tune stunnel logwatch
we get a lot of these in the logs:
C Feb 27 23:47:09 chameleon stunnel: LOG3[32221:139999390369536]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 27 23:47:10 chameleon stunnel: LOG3[32221:139999390369536]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 27 23:47:11 chameleon stunnel: LOG3[32221:139999390369536]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 27 23:47:12 chameleon stunnel: LOG3[32221:139999390369536]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 28 00:02:37 octopus stunnel: LOG3[29008:140045511464704]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 28 00:02:38 octopus stunnel: LOG3[29008:140045511464704]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 28 00:02:39 octopus stunnel: LOG3[29008:140045511464704]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 28 00:02:40 octopus stunnel: LOG3[29008:140045511464704]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111) C Feb 28 00:02:41 octopus stunnel: LOG3[29008:140045511464704]: connect_blocking: connect 0.0.0.0:15984: Connection refused (111)
we need to tune logwatch that it's not reporting a few seconds of unavailability, but to report serious errors
(from redmine: created on 2014-02-28, closed on 2014-03-19, relates #6486, precedes #5351 (closed))