Closed MadsRC closed 8 years ago
Reference: https://github.com/saltstack/salt/blob/develop/salt/beacons/service.py
Looks like it fails because the code, contrary to what the documentation says, expects 'onchangeonly' and 'uncleanshutdown' to be present. While simply setting 'onchangeonly' to False would work (it's implied that False is the default value, which it's not) it won't work for 'uncleanshutdown' as it expects a path to a PID file.
I will test it further, consume a tad more RedBull, and hopefully have a patch ready later tonight.
@MadsRC Will this be resolved once #30121 is merged?
@cachedout PR #30121 will solve the service beacon problem atleast on my CentOS 7 servers. If you'd like, I can conduct a few more tests on more systems?
@MadsRC Sure, more testing is always welcome!
I'm not able to reproduce the issue after implementing my patch, and I can't find any regression bugs either. So I think you can consider this issue closed as per #30121
Seems like I forgot to make the PR against the 2015.8.3 branch (as it was a bugfix), do you want me to back-port it so it can be part of the next release?
I'll mark it for backporting. Thanks @MadsRC !
While trying to set up a service beacon and reading the documentation (https://docs.saltstack.com/en/latest/ref/beacons/all/salt.beacons.service.html) I noticed that the following beacon fails and leaves stack traces:
Here's the salt-minion debug log:
System Info: CentOS 7 Salt Version 2015.8.3 from SaltStack's own repo