On a CentOS-7 machine, after upgrade to a systemd using sensu release (in my case the upgrade was from 0.26.5 to 0.29) the sensu services would not start, with systemd giving an access error. In this case it was because a "systemctl daemon-reload" had not been performed so systemd did not know about the new unit file (but probably still knew about the old init scripts).
Ideally the %postinstall scriptlet would run the reload if the unit didn;t respond to a "status" query, otherwise a note in the docs to do a reload after would be great.
nathanhruby
commented
7 years ago
On a CentOS-7 machine, after upgrade to a systemd using sensu release (in my case the upgrade was from 0.26.5 to 0.29) the sensu services would not start, with systemd giving an access error. In this case it was because a "systemctl daemon-reload" had not been performed so systemd did not know about the new unit file (but probably still knew about the old init scripts).
Ideally the %postinstall scriptlet would run the reload if the unit didn;t respond to a "status" query, otherwise a note in the docs to do a reload after would be great.