[tor-bugs] #13003 [Onionoo]: Figure out a better strategy to avoid concurrent Onionoo executions

[Tor Bug Tracker & Wiki]

#13003: Figure out a better strategy to avoid concurrent Onionoo executions
-------------------------+-----------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------

Comment (by karsten):

 Still no luck.  But I wonder if we can do better than using SMTPAppender.
 The [https://gitweb.torproject.org/admin/tor-nagios.git/blob/HEAD:/tor-
 nagios-checks/checks/tor-check-onionoo Nagios plugin that checks that
 Onionoo is running and returns recent data] works just fine.  Maybe we
 should write a second plugin that checks that the back-end cronjob works
 without problems.  And we could write a third plugin that checks that the
 front-end part works without issues.  The two new plugins would probably
 simply look for a file with error logs on disk.  I can write those scripts
 using Python.  Also, not requiring a working mail setup could make
 deployment easier, too.  Whoever wants to deploy Onionoo can use whatever
 they like to watch the service, which could be our Nagios scripts or
 something else.  What do you think?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13003#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online