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

Luca · 2026-08-22T20:31:17.483Z

guys pls help i wrote a simple unit file for our app. Running teh command manually works perefctly. Running it as worker.service: [code] systemctl status shows sattus=1/FAILURE and thats it... no useful message... ive relaoded the dameon a dozen times. Ive compared the command in ExecStart with what i type in my shell character by character, they look identical, the srevice user exists, im clearly missing something about how systemd runs things, but i cant figure out what it is.

Solvedlinux services systemd1 replies · 96 views · started 2 mo. ago

Accepted solution by Pia D. — if its flapping, check Restart= and StartLimitIntervalSec=/StartLimitBurst=. After hitting the limit, clear it with sudo systemctl reset…

Luca
@framemonk
130 rep · 18 posts
2 mo. ago
guys pls help i wrote a simple unit file for our app. Running teh command manually works perefctly. Running it as worker.service:
```
This app can't run on your PC

To find a version for your PC, check with the
software publisher.
```
systemctl status shows sattus=1/FAILURE and thats it... no useful message... ive relaoded the dameon a dozen times.

Ive compared the command in ExecStart with what i type in my shell character by character, they look identical, the srevice user exists, im clearly missing something about how systemd runs things, but i cant figure out what it is.
3
Pia D.
@piad258
180 rep · 13 posts
2 mo. ago Accepted solution
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.

0 4 helpful

Reply to this topic