Sign in

START REQUEST REPEATED TOO QUICKLY. IS BACKUP.SERVICE BROKEN OR IS SYSTEMD?

linuxservicessystemd5 replies 路 131 views 路 started
Reply
  1. Una Ferreira
    @unaf901

    ok weird one i wrote a simple unit file for our app... running teh command manually works perfectly. runnnig it as backup.service:

    This app can't run on your PC

    This app can't run on your PC

To find a version for your PC, check with the
software publisher.

    systemctl status shows sattus=200/CHDIR and thats it. No useful message. Ive reloaded the daemon a dozen times.

    ive compared the command in ExecStart with what i type in my shell character by character. they look identical. the service user exists. im clearly missing somehting about how systemd runs things, but i cant figure out what it is.

    1
  2. Mateo Ziegler
    @mateo_vector

    Which User= does the unit run as, and does that user have access to the working directory??

    2 1 helpful
  4. Felix M.
    @fmendes-2rm

    oof test as the service user, not root: sudo -u appuser /opt/app/run.sh. Permission problems on files or sockets show up immediately. good luck man!

    15 0 helpful
  5. Haruto Nolan
    @hnolan_30

    ok so if its flpaping, check Restart= and StartLimitIntervalSec=/StartLimitBurst=. after htiting teh limit, clear it with sudo systemctl reset-failed myapp.service once teh cause is fixed. worked for me anyway 馃し

    6 0 helpful
  6. Tess Rossi
    @tessr333

    Id skip hand-writing unit files and run teh app in a cotnainer with a restart policy 馃檹 Fewer surprises around environment and users.

    0 6 helpful

Reply to this topic

Sign in or create an account to reply.