SOLVED: systemd won't start atom-worker service: Start request repeated too quickly

[Patrick Goetz]

There is a typo here:
https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/asynchronous-jobs/#installation-asynchronous-jobs

which is going to cause the atom-worker service to fail:

Aug 02 08:09:24 atom systemd[1]: atom-worker.service: Start request repeated too quickly.
Aug 02 08:09:24 atom systemd[1]: atom-worker.service: Failed with result 'exit-code'.
Aug 02 08:09:24 atom systemd[1]: Failed to start AtoM worker.

even when the qtSwordPlugin is enabled.  The last line of the atom-worker.service file needs to be:

  RestartSec=30s

instead of

  RestartSec=30

[José Raddaoui]

Hi Patrick,

I think both values are valid:

https://www.freedesktop.org/software/systemd/man/systemd.service.html#RestartSec= 

Maybe you hit the restart limit, see the tip at the bottom of:

https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/asynchronous-jobs/#installation-asynchronous-jobs 

Best regards,

Radda.

[E Morgan]

Thank you!

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/f6d4fc7b-c423-4db1-b87f-560e8aff7881n%40googlegroups.com.

[Patrick Goetz]

Hi Radda -

I definitely hit the restart limit.  I've written systemd unit files in another context and have found the automatic restart feature to be a bit tricky to work with. In this case, I could not get the atom-worker service to successfully start until I changed RestartSec=30 to RestartSec=30s.  I would include it as it doesn't hurt and removes ambiguity.

On Sunday, August 2, 2020 at 9:18:23 AM UTC-5 E Murphy wrote:

Thank you!

On Sunday, August 2, 2020, Patrick Goetz <pgo...@gmail.com> wrote:

There is a typo here:
https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/asynchronous-jobs/#installation-asynchronous-jobs

which is going to cause the atom-worker service to fail:

Aug 02 08:09:24 atom systemd[1]: atom-worker.service: Start request repeated too quickly.
Aug 02 08:09:24 atom systemd[1]: atom-worker.service: Failed with result 'exit-code'.
Aug 02 08:09:24 atom systemd[1]: Failed to start AtoM worker.

even when the qtSwordPlugin is enabled.  The last line of the atom-worker.service file needs to be:

  RestartSec=30s

instead of

  RestartSec=30

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.

[José Raddaoui]

Hi again Patrick,

I may be wrong but my impression is that the service was not starting due to the restart limit and that changing the service file made it work, not the actual value change. I guess that if you change it back it will still work. I see your point about ambiguity (looking at StartLimitIntervalSec) but it's called RestartSec, and using 30s is a bit redundant. Please, let us know if you still can't make it work with only 30 and we'll give it a deeper look, as I'm not an expert in this matter.

Best regards,

Radda.

[Patrick Goetz]

Hi Radda -

You are correct.  I experimented with several iterations of removing the "s", reloading the daemons, and restarting the service, and it hasn't failed since.  Apparently seconds is the default, as you suggest.  Thanks very much for your persistent help with these matters.