Workstation Uninstructed Reboot

General support questions
desertcat
Posts: 843
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Workstation Uninstructed Reboot

Post by desertcat » 2019/10/07 16:49:15

CaveDann wrote:
2019/10/07 09:57:14
Hey All,

Thanks again for the support on this.

I can confirm, all the fans are clear and running.

Also, my /etc/systemd/logind.conf still holds the default configuration. All lines are commented out, no lines have been added or edited. I know it's commented, so it wouldn't have an effect anyway, but for the sake of clarity the line in question reads #IdleAction=ignore.

Still, thanks for the suggestion. It wasn't a line I'd caught and googled before.

If I find anything else, I'll update here. If anyone has any other questions or ideas, they're obviously more than welcome!

Cheers,
CD
Hummmmmmm Mysterious and more Mysterious. Which brings me back to Dirty Power. Do you have it plugged into a UPS?!? A Surge Protector?!? Or just the Wall Outlet?!?

lightman47
Posts: 1522
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Workstation Uninstructed Reboot

Post by lightman47 » 2019/10/07 17:24:39

Solely to clarify:
This has happened on all of CentOS 6.6, 6.7, 6.9 and now 7.6 too. Posting to CentOS 7 General as 7 is the desired OS for this PC.
This is a multi-boot machine with all these installations, and all suffer the problem when running? Or is this one machine with these VMs on it?

Thank you.

CaveDann
Posts: 27
Joined: 2018/12/14 15:05:27
Location: U.K.

Re: Workstation Uninstructed Reboot

Post by CaveDann » 2019/10/09 07:55:36

Hey D'Cat, Lightman,

It's not plugged into a UPS, just a surge protected wall outlet.

The machine itself has only CentOS 7 installed on it at present. It has only ever had a single OS installed on it. I don't use VM's with it.

Hope that clarifies the situation I'm dealing with.

Cheers,
CD

lightman47
Posts: 1522
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Workstation Uninstructed Reboot

Post by lightman47 » 2019/10/09 12:03:36

Yeh - unless it's some BIOS sleep timer (if there is such a thing), I'm suspecting some system hardware issue.

CaveDann
Posts: 27
Joined: 2018/12/14 15:05:27
Location: U.K.

Re: Workstation Uninstructed Reboot

Post by CaveDann » 2019/10/10 08:28:04

lightman47 wrote:
2019/10/09 12:03:36
Yeh - unless it's some BIOS sleep timer (if there is such a thing), I'm suspecting some system hardware issue.
Ditto. I'm going to leave it in the BIOS boot menu for a month, maybe a little more. If it turns off in this time and boots to CentOS, then it surely has to be hardware or environmental. Either way, that should rule out OS issues.

User avatar
TrevorH
Site Admin
Posts: 33219
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Workstation Uninstructed Reboot

Post by TrevorH » 2019/10/10 08:52:22

You could also download and run memtest86+ on it for a few days. That should add a bit of stresss to it.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

tony_down_under
Posts: 83
Joined: 2019/08/07 01:50:24
Location: Perth, Australia but originally from Carshalton, Surrey

Re: Workstation Uninstructed Reboot

Post by tony_down_under » 2019/11/12 01:17:24

desertcat wrote:
2019/10/05 22:59:19
Hummmnm. If you have dirty power it will not be solved by moving it to a different power outlet. The question was "Do you have access to a UPS"? This still sounds like a "hiccup" in the power supply -- just enough to shut it down but then immediately re-boot. Maybe like in a "Brown Out" such as it goes into a LOG OUT rather than a SHUT DOWN mode.
Nice idea but as far as I know we dont generally get that kind of thing in the UK. Still, wouldnt hurt to rule it out :)
TrevorH wrote:
2019/10/06 12:06:48
Sep 24 11:19:13 proto systemd-logind: Delay lock is active (UID <removed>, PID <removed>) but inhibitor timeout is reached.
Sep 24 11:19:13 proto systemd-logind: System is powering down.
Googling those leads to https://www.freedesktop.org/software/sy ... .conf.html and I think it's doing that because you have IdleAction=poweroff in /etc/systemd/logind.conf and it thinks your system is idle because one of the processes that was killed was the one it was looking at to determine if the system was idle.
Nice find :)

Post Reply