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?!?CaveDann wrote: ↑2019/10/07 09:57:14Hey 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
Workstation Uninstructed Reboot
Re: Workstation Uninstructed Reboot
-
- Posts: 1522
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Re: Workstation Uninstructed Reboot
Solely to clarify:
Thank you.
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?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.
Thank you.
Re: Workstation Uninstructed Reboot
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
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
-
- Posts: 1522
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Re: Workstation Uninstructed Reboot
Yeh - unless it's some BIOS sleep timer (if there is such a thing), I'm suspecting some system hardware issue.
Re: Workstation Uninstructed Reboot
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.lightman47 wrote: ↑2019/10/09 12:03:36Yeh - unless it's some BIOS sleep timer (if there is such a thing), I'm suspecting some system hardware issue.
Re: Workstation Uninstructed Reboot
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
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
-
- Posts: 83
- Joined: 2019/08/07 01:50:24
- Location: Perth, Australia but originally from Carshalton, Surrey
Re: Workstation Uninstructed Reboot
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 outdesertcat wrote: ↑2019/10/05 22:59:19Hummmnm. 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 findTrevorH wrote: ↑2019/10/06 12:06:48Googling 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.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.