All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Why so many reboots?
So I am seeing my KS server is going under reboots way too many times. Is it possible to help detect why? What should I be checking the root cause? I have CentOS7 installed, and nothing more.
I will go to KS support, but, I wanna see if I can figure out why...
[root@ns ~]# last | grep reboot reboot system boot 3.14.32-xxxx-grs Mon Aug 22 18:39 - 20:20 (01:41) reboot system boot 3.14.32-xxxx-grs Mon Aug 22 17:00 - 20:20 (03:19) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 16:25 - 20:20 (1+03:55) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 16:23 - 20:20 (1+03:57) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 14:26 - 20:20 (1+05:54) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 14:23 - 20:20 (1+05:57) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 14:19 - 20:20 (1+06:01) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 14:15 - 20:20 (1+06:05) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 14:12 - 20:20 (1+06:07) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 13:45 - 20:20 (1+06:34) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 12:06 - 20:20 (1+08:14) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 12:04 - 20:20 (1+08:15) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 11:55 - 20:20 (1+08:24) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 10:24 - 20:20 (1+09:56) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 09:08 - 20:20 (1+11:12) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 09:05 - 20:20 (1+11:15) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 09:02 - 20:20 (1+11:18) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 08:54 - 20:20 (1+11:26) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 08:49 - 20:20 (1+11:31) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 08:47 - 20:20 (1+11:33) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 08:40 - 20:20 (1+11:40) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 06:04 - 20:20 (1+14:16) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 05:57 - 20:20 (1+14:23) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 05:05 - 20:20 (1+15:15) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 05:00 - 20:20 (1+15:20) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 04:46 - 20:20 (1+15:33) reboot system boot 3.14.32-xxxx-grs Sun Aug 21 01:33 - 20:20 (1+18:47) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 23:31 - 20:20 (1+20:49) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 22:37 - 20:20 (1+21:42) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 21:18 - 20:20 (1+23:01) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 21:07 - 20:20 (1+23:12) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 20:59 - 20:20 (1+23:21) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 20:15 - 20:20 (2+00:05) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 20:11 - 20:20 (2+00:09) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 19:07 - 20:20 (2+01:13) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 16:05 - 20:20 (2+04:15) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:45 - 20:20 (2+04:35) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:41 - 20:20 (2+04:38) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:38 - 20:20 (2+04:42) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:33 - 20:20 (2+04:47) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:29 - 20:20 (2+04:51) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:21 - 20:20 (2+04:59) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:19 - 20:20 (2+05:01) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 15:10 - 20:20 (2+05:10) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 14:53 - 20:20 (2+05:27) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 14:49 - 20:20 (2+05:31) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 14:47 - 20:20 (2+05:33) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 14:35 - 20:20 (2+05:45) reboot system boot 3.14.32-xxxx-grs Sat Aug 20 12:58 - 20:20 (2+07:22) reboot system boot 3.14.32-xxxx-grs Thu Aug 18 22:58 - 20:20 (3+21:22) [root@ns ~]#
Comments
If it isn't the DC doing something then I'd say failing PSU.
Francisco
Support just did a maintenance and "stress test" which came up with no issues. Phew, not sure what do I do now...
@francisco: anything I can do to trace the error to its core?
Check your logs in
/var/log/. Rundmesgand check for any warnings/errors. Runjournalctl -xeif you have systemd/journald.System goes down at 20:20 each time? I'm kinda on lack of sleep
Thanks. Will check.
I am seeing that too... Not sure how to interpret this output
This might be long shot, but are you sure you don't have anything in cron setup for 20:20 precisely ? It's too precise to be done manually.
Whats your provider.
What do you rin on your centos maybe they restart tour server on or long term cpu usage.
But if you have a clean installed os then idk.
Edit: i noted that too every 20:20
It's in the OP. Please read before responding...
Yea ok sorry for that then.
KS = KloudServer
British garbage
Link pleaese there not findable here on google.
KimSufi
@plumberg check acces logs. Maybe you have a bot doing it. (Just an idea it doesnt need to be this but why wint you check it)
I would check all the cron stuff. so crontab, /etc/cron.d. Also incron.
After that look for external access in logs.
After that maybe watch top and see what processes are running and watch for memory changes. If this is KVM then run slabtop to see what the kernel memory is doing.
My best guess also goes for Cron. Seems like some cron job is effed up