Monitoring

monitoring@federez.net

5453 discussions

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

par root＠baldrick.crans.org

/etc/cron.daily/duplicity-backup: BackendException: ssh connection to duplicity@hexagon.federez.net:22 failed: [Errno 113] No route to host BackendException: ssh connection to duplicity@hexagon.federez.net:22 failed: [Errno 113] No route to host

9 années, 12 mois

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

par root＠hexagon.federez.net

/etc/cron.daily/duplicity-backup: ssh: Exception: Incompatible ssh peer (no acceptable kex algorithm) ssh: Traceback (most recent call last): ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1546, in run ssh: self._handler_table[ptype](self, m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1618, in _negotiate_keys ssh: self._parse_kex_init(m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1731, in _parse_kex_init ssh: raise SSHException('Incompatible ssh peer (no acceptable kex algorithm)') ssh: SSHException: Incompatible ssh peer (no acceptable kex algorithm) ssh: BackendException: ssh connection to 138.231.142.239:22 failed: Incompatible ssh peer (no acceptable kex algorithm) ssh: Exception: Incompatible ssh peer (no acceptable kex algorithm) ssh: Traceback (most recent call last): ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1546, in run ssh: self._handler_table[ptype](self, m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1618, in _negotiate_keys ssh: self._parse_kex_init(m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1731, in _parse_kex_init ssh: raise SSHException('Incompatible ssh peer (no acceptable kex algorithm)') ssh: SSHException: Incompatible ssh peer (no acceptable kex algorithm) ssh: BackendException: ssh connection to 138.231.142.239:22 failed: Incompatible ssh peer (no acceptable kex algorithm)

9 années, 12 mois

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

par root＠quigon.rez-gif.supelec.fr

/etc/cron.daily/duplicity-backup: ssh: Exception: Incompatible ssh peer (no acceptable kex algorithm) ssh: Traceback (most recent call last): ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1546, in run ssh: self._handler_table[ptype](self, m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1618, in _negotiate_keys ssh: self._parse_kex_init(m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1731, in _parse_kex_init ssh: raise SSHException('Incompatible ssh peer (no acceptable kex algorithm)') ssh: SSHException: Incompatible ssh peer (no acceptable kex algorithm) ssh: BackendException: ssh connection to baldrick.federez.net:22 failed: Incompatible ssh peer (no acceptable kex algorithm) ssh: Exception: Incompatible ssh peer (no acceptable kex algorithm) ssh: Traceback (most recent call last): ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1546, in run ssh: self._handler_table[ptype](self, m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1618, in _negotiate_keys ssh: self._parse_kex_init(m) ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 1731, in _parse_kex_init ssh: raise SSHException('Incompatible ssh peer (no acceptable kex algorithm)') ssh: SSHException: Incompatible ssh peer (no acceptable kex algorithm) ssh: BackendException: ssh connection to baldrick.federez.net:22 failed: Incompatible ssh peer (no acceptable kex algorithm)

9 années, 12 mois

monit alert -- Timeout fail2ban

par monit＠baldrick.crans.org

Timeout Service fail2ban Date: Sat, 02 May 2015 00:19:55 Action: unmonitor Host: baldrick.crans.org Description: service restarted 5 times within 5 cycles(s) - unmonitor Monit, unique employÃ© de federez,

9 années, 12 mois

monit alert -- Execution failed fail2ban

par monit＠baldrick.crans.org

Execution failed Service fail2ban Date: Sat, 02 May 2015 00:17:25 Action: alert Host: baldrick.crans.org Description: failed to start (exit status 0) -- /etc/init.d/fail2ban: Starting authentication failure monitor: fail2ban. Monit, unique employÃ© de federez,

9 années, 12 mois

monit alert -- Does not exist fail2ban

par monit＠baldrick.crans.org

Does not exist Service fail2ban Date: Sat, 02 May 2015 00:16:55 Action: restart Host: baldrick.crans.org Description: process is not running Monit, unique employÃ© de federez,

9 années, 12 mois

monit alert -- Execution failed fail2ban

par monit＠baldrick.crans.org

Execution failed Service fail2ban Date: Sat, 02 May 2015 00:13:03 Action: alert Host: baldrick.crans.org Description: failed to start (exit status 0) -- /etc/init.d/fail2ban: Starting authentication failure monitor: fail2ban. Monit, unique employÃ© de federez,

9 années, 12 mois

monit alert -- Does not exist fail2ban

par monit＠baldrick.crans.org

Does not exist Service fail2ban Date: Sat, 02 May 2015 00:12:32 Action: restart Host: baldrick.crans.org Description: process is not running Monit, unique employÃ© de federez,

9 années, 12 mois

*** SECURITY information for baldrick ***

par root＠baldrick.crans.org

baldrick : May 2 00:06:11 : root : parse error in /etc/sudoers.d/apt-dater-host near line 1 ; TTY=ttyS0 ; PWD=/home/detraz ;

9 années, 12 mois

*** SECURITY information for baldrick.crans.org ***

par detraz＠baldrick.crans.org

baldrick.crans.org : May 2 00:02:38 : detraz : user NOT in sudoers ; TTY=ttyS0 ; PWD=/home/detraz ; USER=root ; COMMAND=/bin/su

9 années, 12 mois

Aller à la page :

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Monitoring