-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
Agent service needs to require the startup script #788
Comments
As far as I can recall, this dependency is automatically managed by Puppet. What version are you using? |
I am using Puppet 6.22.1 and puppet-zabbix 9.1.0. |
Hey @baron1405 ! Can you take a look at the zabbix::startup class. I believe that can solve your problem (although dunno how obvious/usable is that). |
@root-expert thanks for the reply. Yes, I looked at Note that before arriving at the above workaround where I manage the startup script, I tried using arrow notation to have the service class depend on the systemd unit file resource. It did not work but that could be either due to my clumsiness with Puppet or the relationship not being interpreted when or as expected. |
What's your version of puppet/systemd? |
@root-expert Versions are: Puppet: 6.22.1 |
Sorry it wasn't very clear, I was asking what's your version of puppet-systemd module 😅 |
puppet-systemd: 3.0.0 |
The agent service does not explicitly require the startup script. This can result in the agent service starting using the wrong systemd service configuration file. The specific case causing the issue is:
Operating system: CentOS 7.7
Zabbix agent version: Default in the module
The zabbix agent RPM installs a systemd service script in /usr/lib/systemd/system. Because the Service['zabbix-agent'] does not require the Systemd::Unit_File['zabbix-agent.service'] in startup.pp, the service configuration file in /usr/lib/systemd/system is used rather than the correct one in /etc/systemd/system. The results in the service not completing its startup and being left in an undefined state (i.e. "starting" according to systemd).
I was able to work around the problem by telling the agent module not to manage the startup script, installing the startup script in my manifest and having the zabbix::agent require the startup script.
The text was updated successfully, but these errors were encountered: