#40 Problem in configurin AOLServer: Not able to get proper Port

[chillyroll]

Hello guys,

I am trying to install AOLServer on my server using instructions on http://openacs.org/doc/current/aolserver4.html. I was able to run all the instructions successfully of this document. But when I test the server installation, I am not getting the welcome page. That means, server is not configured properly. When I referred to the log file in /usr/local/aolserver/log/server.log, I get following line:

Error: nssock: failed to listen on 127.0.0.1:8000: Address already in use

Then I went on to change the sample-config.tcl file from

set hostname [ns_info hostname]
set address [ns_info address]

to

set hostname [ns_info hostname]
#set address [ns_info address]
set address 0.0.0.0

to allow AOLserver listen on all available addresses. I tried several ports where I can find AOLServer listening, but I am not getting the AOLServer welcome page on any of them.

So, I request you to guide me on this configuration.

Thanks in advance.

[Scott S. Goodwin]

Logged In: YES
user_id=37651
Originator: NO

The error "Address already in use" indicates that something else on your host is currently listening on that port. This normally happens to me when I've started nsd and then try to start it again, not realizing that I haven't stopped the first one.

You can use lsof to see what process that might be. netstat can also be used to help determine what's using that port.

Also, you can try putting the server on another port that you are certain is not in use (but is still above port 1024) just to confirm the problem.

[Scott S. Goodwin]

Logged In: YES
user_id=37651
Originator: NO

The error "Address already in use" indicates that something else on your host is currently listening on that port. This normally happens to me when I've started nsd and then try to start it again, not realizing that I haven't stopped the first one.

You can use lsof to see what process that might be. netstat can also be used to help determine what's using that port.

Also, you can try putting the server on another port that you are certain is not in use (but is still above port 1024) just to confirm the problem.