VPS Crashes Every 24 Hours - No Logs?

James.Simpson

Member
Feb 18, 2013
22
0
1
United Kingdom
cPanel Access Level
Root Administrator
Hi All,

After a bit of help with this one, as I'm pretty stuck as to what is causing the fault. I have checked all the logs I can think of, and there is nothing in any of them to suggest what is causing the VPS to turn itself off.

For example - messages log:
Code:
Feb 16 02:08:33 vps-8250c3 kernel: [63610.912936] Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:52:54:00:22:fd:13:08:00 SRC=185.151.29.33 DST=185.151.29.255 LEN=49 TOS=0x00 PREC=0x00 TTL=64 ID=36504 DF PROTO=UDP SPT=41229 DPT=32412 LEN=29
Feb 16 02:08:33 vps-8250c3 kernel: [63610.913899] Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:52:54:00:22:fd:13:08:00 SRC=185.151.29.33 DST=185.151.29.255 LEN=49 TOS=0x00 PREC=0x00 TTL=64 ID=36505 DF PROTO=UDP SPT=42134 DPT=32414 LEN=29
Feb 16 07:23:33 vps-8250c3 kernel: imklog 5.8.10, log source = /proc/kmsg started.
Feb 16 07:23:33 vps-8250c3 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1464" x-info="http://www.rsyslog.com"] start
Feb 16 07:23:33 vps-8250c3 kernel: Initializing cgroup subsys cpuset
Feb 16 07:23:33 vps-8250c3 kernel: Initializing cgroup subsys cpu
Feb 16 07:23:33 vps-8250c3 kernel: Linux version 2.6.32-696.20.1.el6.x86_64 ([email protected]_64_01.bsys.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Fri Jan 26 17:51:45 UTC 2018
As you can see, the server crashed/turned off around 2:08am till i manually went in and started the VPS again at 7:23am this morning.

It has been doing it over the last week, and I've been puzzled as to the cause, and cannot find anything that may be causing it - not sure if there is a memory spike.

The only thing i could possibly think is maybe the backups are causing it to crash? As there is a massive 3GB database in use on the server, but can't seem to find any log files for that?
 

James.Simpson

Member
Feb 18, 2013
22
0
1
United Kingdom
cPanel Access Level
Root Administrator
Doesnt look like there was anything running on a cron at the time of crash either

Code:
Feb 16 02:01:01 vps-8250c3 CROND[24855]: (root) CMD (run-parts /etc/cron.hourly)
Feb 16 02:01:01 vps-8250c3 run-parts(/etc/cron.hourly)[24855]: starting 0anacron
Feb 16 02:01:01 vps-8250c3 anacron[24866]: Anacron started on 2018-02-16
Feb 16 02:01:01 vps-8250c3 anacron[24866]: Jobs will be executed sequentially
Feb 16 02:01:01 vps-8250c3 anacron[24866]: Normal exit (0 jobs run)
Feb 16 02:01:01 vps-8250c3 run-parts(/etc/cron.hourly)[24868]: finished 0anacron
Feb 16 02:05:01 vps-8250c3 CROND[25212]: (root) CMD (/usr/local/cpanel/scripts/eximstats_spam_check 2>&1)
Feb 16 02:05:01 vps-8250c3 CROND[25214]: (root) CMD (/usr/local/cpanel/scripts/dcpumon-wrapper >/dev/null 2>&1)
Feb 16 07:23:38 vps-8250c3 crond[2459]: (CRON) STARTUP (1.4.4)
Feb 16 07:23:38 vps-8250c3 crond[2459]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 46% if used.)
Feb 16 07:23:38 vps-8250c3 crond[2459]: (CRON) INFO (running with inotify support)
Feb 16 07:23:38 vps-8250c3 CROND[2473]: (root) CMD (/usr/local/cpanel/bin/onboot_handler)
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,205
363
Hi James,

Have you reached out to your VPS hosting provider to verify if the reboot is stemming from an issue with the VPS hardware node itself?

Thank you.