How to debug a crash in a /etc/init.d script? Works OK when run from command line, worked in 22.04.

[Chris Green]

On Sat, Jun 08, 2024 at 12:02:43PM +0200, Ralf Mardorf via ubuntu-users wrote:
> Hi,
> 
> there's a German expression that says, three guesses.
> 
> 1. Your install seem to be using a mix of /usr/local/libexec/ and
> /usr/libexec/, which looks suspicious to me.
> 
The mix is because there are some bits and pieces required by the
scanner in /usr/libexec, it's only the 'old' bits that are in
/usr/local/libexec/.  It's exactly as it was in the 22.04 system where
it worked OK.


> 2. Since it worked before, it could be a race condition. Systemd could
> be running the init script before the dependencies are ready for use.
> 
Yes, that's what I've been thinking is the most likely cause.  I
suspect that a time delay in a /etc/init.d script is not a good idea
though.  I'll have to try a wrapper script that returns immediately
after starting a script with a delay in it.


> I'll save the third guess for now.
> 
:-)

-- 
Chris Green