CWP Pro: Server reboot occurrence

[fvnet]

Hello dear friends,
I am running CWP Pro on a Hetzner cloud and every now and then I login to check for any issues. In yesterday's login I saw that the server uptime is 1 day and some hours which puzzled me as the VM is running for almost 20 days without reboot.

In var\log\messages I spotted this

Code Select Expand


Aug 30 09:28:53 d1 qemu-ga: info: guest-shutdown called, mode: powerdown
Aug 30 09:28:53 d1 systemd: Started Delayed Shutdown Service.
Aug 30 09:28:53 d1 systemd: Starting Delayed Shutdown Service...
Aug 30 09:28:53 d1 systemd-shutdownd: Shutting down at Thu 2018-08-30 09:28:53 CEST (poweroff)...
Aug 30 09:28:53 d1 systemd-shutdownd: Creating /run/nologin, blocking further logins...
Aug 30 09:28:53 d1 systemd: Stopped Dump dmesg to /var/log/dmesg.
Aug 30 09:28:53 d1 systemd: Stopping Dump dmesg to /var/log/dmesg...
Aug 30 09:28:53 d1 systemd: Stopping clamd scanner () daemon...
Aug 30 09:28:53 d1 systemd: Stopped target Timers.
Aug 30 09:28:53 d1 systemd: Stopping Timers.
Aug 30 09:28:53 d1 systemd: Stopped Daily Cleanup of Temporary Directories.
Aug 30 09:28:53 d1 systemd: Stopping Daily Cleanup of Temporary Directories.
Aug 30 09:28:53 d1 systemd: Stopped Amavisd clean tmp timer.
Aug 30 09:28:53 d1 systemd: Stopping Amavisd clean tmp timer.
Aug 30 09:28:53 d1 systemd: Stopped Amavisd clean quarantine timer.
Aug 30 09:28:53 d1 systemd: Stopping Amavisd clean quarantine timer.
Aug 30 09:28:53 d1 systemd: Stopping Authorization Manager...
Aug 30 09:28:53 d1 systemd: Stopping QEMU Guest Agent...
Aug 30 09:28:53 d1 systemd: Stopping Session 3189 of user root.
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpuset
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpu
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpuacct
Aug 30 09:39:33 d1 kernel: Linux version 3.10.0-862.9.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Mon Jul 16 16:29:36 UTC 2018
Aug 30 09:39:33 d1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-862.9.1.el7.x86_64

I am attaching the screenshots and I am wondering is something that has to do with CWP or do I have to contact the provider?

https://www.dropbox.com/s/kavjhsiqtazlkvo/sc1.jpg?dl=0
https://www.dropbox.com/s/u26u0myc7mm0h2n/sc2.jpg?dl=0

[fvnet]

Hello again, I will answer it myself.
The provider (Hetzner) actually rebooted the hostnode due to a problem.

[ring_c]

Thanks, I'm in Hetzner too. Good to know...

[fvnet]

And by the way, it's the second time this has occurred.
You can check status here
https://www.hetzner-status.de/en.html
If you want to know your cloud node ID just tracert your servers IP.

[ring_c]

Thanks!