Thanks, Pat, but is seems to be disabled there. With all these magic interactions between gnome-settings, systemd, gdm/lightdm, etc, I sense a conspiracy to turn linux into windows.
I do see the setting for "go to suspend" if power button is activated, it should be "go to power-off", or even better, "do nothing", if you ask me. Machine should not do something drastic without confirmation if somebody hits a front panel button by mistake. (long press to hard-power-off is okey by me). [root@daqbackup ~]# gsettings list-recursively org.gnome.settings-daemon.plugins.power org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power active true [root@daqbackup ~]# K.O. On Thu, Mar 09, 2017 at 01:35:26PM -0600, Pat Riehecky wrote: > I've seen GDM suspending the box after too much time without > interaction. My fix: > > echo '[org.gnome.settings-daemon.plugins.power]' > > /usr/share/glib-2.0/schemas/disable_powermgmt.gschema.override > echo sleep-inactive-ac-timeout=0 >> > /usr/share/glib-2.0/schemas/disable_powermgmt.gschema.override > echo idle-dim=false >> > /usr/share/glib-2.0/schemas/disable_powermgmt.gschema.override > > glib-compile-schemas /usr/share/glib-2.0/schemas > > > Pat > > > > > On 03/09/2017 12:14 PM, Konstantin Olchanski wrote: > >Hi, there. I wonder if anybody else is seeing the same problem with el7: > > > >The symptoms are: no ping, dead video, dead keyboard. After power cycle, > >syslog shows that the system has attempted to go into sleep or suspend > >or whatever they call it. > > > >This is very strange, usualy a system will go into suspend mode when you > >close the laptop lid, but these are not laptops. They are normal desktop > >machines (and at least in one case, there is no local user to blame for > >pressing the "sleep" button). > > > >So what's in the syslog: > >- normal activity (systemd spam) > >- network manager reports "sleep requested" > >- some kind of nm_dispatcher activity > >- systemd reaches sleep and suspend targets. > >- continues spewing sundry messages, never recovers (never goes into actual > >sleep). > > > >The machine is effectively dead after network manager put the network > >interfaces to sleep. > > > >The best google-advice I see it to disable the systemd sleep and suspend > >targets: > >systemctl mask sleep.target suspend.target hibernate.target > >hybrid-sleep.target systemd-suspend.service systemd-hybrid-sleep.service > >(now waiting for this machine to go to sleep). > > > >It is very worrysome that the syslog does not say who initiated the > >sleep/suspend sequence. > > > >That would be a show stopper for el7 - servers randomly going offline into > >uncommanded sleep/suspend. > >It does seem to happen rarely, but I have seen 3 or 4 machines do it at > >least once, so not rare enough. > > > >Any ideas? > > > > > >K.O. > > > > > >Here is the syslog contents: > > > >Mar 3 15:50:01 daqbackup systemd: Starting Session 1599 of user root. > >Mar 3 15:50:01 daqbackup systemd: Started Session 1602 of user root. > >Mar 3 15:50:01 daqbackup systemd: Starting Session 1602 of user root. > >Mar 3 15:50:16 daqbackup NetworkManager[1076]: <info> [1488585016.1046] > >manager: sleep > >requested (sleeping: no enabled: yes) > >Mar 3 15:50:16 daqbackup NetworkManager[1076]: <info> [1488585016.1052] > >manager: > >sleeping... > >Mar 3 15:50:16 daqbackup NetworkManager[1076]: <info> [1488585016.1061] > >manager: > >NetworkManager state is now ASLEEP > >Mar 3 15:50:16 daqbackup dbus-daemon: dbus[846]: [system] Activating via > >systemd: service > >name='org.freedesktop.nm_dispatcher' > >unit='dbus-org.freedesktop.nm-dispatcher.service' > >Mar 3 15:50:16 daqbackup dbus[846]: [system] Activating via systemd: service > >name='org.freedesktop.nm_dispatcher' > >unit='dbus-org.freedesktop.nm-dispatcher.service' > >Mar 3 15:50:16 daqbackup systemd: Cannot add dependency job for unit > >microcode.service, > >ignoring: Unit is not loaded properly: Invalid argument. > >Mar 3 15:50:16 daqbackup systemd: Starting Network Manager Script > >Dispatcher Service... > >Mar 3 15:50:16 daqbackup dbus-daemon: dbus[846]: [system] Successfully > >activated service > >'org.freedesktop.nm_dispatcher' > >Mar 3 15:50:16 daqbackup dbus[846]: [system] Successfully activated service > >'org.freedesktop.nm_dispatcher' > >Mar 3 15:50:16 daqbackup systemd: Started Network Manager Script Dispatcher > >Service. > >Mar 3 15:50:16 daqbackup nm-dispatcher: req:1 'connectivity-change': new > >request (4 scripts) > >Mar 3 15:50:16 daqbackup nm-dispatcher: req:1 'connectivity-change': start > >running ordered > >scripts... > >Mar 3 15:50:21 daqbackup systemd-logind: Delay lock is active (UID 42/gdm, > >PID 3237/gnome- > >shell) but inhibitor timeout is reached. > >Mar 3 15:50:21 daqbackup systemd: Reached target Sleep. > >Mar 3 15:50:21 daqbackup systemd: Starting Sleep. > >Mar 3 15:50:21 daqbackup systemd: Starting Suspend... > >Mar 3 15:50:21 daqbackup systemd-sleep: Suspending system... > >Mar 3 15:54:11 daqbackup kernel: PM: Syncing filesystems ... done. > >Mar 3 15:54:11 daqbackup kernel: Freezing user space processes ... (elapsed > >0.046 seconds) > >done. > > > > -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
