[BlueOnyx:17605] Re: problems with a 5106 _ httpd / cced /admserv not working

[Michael Stauber]

Hi Janwillem,

> [root at s16 init.d]# ./cced.init status
> 
> cced dead but subsys locked
> 
> [root at s16 init.d]# ./cced.init start
> 
> Starting cced:                                             [  OK  ]
> Running CCE constructors:

When "Running CCE constructors:" is not eventually (it may take a while)
followed by an "[ OK ]", then there are probably some stuck processes.
Like "pperld" processes, handlers that never finished, stuck cronjobs or
and things like that.

So it would be helpful to see the process list for further diagnosis.
The command for that is "ps axf".

Before it's possible to restart CCEd successfully these "stuck"
processes need to be killed off.

The fastest way to get this sorted would really be a reboot.

Other than that you can try this:

killall -9 cced
killall -9 pperld

Then check with lsof to see if there are still files open that belong to
Sausalito or CCEd:

lsof -n|grep /usr/sausalito

If there are, then CCEd is not really fully stopped and some processes
related to it are still running. The second column gives the process ID
and you need to kill these processes one by one:

kill -9 <process ID>

Then check again with the above lsof command until nothing more is reported.

Finally you should be able to restart CCed:

/sbin/service cced.init restart

-- 
With best regards

Michael Stauber