Forum OpenACS Q&A: nsd won't start

Collapse
Posted by kip canfield on
My 3.2.5 installation from the jmarsden rpms has been running fine
for over a year. Today I couldn't connect and found that aolserver
was crashing for some reason. It starts up fine with all the threads
on a retstart and then everything but the basic process dies almost
instantly.

So if you look at the status of the process it says running. In a ps
aux, nsd is running and then a second line under it (where the
several other nsd lines should be) says defunct and listed as
Zombie. Postgres is running fine. The log is full of lines
like  "Notice: nsd.tcl: sourcing:..." for all params on every start.

Collapse
Posted by kip canfield on
I think these log lines from messages are the problem:
Oct 11 14:46:35 lhi1 nsd: [11/Oct/2002:14:46:35][1661.1024][-main-] Notice: nsd.tcl: starting to read config file...
Oct 11 14:46:35 lhi1 nsd: [11/Oct/2002:14:46:35][1661.1024][-main-] Warning: nsd.tcl: nscp not loaded because user/password is not set.
Oct 11 14:46:35 lhi1 nsd: [11/Oct/2002:14:46:35][1661.1024][-main-] Warning: nsd.tcl: nsssl not loaded because key/cert files do not exist.
Oct 11 14:46:35 lhi1 aolserver: nsd startup succeeded
Why? As I mentioned, it has been working for a long time with no configuration changes.
Collapse
Posted by kip canfield on
Ok, OK, so that was NOT it. Still looking...
Collapse
Posted by Patrick Giagnocavo on
Is it possible that you have upgraded something else on the system?

If running Linux, you sometimes have to be careful about upgrading your glibc library.

I have found in occasional cases that vacuum-ing the Postgres database can fix the problem, apparently the sec_sessions (not sure of exact name) table can get out of whack.  Search the forums for more info on that, if you wish.

Collapse
Posted by kip canfield on
Thanx. Vacuuming didn't help but I have been upgrading the rpms resident on
the rh7.1 box continually, including the development stuff. The problem didn't
seem to coincide exactly with an upgrade. Is there something specific I should
check with glibc?
Collapse
Posted by kip canfield on
I fixed it. I had to increase the stack size in nsd.tcl as  mentioned in: http://
openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0004ra&topic_id=11&
topic=OpenACS.