Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systemd startup #298

Closed
jhnlsn opened this issue Oct 20, 2021 · 1 comment · Fixed by #344
Closed

Systemd startup #298

jhnlsn opened this issue Oct 20, 2021 · 1 comment · Fixed by #344
Milestone

Comments

@jhnlsn
Copy link
Contributor

jhnlsn commented Oct 20, 2021

Users running Centos/RHEL 8 may experience a problem with the agent after rebooting their instance where the agent no longer publishes data to CloudWatch.

change "After=network.target" to "After=network-online.target"

More information about different targets: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

@jhnlsn jhnlsn added this to the 1.247350.0 milestone Oct 20, 2021
@SaxyPandaBear
Copy link
Contributor

More reading on systemd and the network targets.

The network target does not significantly delay the execution of the boot process. Reaching the network target means that the service that is responsible for setting up the network has started. However, it does not mean that a network device was configured. This target is important during the shutdown of the system. For example, if you have a service that was ordered after the network target during bootup, then this dependency is reversed during the shutdown. The network does not get disconnected until your service has been stopped. All mount units for remote network file systems automatically start the network-online target unit and order themselves after it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants