search

goetzk / ansible-shinken

Ansible configuration role for Shinken monitoring system
2 stars 2 forks source link

Shinken doesn't correctly restart under systemd #10

Closed goetzk closed 7 years ago

goetzk commented 7 years ago

While not a defect in this role, it is something that needs to be worked around here in places.

See for example: https://github.com/naparuba/shinken/issues/1763 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777148#25

There appear to be systemd units (those referenced in the shinken issue above) at https://github.com/naparuba/shinken/tree/master/for_fedora/systemd but I can't see them on my installed shinken server.

While investigating why only my arbiter was starting I discovered that /var/run/shinken was owned root:root and none of the other daemons could write their pid files in there. I believe that is a bug in shinkens init script/s and their interaction with systemd.

Sysvinit is "fine" and things restart correctly.

I will look in to fixing /var/run/ permissions

goetzk commented 7 years ago

While looking in to this I came across another shinken commit that seems related. https://github.com/naparuba/shinken/commit/ac2b318624e3cd6c76e1f726d7109fb31453d626

goetzk commented 7 years ago

This has fixed the issue from my PoV - anyone using the role will now be able to run it with a degree of confidence that their shinken will start afterward.