Hi Remi, On Thu, Sep 28, 2023 at 11:37:32AM +0400, Remi L. wrote: > While this workaround is effective for now, I'm still open to a more proper > solution if one comes up. If you or anyone else has any further insights, > I'd greatly appreciate it.
I have the same issue with audio/navidrome: it starts fine manually, but not at boot time with the rc script. If I turn on verbose logging and add a `daemon_logger` to the rc.d script, then I can see from the logs that it comes up, but shortly after receives a SIGHUP, which causes it to stop dead. ``` Dec 4 20:44:11 arrakis navidrome[33817]: time="2023-12-04T20:44:11Z" level=info msg="----> Navidrome server is ready!" address="0.0.0.0:4533" startupTime=357ms tlsEnabled=false ... Dec 4 20:44:12 arrakis navidrome[33817]: time="2023-12-04T20:44:12Z" level=info msg="Received termination signal" signal=hangup Dec 4 20:44:12 arrakis navidrome[33817]: time="2023-12-04T20:44:12Z" level=info msg="Stopping HTTP server" ``` Ignoring the fact that a SIGHUP should cause a daemon to *restart* (not halt), I still don't know where the SIGHUP is coming from. I wonder if this is the same issue as you are seeing with your Node stuff? So does anyone know where a SIGHUP might come from as the system is coming up? -- Best Regards Edd Barrett https://www.theunixzoo.co.uk
