Forum OpenACS Q&A: Aolserver cannot restart
ps ax showed a single [nsd] with status "DW" (that could not be killed), netstat showed a lot of connections to port 80 in status SYN_RECV. there were also still some postgres backends around.
i tried to get rid of the connections by restarting the network, taking down eth0 but nothing worked. (why is that by the way?)
did anyone else have such problems? i would be glad to hear about any experiences with something like that!
I use daemontools too and have not faced this problem yet.
However, while testing/development, I generally use a
killall -9 nsd
to make sure my aolserver is properly shutdown.
Ofcourse be careful using this method if you are running multiple instances of AOLServer !
My (only) solution to the problem was to restart the server, nothing else seemed to help.
The problem could be with the location of the pid file. Check your logs to see if AOLServer could create the PID file. If it can't, restarting aolserver via nsd will not be possible.
If there is a problem there is a parameter in the config file for pointing the file to somewhere suitable (where permissions are favourable).
using daemon tools will obviate the need for the above solution as no pid file is created.