Jira (PUP-5402) systemd: Puppet agent starts before network-online.target is reached
Title: Message Title Rene Rinco updated an issue Puppet / PUP-5402 systemd: Puppet agent starts before network-online.target is reached Change By: Rene Rinco Affects Version/s: PUP 4.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5402) systemd: Puppet agent starts before network-online.target is reached
Title: Message Title Rene Rinco commented on PUP-5402 Re: systemd: Puppet agent starts before network-online.target is reached The same here in RHEL7 with 4.8.0: [root@xl-ifr28 system]# rpm -qf /usr/lib/systemd/system/puppet.service puppet-agent-1.8.0-1.el7.x86_64 [root@xl-ifr28 system]# cat /usr/lib/systemd/system/puppet.service # Local settings can be configured without being overwritten by package upgrades, for example if you want to increase puppet open-files-limit to 1, you need to increase systemd's LimitNOFILE setting, so create a file named "/etc/systemd/system/puppet.service.d/limits.conf" containing: [Service] LimitNOFILE=1 You can confirm it worked by running systemctl daemon-reload then running systemctl show puppet | grep LimitNOFILE # [Unit] Description=Puppet agent Wants=basic.target After=basic.target network.target [Service] EnvironmentFile=-/etc/sysconfig/puppetagent EnvironmentFile=-/etc/sysconfig/puppet EnvironmentFile=-/etc/default/puppet ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize ExecReload=/bin/kill -HUP $MAINPID KillMode=process [Install] WantedBy=multi-user.target [root@xl-ifr28 system]# Add Comment
