root@syslog:~# monit status Monit 5.23.0 uptime: 0m Process 'fail2ban' status OK monitoring status Monitored monitoring mode active on reboot start pid 569 parent pid 1 uid 0 effective uid 0 gid 0 uptime 3d 0h 20m threads 3 children 0 cpu 0.0% cpu total 0.0% memory 1.0% [42.0 MB] memory total 1.0% [42.0 MB] disk read 0 B/s [2.2 GB total] disk write 0 B/s [64.0 MB total] unix socket response time 0.040 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT data collected Mon, 24 Apr 2017 14:49:11 File 'fail2ban_log' status OK monitoring status Monitored monitoring mode active on reboot start permission 640 uid 0 gid 4 size 305.0 kB access timestamp Mon, 24 Apr 2017 14:40:08 change timestamp Mon, 24 Apr 2017 14:46:45 modify timestamp Mon, 24 Apr 2017 14:46:45 content match no data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'tns1' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.460 ms port response time 0.706 ms to xxx.xxx.176.138:53 type UDP/IP protocol DNS data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'tns2' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.511 ms port response time 0.668 ms to xxx.xxx.177.72:53 type UDP/IP protocol DNS data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'voipology' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.519 ms port response time 144.257 ms to xxx.xxx.19.41:443 type TCP/IP using TLS (certificate valid for 2195 days) protocol HTTP port response time 0.963 ms to xxx.xxx.19.41:80 type TCP/IP protocol HTTP port response time 0.776 ms to xxx.xxx.19.41:5060 type UDP/IP protocol SIP data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'voipnow' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.437 ms port response time 131.543 ms to xxx.xxx.176.175:443 type TCP/IP using TLS (certificate valid for 888 days) protocol HTTP port response time 0.885 ms to xxx.xxx.176.175:80 type TCP/IP protocol HTTP port response time 0.511 ms to xxx.xxx.176.175:5060 type UDP/IP protocol SIP data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'meost' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.504 ms port response time 12.471 ms to xxx.xxx.176.178:443 type TCP/IP using TLS (certificate valid for 107 days) protocol HTTP port response time 1.101 ms to xxx.xxx.176.178:80 type TCP/IP protocol HTTP data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'cloudbackup' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.437 ms port response time 7.133 ms to xxx.xxx.176.172:443 type TCP/IP using TLS (certificate valid for 383 days) protocol HTTP port response time 1.105 ms to xxx.xxx.176.172:80 type TCP/IP protocol HTTP data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'xxx' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 0.061 ms port response time 6.992 ms to xxx.xxx.20.161:110 type TCP/IP protocol POP port response time 0.441 ms to xxx.xxx.20.161:53 type TCP/IP protocol DNS port response time 7.156 ms to xxx.xxx.20.161:143 type TCP/IP protocol IMAP port response time 20.668 ms to xxx.xxx.20.161:443 type TCP/IP using TLS (certificate valid for 53 days) protocol HTTP port response time 1.951 ms to xxx.xxx.20.161:80 type TCP/IP protocol HTTP port response time 21.646 ms to xxx.xxx.20.161:25 type TCP/IP protocol SMTP data collected Mon, 24 Apr 2017 14:49:11 Remote Host 'newmail' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 351.664 ms port response time 19.995 ms to xxx.xxx.20.214:143 type TCP/IP protocol IMAP port response time 62.236 ms to xxx.xxx.20.214:8000 type TCP/IP protocol HTTP port response time 103.020 ms to xxx.xxx.20.214:587 type TCP/IP protocol SMTP port response time 94.157 ms to xxx.xxx.20.214:25 type TCP/IP protocol SMTP data collected Mon, 24 Apr 2017 14:49:12 Remote Host 'googledns' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 9.883 ms port response time 19.974 ms to 8.8.8.8:53 type TCP/IP protocol DNS data collected Mon, 24 Apr 2017 14:49:12 Remote Host 'opendns' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 8.703 ms port response time 17.400 ms to 208.67.222.222:53 type TCP/IP protocol DNS data collected Mon, 24 Apr 2017 14:49:12 Remote Host 'rbs' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 14.415 ms port response time 141.394 ms to xxx.xxx.136.138:8000 type TCP/IP protocol HTTP port response time 138.164 ms to xxx.xxx.136.138:143 type TCP/IP protocol IMAP port response time 195.862 ms to xxx.xxx.136.138:25 type TCP/IP protocol SMTP data collected Mon, 24 Apr 2017 14:49:12 Remote Host 'fth' status OK monitoring status Monitored monitoring mode active on reboot start ping response time 6.477 ms port response time 45.304 ms to xxx.xxx.97.6:8000 type TCP/IP protocol HTTP port response time 68.265 ms to xxx.xxx.97.6:143 type TCP/IP protocol IMAP port response time 115.457 ms to xxx.xxx.97.6:25 type TCP/IP protocol SMTP data collected Mon, 24 Apr 2017 14:49:13 System 'syslog' status OK monitoring status Monitored monitoring mode active on reboot start load average [0.00] [0.00] [0.00] cpu 0.0%us 0.0%sy 0.0%wa memory usage 1.3 GB [32.8%] swap usage 1.5 GB [38.5%] uptime 3d 0h 20m boot time Fri, 21 Apr 2017 14:28:56 data collected Mon, 24 Apr 2017 14:49:13 root@syslog:~#