Re: Systemd Unit Fails at Boot, but Succeeds when Started from the Console

[Jonathan Ryshpan <jonrysh@xxxxxxxxxxx>]

On Sun, 2023-04-30 at 16:41 -0500, Chris Adams wrote:

Once upon a time, Jonathan Ryshpan <jonrysh@xxxxxxxxxxx> said:

This unit 

   $ cat /etc/systemd/system/noip-duc.service  

   [Unit]

   Description=No-IP Dynamic Update Client

   After=network.target auditd.service

This should probably be network-online.target.

always fails at boot time with the message status=2/INVALIDARGUMENT

That's the exit code from the program.  It is probably the return code from a system call made within the program, not in response to some    command-line argument.  But if the program runs before the network is up and doesn't handle waiting, that's the most likely culprit.

A very plausible theory. I was sure this would fix the problem; but it is not so. I edited /etc/systemd/system/noip-duc.service as you recommend.

The file noip-duc.service has been edited to change  
       After=network.target auditd.service
to
       After=network-online.target auditd.service

>

And the problem remains. Further advice would be welcome.

-- 

Sincerely Jonathan Ryshpan <jonrysh@xxxxxxxxxxx>

	Common sense is the collection of prejudices
	acquired by the age of eighteen. -- Einstein

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue