Sign in

Systemd Says 'Failed To Start' And Nothing Else. Where Are The REAL Logs?

Solvedlinuxservicessystemd9 replies · 297 views · started
Reply
Accepted solution by Diego Sorensen — test as teh service user, not root: sudo u appuser /opt/app/run.sh. permission problems on files or sockets show up immediately. hope that…
  1. Fenna Costa
    @heap_fox816

    myapp.service was fine until todays server patching. now it wont start:

    the status line says status=1/FAILURE 👍 i didn't touch the unit file. did teh updtae change smth underneath?

    the update touched a bunch of pacakges, sooo it could be anything xD ive checked that teh binary is still there and still runs by hand as root. is there a good way to see what changed for myapp.service specifically?

    6
  2. Zora
    @zora_tensor

    hmmm what does journalctl -u worker.service -b show right before the failure?

    0 2 helpful
  3. Fenna Costa
    @heap_fox816
    in reply to @zora_tensor

    journal says Failed to locate executable and then status=1/FAILURE... so teh path is wrong somehow. sorry for the wall of text lol

    2 2 helpful
  4. Zora
    @zora_tensor

    xD

    4 0 helpful
  5. Xavi P.
    @xpereira

    oof after editing, always sudo systemctl daemon-reload and then sudo systemctl restart worker.service. systemd-analyze verify /etc/systemd/system/worker.service catches snytax mistakes.

    1 0 helpful
  6. Cleo Iqbal
    @cleo.iqbal

    if it's flapping, check Restart= and StartLimitIntervalSec=/StartLimitBurst=... after hitting the limit, clear it with sudo systemctl reset-failed worker.service once teh cause is fixed.

    2 0 helpful
  7. Xavi P.
    @xpereira

    @gpetrov works on paper, not in real life

    1 1 helpful
  8. Diego Sorensen
    @diego.sorensen
    Accepted solution

    test as teh service user, not root: sudo -u appuser /opt/app/run.sh. permission problems on files or sockets show up immediately. hope that helps :)

    0 5 helpful

Reply to this topic

Sign in or create an account to reply.