CodeShakingSheep
commented
11 months ago I just took some time to investigate this issue myself. I found these log lines which seem to be relevant:
Aug 02 10:38:17 systemd[1]: listmonk.service: Start request repeated too quickly.
Aug 02 10:38:17 systemd[1]: listmonk.service: Failed with result 'exit-code'.4 of 5 attempts for starting the service are executed in the exact same second. To fix the issue that the start request is repeated too quickly, a possible solution would be to specify RestartSec=2s in systemd service file or perhaps the number of seconds between the start attempts even needs to be increased.
Setting RestartSec=2c is also done in Vikunja, see here which seems to work great (at least I never encountered any failed Vikunja service startups and I'm running Vikunja on the same server as Listmonk). Would you accept a PR for this @navanchauhan ?
navanchauhan
Describe the bug
After I restart my whole yunohost server, listmonk service often fails to restart. According to the logs the problem seems to be that the service tries to start before the DB is up again. When I start listmonk service manually after server is up again there is no issue. So, may be a solution would be to tell listmonk service to wait until DB is up again before restarting. I have a lot of systemd services running and listmonk is the only one with this problem. Thank you for help.
Context
Steps to reproduce
Just restart whole Yunohost server and wait if listmonk systemd service starts successfully.
Expected behavior
Listmonk systemd service should start successfully after server restart.
Logs
Here are the logs: https://paste.yunohost.org/lejehupavu