Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Another python3 fix, and some error logging | Tom Ritter | 2020-09-08 | 1 | -7/+10 |
| | |||||
* | Better error logging | Tom Ritter | 2020-09-08 | 2 | -15/+19 |
| | |||||
* | Other python3 fixes | Tom Ritter | 2020-09-08 | 3 | -5/+5 |
| | |||||
* | base64 encode requires bytes | Tom Ritter | 2020-09-08 | 1 | -1/+2 |
| | |||||
* | env python -> python3 | Tom Ritter | 2020-09-07 | 8 | -8/+8 |
| | |||||
* | Run futurize on the codebase for python3 | Tom Ritter | 2020-09-07 | 8 | -16/+33 |
| | |||||
* | Correct line endings | Tom Ritter | 2020-09-07 | 3 | -175/+175 |
| | |||||
* | Fix executions that stomped on each other | Tom Ritter | 2017-11-11 | 1 | -2/+2 |
| | | | | | | | | | | | | Every hour I would fire off two executions: the minute execution and the hour execution. Each would read the statefile on start. Whichever execution took longer would overwrite the state file with the data that was present for the other's execution upon start. This would manifest as extra notifications if the starts aligned - because the 'I already sent a notification' member update wasn't being persisted. This fixes it by only performing one execution at any given time, but knowing to run all the relevant jobs for that type of execution. AKA When I run the hourly job I also run the minute jobs. Another problem related to this one is logged in #1 - minute executions that take longer than a minute will also cause this type of error. | ||||
* | Add 5 and 10 minute intervals and fix bwauth last scanner check | Tom Ritter | 2017-04-03 | 1 | -0/+2 |
| | |||||
* | Hopefully finally solve the bug about only getting success messages for ↵ | Tom Ritter | 2017-03-03 | 1 | -2/+6 |
| | | | | state change alerts | ||||
* | Give a day notification a little widdle room | Tom Ritter | 2017-02-06 | 1 | -1/+1 |
| | |||||
* | Only notify on failures and successes after the number of failures required | Tom Ritter | 2017-02-01 | 1 | -8/+8 |
| | |||||
* | Clarify the job inheritance info and make the state file simpler | Tom Ritter | 2017-02-01 | 3 | -3/+3 |
| | |||||
* | Change the statename to base64 instead of sha1 for debugging purposes. | Tom Ritter | 2016-12-28 | 1 | -2/+2 |
| | |||||
* | Create an option that lets you require two failures before alerting. | Tom | 2016-12-28 | 7 | -19/+50 |
| | |||||
* | Check for 200 status code and set server timeout to 10 | Tom Ritter | 2016-12-28 | 2 | -5/+8 |
| | |||||
* | Add TLS certificate expiration checker | Tom | 2016-09-14 | 1 | -0/+58 |
| | |||||
* | Add email body to nomail output | Tom | 2016-09-14 | 1 | -1/+1 |
| | |||||
* | Add daily failure notifications | Tom | 2016-09-14 | 1 | -0/+7 |
| | |||||
* | Set a timeout on socket connections | Tom | 2016-09-14 | 1 | -0/+1 |
| | |||||
* | Add a new nomail commandline option for debugging | Tom | 2016-09-14 | 2 | -0/+8 |
| | |||||
* | Need to compare timedelta to timedelta | Tom Ritter | 2016-05-09 | 1 | -3/+3 |
| | |||||
* | Add in the friendly name to the state file for debugging | Tom Ritter | 2016-02-02 | 1 | -0/+2 |
| | |||||
* | Fix the super() calling | Tom Ritter | 2016-01-31 | 4 | -5/+5 |
| | |||||
* | Get custom state names for each of the jobs now | Tom Ritter | 2016-01-31 | 4 | -2/+7 |
| | |||||
* | Correcting a few small errors | Tom Ritter | 2016-01-31 | 2 | -4/+4 |
| | |||||
* | Refactor lots of things to allow you to be notified every so often, instead ↵ | Tom Ritter | 2016-01-31 | 7 | -54/+160 |
| | | | | of every single time. | ||||
* | For getting boolean values I need to coerce the type | Tom Ritter | 2016-01-28 | 2 | -2/+2 |
| | |||||
* | Add an option to use or bust gmail threading | Tom Ritter | 2016-01-28 | 1 | -1/+3 |
| | |||||
* | Add day and daily at noon options | Tom Ritter | 2016-01-26 | 2 | -0/+3 |
| | |||||
* | Differentiating between a mail problem and jobs not being run. | Tom Ritter | 2016-01-26 | 1 | -1/+9 |
| | |||||
* | Add a server identifier to the settings file. | Tom Ritter | 2016-01-26 | 1 | -2/+2 |
| | |||||
* | Debugging why EmailChecker was failing. Added more details to the ↵ | Tom Ritter | 2016-01-26 | 1 | -2/+10 |
| | | | | notification, and diagnosed it to a time window search issue. | ||||
* | Fixing PeerChecker to actually work, and report details of a failure | Tom Ritter | 2016-01-26 | 2 | -5/+12 |
| | |||||
* | Log an exception if we can't send email. | Tom Ritter | 2016-01-25 | 1 | -2/+3 |
| | |||||
* | Initial commit of checker | Tom Ritter | 2016-01-25 | 7 | -0/+306 |