Closed Bug 690590 Opened 13 years ago Closed 11 years ago

monitor puppet logs for cert problems

Categories

(Release Engineering :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jhford, Unassigned)

References

Details

(Whiteboard: [puppet][puppetca])

puppet cert problems are common and block machines from entering production or syncing with puppet. There are two major failure cases: 1) machine has been signed but now presents a new cert 2) machine has not been signed and is waiting for signing I have written a script that monitors the logs for these failures cases. The first failure case is automatically fixed, while the second case is not for security reasons. I dont know how to send emails from python and I don't know if we expect to have outgoing mail access from puppet masters. https://gist.github.com/1252149
Priority: -- → P5
I have https://gist.github.com/1252149/bf5715c7d3f85c5457883f7e6b50d2f9cb3342ac running in a screen session on scl-production-puppet. It is emailing me properly.
When I disconnect from this host, I am getting the following exception. Not sure why this is happening, especially given that the program is running under screen Traceback (most recent call last): File "watch_puppet.py", line 94, in ? main() File "watch_puppet.py", line 90, in main watch(sys.argv[1]) File "watch_puppet.py", line 78, in watch process_line(data) File "watch_puppet.py", line 65, in process_line m.group("hostname") File "watch_puppet.py", line 48, in handle_waiting_cert email(subject,body) File "watch_puppet.py", line 23, in email sender = '%s@%s' % (os.getlogin(), socket.gethostname()) OSError: [Errno 2] No such file or directory
Found in triage.
Blocks: re-nagios
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: hwine
This bug was about "old puppet". All "puppetAgain" errors send out an e-mail, which includes cert errors
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.