Monitoring Octobre 2016

monitoring@federez.net

4 participants
75 discussions

par monit＠hexagon.federez.net

Connection failed Service ssh Date: Sun, 23 Oct 2016 09:29:54 Action: restart Host: hexagon.federez.net Description: failed protocol test [SSH] at INET[localhost:22] via TCP -- SSH: error receiving identification string -- Resource temporarily unavailable Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Does not exist fail2ban

par monit＠hexagon.federez.net

Does not exist Service fail2ban Date: Sun, 23 Oct 2016 09:28:40 Action: restart Host: hexagon.federez.net Description: process is not running Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Execution failed fail2ban

par monit＠hexagon.federez.net

Execution failed Service fail2ban Date: Sun, 23 Oct 2016 09:27:14 Action: alert Host: hexagon.federez.net Description: failed to stop (exit status -1) -- Program /usr/sbin/service timed out Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Connection failed fail2ban

par monit＠hexagon.federez.net

Connection failed Service fail2ban Date: Sun, 23 Oct 2016 09:20:40 Action: restart Host: hexagon.federez.net Description: failed protocol test [SSH] at INET[localhost:22] via TCP -- SSH: error receiving identification string -- Resource temporarily unavailable Monit, unique employÃ© de federez,

8 années, 7 mois

Cron <root@hexagon> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

par root＠hexagon.federez.net

/etc/cron.daily/logrotate: Job for freeradius.service failed. See 'systemctl status freeradius.service' and 'journalctl -xn' for details. error: error running non-shared postrotate script for /var/log/freeradius/radius.log of '/var/log/freeradius/*.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1

8 années, 7 mois

monit alert -- Connection succeeded fail2ban

par monit＠hexagon.federez.net

Connection succeeded Service fail2ban Date: Fri, 21 Oct 2016 21:37:51 Action: alert Host: hexagon.federez.net Description: connection succeeded to INET[localhost:22] via TCP Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Connection failed fail2ban

par monit＠hexagon.federez.net

Connection failed Service fail2ban Date: Fri, 21 Oct 2016 21:34:34 Action: restart Host: hexagon.federez.net Description: failed protocol test [SSH] at INET[localhost:22] via TCP -- SSH: error receiving identification string -- Resource temporarily unavailable Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Connection succeeded ssh

par monit＠hexagon.federez.net

Connection succeeded Service ssh Date: Fri, 21 Oct 2016 06:01:33 Action: alert Host: hexagon.federez.net Description: connection succeeded to INET[localhost:22] via TCP Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Connection succeeded fail2ban

par monit＠hexagon.federez.net

Connection succeeded Service fail2ban Date: Fri, 21 Oct 2016 06:01:24 Action: alert Host: hexagon.federez.net Description: connection succeeded to INET[localhost:22] via TCP Monit, unique employÃ© de federez,

8 années, 7 mois

monit alert -- Execution succeeded ssh

par monit＠hexagon.federez.net

Execution succeeded Service ssh Date: Fri, 21 Oct 2016 06:01:24 Action: alert Host: hexagon.federez.net Description: process is running after previous exec error (slow starting or manually recovered?) Monit, unique employÃ© de federez,

8 années, 7 mois

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Monitoring Octobre 2016