Re: supervise not running

Larry Weldon wrote:

>> After the readproctitle, add an "echo `date` finished" to see if the
>> script progressing past the svscan start, which it's not supposed to.
>> Then reboot.

> did that. No additions to /tmp/svscanboot.log

So not even a "finished" message?  And yet svscan is no longer running?
And svscanboot not running either?

That sounds incredibly borked if those three processes are dying with
no further entries in the log file.

> Something further - as the system booted this lasst time I saw some
> processes could not start and (I can't be sure - messages fly past
> quickly) but it looked like it was because of messagebus.

Hmm, I can't think of any dependencies on messagebus that would cause
an issue.

Later, in the next message:

>> Don't forget that init reads the inittab top to bottom. If your rc
>> script (not the stuff in /etc/rc?.d but /etc/init.d/rc or whatever
>> your system uses to actually run those scripts) doesn't complete, then
>> init will never get to your svscanboot entry. See if rc.local or
>> something like that never completes. The process list will show the
>> existence of /etc/init.d/rc (or equivalent) if this is happening to
>> you.

> That works. I put it right after;
> id:5:initdefault:

OK, that's weird, because svscanboot was being at least initially
started by init (you have a debug log to prove this), yet it appears
to be getting terminated.  I wonder if something in one of the rc
scripts is killing other processes?

You haven't modified the inittab order recently, have you?

> env - PATH=$PATH svscan /service

My next recommendation was going to be to strace svscan, but if
you're not getting the "finished" message then something (possibly
external) is killing off processes that shouldn't be touched, and
I suspect strace would be one of them.


-- 
Regards,
  Daryl Tester

"I'm beginning to wonder about Cap'n Snooze's military credentials."