On Sunday, June 1, 2003, at 12:11 PM, Tom Brown wrote:
The second instance server log says the server failed at nscp on port
9999.
The first instance already grabbed port 9999. Turning off nscp in the
second instance allowed the second server to start but left me without a
control port -- even though I've not yet tried using one. So I upped the
nscp port on the second instance to 10000. The second instance boots fine
there.
You should understand that you're seeing normal behavior here. The
control port is a server, just like the HTTP port, and you can only have
one process listening on a given IP address and port combo, so just as you
had to move the HTTP port on the dev server, you're also going to have to
move its control port, or just run without the control port by not
including nscp in your modules configuration for the server.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
