Prevent restart loop of mailman container

[icarito]

Should help avoid issues like #5817

Mailman is set to restart continually, this sets a limit of 5 consecutive restarts.

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• PR is descriptively titled 📑 and links the original issue above 🔗
• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
• code is in uniquely-named feature branch and has no merge conflicts 📁
• screenshots/GIFs are attached 📎 in case of UI updation
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

[jywarren]

OK, cool, but we will know if it fails 5 times because of the SMTP test alert or some other means? Thanks!

[icarito]

Mailman fetches the incoming mail, so SMTP test doesn't cover it. We could add a check on SMTP test to test for mailman container availability too... Currently we don't know if it failed and this seems to have caused a lot of issues with continuous restarts.

…

On 5/06/19 10:29, Jeffrey Warren wrote: OK, cool, but we will know if it fails 5 times because of the SMTP test alert or some other means? Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5841?email_source=notifications&email_token=AABQYS6NPCGU2KBD65IWQ7LPY7LVPA5CNFSM4HT3P3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXACXMA#issuecomment-499133360>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABQYS6DTDU62IKW2HFJDKTPY7LVPANCNFSM4HT3P3JA>.

[jywarren]

ok, so shall we merge this and prioritize a monitoring system? we could output into the log after the fetching in the ruby script, and watch that it succeeds in the publicly readable log