Can i use any port other than 8000 or 8100?

[sk545]

Abyssws (Linux version) seems to run fine on ports 8000 or 8100. But how come it has to use those big ports? Can i set it to like port 81? I tried it with port 81, but i get a error saying that the port is already in use:

[nquin321]

Set apache on a different port and try it again.
_________________
How many forum members does it takes to change a light bulb?

[Anonymoose]

netstat -a -n to list ports in use and double check, or nmap localhost.

To use a port under 1024 in Linux you must be logged in as root - if you haven't properly configured how Abyss will run or are running it under a normal user account, you won't be able to bind to anything under 1024.

[sk545]

ok, yes, i was logged in as non-root. So i redid everything from sratch and dowloaded the file to the root's home folder. There i untarred it and ran it. But there is a permissions problem now (the following is when i access http://127.0.0.1:9999/ as a non-root through a browser and try to set up a admin account) :

[Anonymoose]

Your Abyss.conf is owned by root with rw permissions only for root. All the other files are owned by 'cdrecording' and have full rwx permissions. Are you sure Abyss is running as root?

What does the output of ps aux | grep -i "abyss" show ?

[sk545]

permissions are such a pain in linux...

sorry, just had to vent.

Here is what it looks like:

[Anonymoose]

Wierd. Abyss running as root and the conf file owned as root, I can't see a problem. Unless anyone else comes up with something beforehand, I'll give it a try on my slack box at work tomorrow and see if what happens...

Edit: Does this help? See Apreliums post further down the thread...

http://www.aprelium.com/forum/viewtopic.php?t=2443

[sk545]

that helped a little and i can run it as a daemon, but whenver i try to make any changes in the web console, it just spits out the same permissions error as above. :(

So right now i have abyss in my home user directory with these permissions (since the link you gave said specifically not to run it as root):

[aprelium]

sk545,

Please have a look on Abyss Web Server user's manual. All these issues are explained and solved there.

* You cannot use port < 1024 if you are a normal user on UNIX systems. Only root can use these ports.
* For security reasons, Abyss doesn't run as root. It will change its current user to the System User (by default nobody). This change is done after setting the ports.
* The configuration file cannot be saved because the "System User" has no right to write to it.

For security reasons, when you run Abyss as root, it immediately switches to
a less privileged user (by default it switches to the user defined in
Console > Server Configuration > Advanced > Server Parameters > System
User - It is nobody by default).
If you update the configuration, Abyss needs to write to abyss.conf. But as
we can see in the second screenshot, abyss.conf is owned by root, and the
less privileged user has no permission to write to this file. Thus the
error.

There are many ways to solve the issue (and the ports issue), here is the best one (in our opinion of course):

* Login as root
* cd to your abyssws directory.
* We assume that xxx is the System User you have configured (by default, it
is nobody)
* Execute:

[sk545]

thx, this helps a lot.

I can run it fine now with the command 'su xxx -c ./abyssws', but if i run it with the command './abyssws', i am only able to make changes directly in the abyss.conf file. I can't go to the web console and do it since it ends up giving a error if i either want to change port or the document directory:

[aprelium]

sk545,

/rc.d scripts are run by root so you don't need to use the su command. ./abyssws is sufficent.
_________________
Support Team
Aprelium - http://www.aprelium.com

[sk545]

I am still having trouble with it after starting it as a daemon.

Here is what i did:

1) untarred abyss.tar file as non-root
2) ran ./abyssws as non-root to generate a abyss.conf file.
3) su, and did all of the above steps you mentioned.
4) edited /etc/rc.local and added this to it:

echo "Starting Abyss Web Server..."
pushd . > /dev/null
cd /home/khurram/abyssws
./abyssws -d
popd > /dev/null

5) Rebooted computer and the web server started fine.
6) However, going to the console, and trying to change any settings yields the same error message about not being able to save the configuration file.

The permissions are like this as of now:

[aprelium]

sk545,

Run Abyss using the non-root useraccount "me". Log to the console, go to Server Config. > Advanced > Server Parameters and change the System User to me (the user who owns the abyss.conf file.)

Now, everything should go fine.
_________________
Support Team
Aprelium - http://www.aprelium.com

[sk545]

thx. I changed the abyss.conf file's SysUser to me manually. Then i rebooted and i was able to change the document path and all. But, when i tried to change its default port 8000, it gave me a error:

[iNaNimAtE]

[aprelium]

sk545,

This behavior seems to come from a small file permissions error (yet another.)
Please send tp support@aprelium.com your abyss.conf file, your rc.d script (where Abyss is launched) and the output of ls -al of your Abyss Web Server directory.
_________________
Support Team
Aprelium - http://www.aprelium.com

[sk545]

hrm. I don't have a rc.d script, all i have is a /etc/rc.local in which i put in this:


echo "Starting Abyss Web Server..."
pushd . > /dev/null
cd /home/khurram/abyssws
./abyssws -d
popd > /dev/null

Should i email the rc.local?

[aprelium]

sk545,

Yes, please. Do not forget to send us your abyss.conf file as well as the output of ls -al of your Abyss Web Server directory.
_________________
Support Team
Aprelium - http://www.aprelium.com

[sk545]

alright, i sent it.

Let me know if you all receive the files.

Thx.