Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-16 Thread James Hogarth
On 15 October 2017 at 12:20, Mike <1100...@gmail.com> wrote: > On Sat, Oct 14, 2017 at 2:29 PM, Vitalino Victor > wrote: > > > > Try: > > > > # shutdown -r now > > > > I'll have to try this late one evening. > It's a production Samba Active Directory Domain Controller in >

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-15 Thread Mike
It turns out kdump.service is already enabled on the server and /etc/kdump.conf settings would report any kernel crash/error items to /var/crash. The /var/crash file/folder is empty. It leads me to think the kernel is not crashing; however, I could be wrong. I'll need to perform another test

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-15 Thread Mike
Thank you for your thoughtful responses. Very much appreciated. Good points to follow up with. Kind regards, Mike ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-15 Thread Mike
On Sat, Oct 14, 2017 at 6:24 PM, Jonathan Billings wrote: > > When you say that the monitor is plugged in, and the server is unresponsive, > does that mean that the monitor doesn’t even come active? That sounds like > it might have crashed the kernel in a way that the

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-15 Thread Mike
cat /etc/centos-release: CentOS Linux release 7.4.1708 (Core) The bugzilla report does sound similar --- in one of the comments, a user reports hang-up when trying remote reboot. ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-15 Thread Mike
On Sat, Oct 14, 2017 at 2:29 PM, Vitalino Victor wrote: > > Try: > > # shutdown -r now > I'll have to try this late one evening. It's a production Samba Active Directory Domain Controller in production so it's difficult to do this without warning to users.

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Jonathan Billings
On Oct 14, 2017, at 1:54 PM, Mike <1100...@gmail.com> wrote: > Server disconnects my ssh connection and never comes back up. > Go to the server and the power is on but the server is not accessible by ssh. > When I connect a monitor and keyboard --- non-responsive. It's like > it's in suspend

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread John R Pierce
On 10/14/2017 10:54 AM, Mike wrote: When I try systemctl reboot directly on the server. Same problem --- does not start to login prompt. so where does it stop?   does it never finish BIOS short self-test after the shutdown?   does it hang somewhere in the Linux loading sequence?   if it goes

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Alexander Dalloz
Am 14.10.2017 um 19:54 schrieb Mike: Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 The version is a bit unprecise. Are you fully updated? On 7.3 and 7.4 I haven't seen that issue. from ~$root ---

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Vitalino Victor
Hi, I have this problem! Try: # shutdown -r now For a test, please... 2017-10-14 14:54 GMT-03:00 Mike <1100...@gmail.com>: > Hi, > > Such a simple problem, but I can't figure out the cause. > Supermicro server with a Xeon E3-1200 cpu. > 1U entry level item. > > Using CentOS 7 > > from

[CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Mike
Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 from ~$root --- systemctl reboot Server disconnects my ssh connection and never comes back up. Go to the server and the power is on but the server is not