- changed status to resolved
25 million lines of "SSL: write error -- Broken pipe" in eight minutes
Upgraded from 5.11 to 5.12.1 on all servers (46 of them) this afternoon (14:15 localtime). All running fine. Ten minutes ago my m/monit server threw an alert for failed Heatbeat on one server. On investigating, found that Monit began throwing the error "SSL: write error -- Broken pipe" beginning at 22:59:57 localtime, ending only after I issued a kill -9 to monit at 23:08:19:
root@mia-tm-tru-main-primary: /var/log # grep "SSL: write error -- Broken pipe" daemon.log|wc -l 25212419 root@mia-tm-tru-main-primary: /var/log # du -hs daemon.log 1.7G daemon.log (normally about 300k per day)
Nothing else was written to the daemon.log by monit besides when I started it at 14:15 localtime.
Debian 6.0.10 32 bit Built with: ./configure --without-pam --enable-optimized
Comments (4)
-
repo owner -
repo owner Hello,
fix added to the development version, please can you test it? The fixed source code is here: http://mmonit.com/tmp/monit-5.12.2_20150310.tar.gz
To compile:
tar -xzf monit-5.12.2_20150310.tar.gz cd monit-5.12.2_20150310 ./configure --without-pam --enable-optimized make
-
reporter Installed.
-
repo owner - removed version
Removing version: 5.12 (automated comment)
- Log in to comment
fixed Issue
#169→ <<cset 908f3b9784bb>>