[SOLVED] boot runs into Debian GNU - I want to avoid this

schnellschuss

Member
Jun 2, 2020
7
1
8
51
Hi,

after changeing my hardware that I used for the pbs (was: Acer easystore h340 with atom CPU, 2GB RAM; now: Fujitsu P900 with i5 CPU, 16GB to come) I ran into issues. The system boots nicely, I have a monitor to see the procedure and the system starts the Debian GNU/ Linux. As a consequence, the system has it´s own behavior of suspending (which seems to make the server unavailabe on the network). With my prior setup on the easystore, this did not occur - I also followd that on the attached monitor.

While I have of course tried to shut off all kind of energy/power management in both, the BIOS and the Debian GNU, the server still runs into a kind of suspend mode, which is not suitable to my scheduling of tasks and booting/ shutting down intentionally by Magic Paket/ cron.

I am now wondering if I may have missed the option where I could choose, whether or not to boot into the Debian GNU? Any help for that as well as supporting material I can read into (did not find the solution in the manual so far) is well appreciated!
 
Hi,

did you install proxmox from the ISO? Can you check what your log says at the such a suspend happened the last time, just edit the date in this command:

Code:
journalctl --since "2022-05-31 16:00:00"
 
Hi,

thanks for the reply. I have checked out and it seems to come from the network manager - not so familiar still with Linux...please see the relevant part from systemctl:

Code:
Jun 01 10:21:33 backserv proxmox-backup-api[1395]: Detected stopped task 'UPID:backserv:00000573:000011A2:00000001:62972160:termproxy::root@pam:'
Jun 01 10:21:33 backserv systemd[1]: session-5.scope: Succeeded.
Jun 01 10:21:33 backserv systemd-logind[1127]: Removed session 5.
Jun 01 10:21:34 backserv audit[1236]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" de
Jun 01 10:21:34 backserv kernel: audit: type=1400 audit(1654071694.673:1248): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" p
Jun 01 10:21:35 backserv audit[1236]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" de
Jun 01 10:21:35 backserv kernel: audit: type=1400 audit(1654071695.669:1249): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" p
Jun 01 10:21:36 backserv audit[1236]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" de
Jun 01 10:21:36 backserv kernel: audit: type=1400 audit(1654071696.673:1250): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" p
Jun 01 10:21:37 backserv audit[1236]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" de
Jun 01 10:21:37 backserv kernel: audit: type=1400 audit(1654071697.673:1251): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" p
Jun 01 10:21:38 backserv NetworkManager[1125]: <info>  [1654071698.5160] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 01 10:21:38 backserv NetworkManager[1125]: <info>  [1654071698.5160] manager: NetworkManager state is now ASLEEP
Jun 01 10:21:38 backserv gnome-shell[1519]: Screen lock is locked down, not locking
Jun 01 10:21:38 backserv systemd[1]: Reached target Sleep.
Jun 01 10:21:38 backserv systemd[1]: Starting Suspend...
Jun 01 10:21:38 backserv systemd-sleep[2332]: Suspending system...
Jun 01 10:21:38 backserv kernel: PM: suspend entry (deep)
Jun 01 10:21:38 backserv audit[1236]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" de
Jun 01 10:21:38 backserv kernel: audit: type=1400 audit(1654071698.669:1252): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=1236 comm="cups-browsed" family="unix" sock_type="stream" p
Jun 01 10:23:14 backserv kernel: Filesystems sync: 0.257 seconds
Jun 01 10:23:14 backserv kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jun 01 10:23:14 backserv kernel: OOM killer disabled.
Jun 01 10:23:14 backserv kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun 01 10:23:14 backserv kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 01 10:23:14 backserv kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Jun 01 10:23:14 backserv kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 01 10:23:14 backserv kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jun 01 10:23:14 backserv kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Jun 01 10:23:14 backserv kernel: sd 0:0:0:0: [sda] Stopping disk
Jun 01 10:23:14 backserv kernel: sd 3:0:0:0: [sdc] Stopping disk
Jun 01 10:23:14 backserv kernel: sd 4:0:0:0: [sdd] Stopping disk
Jun 01 10:23:14 backserv kernel: sd 1:0:0:0: [sdb] Stopping disk
Jun 01 10:23:14 backserv kernel: parport_pc 00:05: disabled
Jun 01 10:23:14 backserv kernel: serial 00:04: disabled
Jun 01 10:23:14 backserv kernel: e1000e: EEE TX LPI TIMER: 00000011
Jun 01 10:23:14 backserv kernel: ACPI: Preparing to enter system sleep state S3
Jun 01 10:23:14 backserv kernel: PM: Saving platform NVS memory
Jun 01 10:23:14 backserv kernel: Disabling non-boot CPUs ...
Jun 01 10:23:14 backserv kernel: smpboot: CPU 1 is now offline
Jun 01 10:23:14 backserv kernel: smpboot: CPU 2 is now offline
Jun 01 10:23:14 backserv kernel: smpboot: CPU 3 is now offline
Jun 01 10:23:14 backserv kernel: ACPI: Low-level resume complete
 
Last edited:
A bit intrigued by the solution I wanted to understand where the sleep trigger would come from, this post [0] hints to run systemd-inhibit, which is the same as systemd-inhibit --list
And from man systemd-inhibit:
DESCRIPTION
systemd-inhibit may be used to execute a program with a shutdown,
sleep, or idle inhibitor lock taken. The lock will be acquired before
the specified command line is executed and released afterwards.
--list
Lists all active inhibition locks instead of acquiring one.

On a default proxmox install from iso you get:
No inhibitors.
On a debian gnome desktop install you get multiple inhibitors.

From your posted log:
Jun 01 10:21:38 backserv gnome-shell[1519]: Screen lock is locked down, not locking
So I assume that gnome-shell is installed afterwards or proxmox is installed on top of a debian gnome desktop install, both setting the multiple inhibitors, which will trigger sleep state.

[0] https://forums.debian.net/viewtopic.php?t=139752
 
Last edited:
  • Like
Reactions: shrdlicka

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!