As you rebooted it ~2 hours ago, it should definitely be back online now. Let us know! 
If it isn't, you'll need to use a console or IPMI to check for any errors during the boot process.
If it isn't, you'll need to use a console or IPMI to check for any errors during the boot process.
Yes server back to online but the rebooting process does not show successfully completed massage.
Hello @Nirjonadda
Because the server literally reboots it's not going to show you a "reboot complete" message as far as I understand it. It's not like restarting a process.
Thanks!
Because the server literally reboots it's not going to show you a "reboot complete" message as far as I understand it. It's not like restarting a process.
Thanks!
This is the closest discussion that I can find regarding the issue I have with Graceful Reboot.
Our server is currently doing the reboot and it's annoying that it doesn't tell us that it's done rebooting. Or even go back to the main page. Reason why we rebooted is because there's a message on the upper right corner "You must reboot the server to apply software updates."
I waited for an hour or so. Still doing the reboot. And then tried logging out and back in to see if the server rebooted. The update message is still there. So I'm guessing it didn't reboot properly. Does this mean I have to do a Forceful Reboot? And is CPanel going to fix this issue about the server not confirming that reboot is done?
Last edited by a moderator:
You can see the uptime of the server at WHM>>Server Status>>Server Information to confirm whether or not the server was in fact rebooted - you can also run the command uptime over CLI to confirm this was completed or not.
You can also see specifically why it needs to be restarted/rebooted - the thread here should be helpful You must reboot the server to apply software updates
You can also see specifically why it needs to be restarted/rebooted - the thread here should be helpful You must reboot the server to apply software updates
I have a similar issue where the update message is still in the corner and I just rebooted the server not to long ago. Everything is up to date when I run various checks per documentation provided on the site.
/usr/bin/needs-restarting -r
Core libraries or services have been updated:
kernel -> 3.10.0-957.el7
linux-firmware -> 20180911-69.git85c5d90.el7
uname -r 3.10.0-957.12.2.el7.x86_64
uptime 23:39:09 up 20 min,
/usr/bin/needs-restarting -r
Core libraries or services have been updated:
kernel -> 3.10.0-957.el7
linux-firmware -> 20180911-69.git85c5d90.el7
uname -r 3.10.0-957.12.2.el7.x86_64
uptime 23:39:09 up 20 min,
Here is my ticket number 12392069, sorry for the delay in response it was kind of a busy week for me and for some reason I didn't see a notification of a reply.
I can confirm the same issue - but AFAIK it is only a UI/UX issue and server is booting just fine - so I have learned to ignore this message..
maybe can just add a logout / login script or a timer refresh.
maybe can just add a logout / login script or a timer refresh.
Actually what cpanel support found was that one of the packages that was installed had a time stamp in the future, causing the false positive so by reinstalling the package corrected the issue.
It looks like there may have been a time issue on the server when the package was installed causing it to appear to have been installed in 2020
You might check the time on the server now and ensure it's set correctly. Otherwise, I'm glad the issue is resolved for you now.
Code:
================================
[01:33:33 server2 [email protected] ~]cPs# rpm -qi linux-firmware-20180911-69.git85c5d90.el7.noarch|grep Install
Install Date: Thu 20 Feb 2020 04:12:26 PM EST
================================When I go to WHM -> Server Status -> Server Information, where on that page can you tell if the server has been rebooted? I don't see any times or dates. What section would it be in? Or is there any other way to tell through WHM or cPanel?
You see it in WHM -> Server Status -> Apache Status:
" Server uptime: 4 days 5 hours 7 minutes 57 seconds "
The Apache status uptime is not necessarily the same as the entire server's uptime. Here's an example from my personal system:
I'd recommend using "uptime" on the command line of the server (or through the WHM >> Terminal function) as there is not a specific area of the interface that displays this value.
Code:
[[email protected] /]# uptime
10:33:09 up 9 days, 12:14, 1 user, load average: 0.01, 0.04, 0.05
[[email protected] /]# apachectl status | grep uptime
Server uptime: 7 hours 40 minutes 10 seconds
[[email protected] /]# uptime
10:33:40 up 9 days, 12:15, 1 user, load average: 0.01, 0.04, 0.05