Times in UTC
```
23:59:01 <+icinga-wm> PROBLEM - Host backup2001 is DOWN: PING CRITICAL - Packet loss = 100%
00:00:21 <+icinga-wm> RECOVERY - Host backup2001 is UP: PING OK - Packet loss = 0%, RTA = 36.23 ms
```
```
root@backup2001:~# w
06:40:17 up 6:40, 1 user, load average: 0.08, 0.04, 0.00
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
marosteg pts/0 2620:0:860:2:208 06:40 1.00s 0.05s 0.02s sshd: marostegui [priv]
```
Looks like it rebooted itselifecycle log:
```lines=10
2019-12-08 23:57:49 SYS1003 System CPU Resetting.
Log Sequence Number:
1529
Detailed Description:
System is performing a CPU reset because of system power off, power on or a warm reset like CTRL-ALT-DEL.
Recommended Action:
No response action is required.
2019-12-08 23:57:39 SYS1000 System is turning on.
Log Sequence Number:
1528
Detailed Description:
System is turning on.
Recommended Action:
No response action is required.
2019-12-08 23:57:29 SYS1001 System is turning off.
Log Sequence Number:
1527
Detailed Description:
System is turning off.
Recommended Action:
No response action is required.
2019-12-08 23:57:29 SYS1003 System CPU Resetting.
Log Sequence Number:
1526
Detailed Description:
System is performing a CPU reset because of system power off, I haven't checked further,power on or a warm reset like CTRL-ALT-DEL.
Recommended Action:
No response action is required.
2019-12-08 23:57:12 RAC0703 Requested system hardreset.
Log Sequence Number:
1525
Detailed Description:
Requested system hardreset.
Recommended Action:
No response action is required.
2019-12-08 23:57:08 CPU0000 Internal error has occurred check for additional logs.
Log Sequence Number:
1524
Detailed Description:
System event log and OS logs may indicate the source of the error.
Recommended Action:
Review System Event Log and Operating System Logs. creating this task to follow upThese logs can help the user identify the possible issue that is producing the problem.
```