Sign in

what does status=200/chdir even mean???

linuxservicessystemd13 replies 路 446 views 路 started
Reply
  1. Esme V.
    @esme_lambda

    not gonna lie this is driving me nuts api.service was fine until todays server patching. now it wont start:

    The status line says status=200/CHDIR. i didnt touch the unit file. Did the update change smth underneath?

    the update touhced a bunch of packages, so it could be anything... 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 api.service specifically?? what am i doing wrong??

    rage

    13
  2. Ruben Rossi
    @pixelbuilder-2qt

    been there man get the full story from the journal:

    sudo journalctl -u queue-consumer.service -b --no-pager -n 100
sudo systemctl status queue-consumer.service -l

    The journal often has the actual error line that status truncates.

    1 0 helpful
  3. Dev Adler
    @dev_cobalt

    unrelated but anyone elses coffee machine also judging them today

    1 0 helpful
  4. Yusuf Ueda
    @yueda

    @esme_lambda nah thats not it, systemd has nothing to do with it, wait does this also apply to api.service? just my 2 cents

    1 2 helpful
  5. Silas Sato
    @silas.sato

    how is this thread still going lmao

    0 3 helpful
  7. Leon
    @ljansen_10

    after editing, always sudo systemctl daemon-reload and then sudo systemctl restart queue-consumer.service. systemd-analyze verify /etc/systemd/system/queue-consumer.service catches syntax mistakes.

    1 2 helpful
  8. Paula
    @paula_lambda
    in reply to @ljansen_10

    Common exit codes: 203/EXEC means systemd couldnt execute ExecStart (wrong path, missing execute bit, missing shebang, or a relative path) 馃憤 217/USER means the User= doesnt exist :/ 200/CHDIR means WorkingDirectory= is missing or not accessible. good luck man!

    0 2 helpful
  11. Ada Kowalski
    @ada_regex

    make a backup before u touch the DNS, learned that the hard way... dumb question but how do i even check teh antivirus

    thumbsup

    0 4 helpful
  12. Paula
    @paula_lambda

    hmmm if its flapping, check Restart= and StartLimitIntervalSec=/StartLimitBurst=. After hitting the limit, clear it with sudo systemctl reset-failed queue-consumer.service once the cause is fixed. fingers crossed 馃

    4 5 helpful
  13. Leon
    @ljansen_10

    yeahhh test as teh service user, not root: sudo -u appuser /opt/app/run.sh. Permission problems on files or sockets show up immediately. worked for me anyway 馃し

    1 1 helpful
  14. Kenji L.
    @klindqvist

    been there man exact same thing happened to my desktop last month. @paula_lambda did u ever fix it??

    0 6 helpful

Reply to this topic

Sign in or create an account to reply.