How do I keep my server from "sleeping". It shuts down, but power light is still on and nothing will bring it back except power cycling. I've tried everything I can find on disabling sleep and hibernation but it still keeps "sleeping". What good is a web server that doesn't stay up and running?
On Sat, 25 Feb 2023 at 12:00, jdwirtz@cox.net wrote:
How do I keep my server from "sleeping". It shuts down, but power light is still on and nothing will bring it back except power cycling. I've tried everything I can find on disabling sleep and hibernation but it still keeps "sleeping". What good is a web server that doesn't stay up and running?
Sleeping isn't normal behaviour for either Alma8 or Alma9 installed servers. When the system comes back on is there anything in the logs which says why it shut itself down. Reasons it might happen are:
additional configs or settings which make the system think it is a workstation system didn't shutdown but had a hard crash due to thermal, memory or other hardware problem
AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
I've installed it has server with gui. So maybe it does think it's a workstation? Didn't see much in the log, just stopped reporting at 1 this morning then started up with booting messages.
Mar 1 00:40:23 alma1 systemd[1]: dnf-makecache.service: Consumed 5.871s CPU time. Mar 1 01:04:02 alma1 cupsd[1117]: REQUEST localhost - - "POST / HTTP/1.1" 200 185 Renew-Subscription successful-ok Mar 1 01:04:07 alma1 cupsd[1117]: REQUEST localhost - - "POST / HTTP/1.1" 200 182 Renew-Subscription successful-ok Mar 1 07:36:14 alma1 kernel: Linux version 5.14.0-162.12.1.el9_1.x86_64 (mockbuild@x64-builder01.almalinux.org) (gcc (GCC) 11.3.1 20220421 (Red Hat 11.3.1-2), GNU ld version 2.35.2-24.el9) #1 SMP PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 Mar 1 07:36:14 alma1 kernel: The list of certified hardware and cloud instances for Red Hat Enterprise Linux 9 can be viewed at the Red Hat Ecosystem Catalog, https://catalog.redhat.com. Mar 1 07:36:14 alma1 kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-162.12.1.el9_1.x86_64 root=/dev/mapper/almalinux-root ro resume=/dev/mapper/almalinux-swap rd.lvm.lv=almalinux/root rd.lvm.lv=almalinux/swap rhgb quiet Mar 1 07:36:14 alma1 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Mar 1 07:36:14 alma1 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 1 07:36:14 alma1 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 1 07:36:14 alma1 kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'compacted' format.
On Wed, 1 Mar 2023 at 12:07, jdwirtz@cox.net wrote:
I've installed it has server with gui. So maybe it does think it's a workstation? Didn't see much in the log, just stopped reporting at 1 this morning then started up with booting messages.
Mar 1 00:40:23 alma1 systemd[1]: dnf-makecache.service: Consumed 5.871s CPU time. Mar 1 01:04:02 alma1 cupsd[1117]: REQUEST localhost - - "POST / HTTP/1.1" 200 185 Renew-Subscription successful-ok Mar 1 01:04:07 alma1 cupsd[1117]: REQUEST localhost - - "POST / HTTP/1.1" 200 182 Renew-Subscription successful-ok
That looks like a hard crash with the system. If the system is powering down due to inactivity, I believe there are logs to say that is what is happening. The CPU reporting that it can trap split locks says it is pretty new so I would look to see if there are firmware updates for the system. I would also check to see if there any power settings in the EFI firmware which might put the hardware to sleep. [That is about all I have on my bucket list of things to do.. hope someone else can chime in.]
Mar 1 07:36:14 alma1 kernel: Linux version 5.14.0-162.12.1.el9_1.x86_64 ( mockbuild@x64-builder01.almalinux.org) (gcc (GCC) 11.3.1 20220421 (Red Hat 11.3.1-2), GNU ld version 2.35.2-24.el9) #1 SMP PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 Mar 1 07:36:14 alma1 kernel: The list of certified hardware and cloud instances for Red Hat Enterprise Linux 9 can be viewed at the Red Hat Ecosystem Catalog, https://catalog.redhat.com. Mar 1 07:36:14 alma1 kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-162.12.1.el9_1.x86_64 root=/dev/mapper/almalinux-root ro resume=/dev/mapper/almalinux-swap rd.lvm.lv=almalinux/root rd.lvm.lv=almalinux/swap rhgb quiet Mar 1 07:36:14 alma1 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Mar 1 07:36:14 alma1 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87
floating point registers' Mar 1 07:36:14 alma1 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 1 07:36:14 alma1 kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'compacted' format. _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
Thanks... I'm trying to run this on a Beelink Mini PC, Mini S Intel 11th Gen 4-Cores N5095, Mini Desktop Computer 8GB DDR4 RAM 256GB SSD Overall it working, but I guess it is randomly crashing?
It definitely sounds to me like something is crashing - especially if the power light is on but the only way to wake the system is through a hard reboot.
Anything in /var/log/messages for power, kernel, panic, failure, etc.?
If it's actually suspending but having trouble waking up, you should at least see suspend messages in the log. This is from my Fedora laptop: [root@xi00859-lx ~]# cat /var/log/messages | grep -i "suspend" Mar 2 00:53:47 xi00859-lx ModemManager[903]: <info> [sleep-monitor] system is about to suspend Mar 2 00:53:48 xi00859-lx systemd[1]: Starting systemd-suspend.service - System Suspend... Mar 2 00:53:48 xi00859-lx systemd-sleep[2023]: Entering sleep state 'suspend'... Mar 2 00:53:48 xi00859-lx kernel: PM: suspend entry (deep)
Unless you disabled it during install or after, kdump should be enabled. You can check to see if there is anything in /var/crash/. If there is, then that should help you track it down.
Hope this helps some!
Travis Newton
Founder/Owner
Hosting Intellect, LLC
[Hosting Intellect, LLC Logo]rough
https://www.hostingintellect.com
________________________________ From: jdwirtz@cox.net jdwirtz@cox.net Sent: Wednesday, March 1, 2023 4:29:45 PM To: users@lists.almalinux.org Subject: [AlmaLinux Users] Re: Alma 9 keep server up and running.
Thanks... I'm trying to run this on a Beelink Mini PC, Mini S Intel 11th Gen 4-Cores N5095, Mini Desktop Computer 8GB DDR4 RAM 256GB SSD Overall it working, but I guess it is randomly crashing? _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender. If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.
Don't have kdump enabled... didn't think I would need it. Not finding any sleep, suspend but found Mar 2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [WRST] Mar 2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [DRST] Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) ----- Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: enabled with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+ Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: PME: Signaling with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: AER: enabled with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: enabled with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+ Mar 2 08:49:25 alma1 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 ----Mar 2 08:49:25 alma1 kernel: hub 1-0:1.0: USB hub found Mar 2 08:49:25 alma1 kernel: hub 1-0:1.0: 8 ports detected Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14 Mar 2 08:49:25 alma1 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 2 08:49:25 alma1 kernel: usb usb2: Product: xHCI Host Controller Mar 2 08:49:25 alma1 kernel: usb usb2: Manufacturer: Linux 5.14.0-162.12.1.el9_1.x86_64 xhci-hcd Mar 2 08:49:25 alma1 kernel: usb usb2: SerialNumber: 0000:00:14.0 Mar 2 08:49:25 alma1 kernel: hub 2-0:1.0: USB hub found Mar 2 08:49:25 alma1 kernel: hub 2-0:1.0: 6 ports detected Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: usbcore: registered new interface driver usbserial_generic Mar 2 08:49:25 alma1 kernel: usbserial: USB Serial support registered for generic Mar 2 08:49:25 alma1 kernel: i8042: PNP: No PS/2 controller found. ------ \Mar 2 08:49:31 alma1 systemd[1]: Special handling of early boot iSCSI sessions was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/class/iscsi_session). Mar 2 08:49:31 alma1 systemd[1]: OSTree Remount OS/ Bind Mounts was skipped because of a failed condition check (ConditionKernelCommandLine=ostree). Mar 2 08:49:31 alma1 systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes). Mar 2 08:49:31 alma1 systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes). Mar 2 08:49:31 alma1 systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). Mar 2 08:49:31 alma1 systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed. Mar 2 08:49:31 alma1 systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). ----- Mar 2 08:49:32 alma1 kernel: EXT4-fs (sda1): recovery complete Mar 2 08:49:32 alma1 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. Mar 2 08:49:32 alma1 systemd[1]: Mounted /web. Mar 2 08:49:32 alma1 systemd[1]: Reached target Local File Systems. Mar 2 08:49:32 alma1 systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Mar 2 08:49:32 alma1 systemd[1]: Mark the need to relabel after reboot was skipped because of a failed condition check (ConditionPathExists=!/.autorelabel). Mar 2 08:49:32 alma1 systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id). Mar 2 08:49:32 alma1 systemd[1]: Starting Create Volatile Files and Directories... Mar 2 08:49:32 alma1 systemd[1]: Received SIGRTMIN+20 from PID 390 (plymouthd). Mar 2 08:49:32 alma1 systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. Mar 2 08:49:32 alma1 systemd[1]: Finished Create Volatile Files and Directories. Mar 2 08:49:32 alma1 systemd[1]: Mounting RPC Pipe File System... Mar 2 08:49:32 alma1 systemd[1]: Starting Security Auditing Service... Mar 2 08:49:32 alma1 systemd[1]: Starting RPC Bind... Mar 2 08:49:32 alma1 systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var). Mar 2 08:49:32 alma1 systemd[1]: Update is Completed was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 auditd[1021]: audit dispatcher initialized with q_depth=1200 and 1 active plugins Mar 2 08:49:32 alma1 systemd[1]: Started RPC Bind.
I did a search on the ACPI BIOS error being reported and I was able to find this kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213023
It looks like that bug is still in 5.15.x. I checked the one AlmaLinux 9.1 VM we have running right now and it is running 5.14.0-162.12.1.el9_1.x86_64.
I'm not sure if that's what's actually causing the system to lock up, but it might be related. I'd probably install AlmaLinux 8 and see if the problem still exists.
Travis Newton
Founder/Owner
Hosting Intellect, LLC
[Hosting Intellect, LLC Logo]
https://www.hostingintellect.com
________________________________ From: jdwirtz@cox.net jdwirtz@cox.net Sent: Thursday, March 2, 2023 11:32:49 AM To: users@lists.almalinux.org Subject: [AlmaLinux Users] Re: Alma 9 keep server up and running.
Don't have kdump enabled... didn't think I would need it. Not finding any sleep, suspend but found Mar 2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [WRST] Mar 2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [DRST] Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) ----- Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: enabled with IRQ 122 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+ Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: PME: Signaling with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: AER: enabled with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: enabled with IRQ 123 Mar 2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+ Mar 2 08:49:25 alma1 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 ----Mar 2 08:49:25 alma1 kernel: hub 1-0:1.0: USB hub found Mar 2 08:49:25 alma1 kernel: hub 1-0:1.0: 8 ports detected Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14 Mar 2 08:49:25 alma1 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 2 08:49:25 alma1 kernel: usb usb2: Product: xHCI Host Controller Mar 2 08:49:25 alma1 kernel: usb usb2: Manufacturer: Linux 5.14.0-162.12.1.el9_1.x86_64 xhci-hcd Mar 2 08:49:25 alma1 kernel: usb usb2: SerialNumber: 0000:00:14.0 Mar 2 08:49:25 alma1 kernel: hub 2-0:1.0: USB hub found Mar 2 08:49:25 alma1 kernel: hub 2-0:1.0: 6 ports detected Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330) Mar 2 08:49:25 alma1 kernel: ACPI Error: Aborting method _SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Mar 2 08:49:25 alma1 kernel: usbcore: registered new interface driver usbserial_generic Mar 2 08:49:25 alma1 kernel: usbserial: USB Serial support registered for generic Mar 2 08:49:25 alma1 kernel: i8042: PNP: No PS/2 controller found. ------ \Mar 2 08:49:31 alma1 systemd[1]: Special handling of early boot iSCSI sessions was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/class/iscsi_session). Mar 2 08:49:31 alma1 systemd[1]: OSTree Remount OS/ Bind Mounts was skipped because of a failed condition check (ConditionKernelCommandLine=ostree). Mar 2 08:49:31 alma1 systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes). Mar 2 08:49:31 alma1 systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes). Mar 2 08:49:31 alma1 systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). Mar 2 08:49:31 alma1 systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed. Mar 2 08:49:31 alma1 systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). ----- Mar 2 08:49:32 alma1 kernel: EXT4-fs (sda1): recovery complete Mar 2 08:49:32 alma1 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. Mar 2 08:49:32 alma1 systemd[1]: Mounted /web. Mar 2 08:49:32 alma1 systemd[1]: Reached target Local File Systems. Mar 2 08:49:32 alma1 systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Mar 2 08:49:32 alma1 systemd[1]: Mark the need to relabel after reboot was skipped because of a failed condition check (ConditionPathExists=!/.autorelabel). Mar 2 08:49:32 alma1 systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id). Mar 2 08:49:32 alma1 systemd[1]: Starting Create Volatile Files and Directories... Mar 2 08:49:32 alma1 systemd[1]: Received SIGRTMIN+20 from PID 390 (plymouthd). Mar 2 08:49:32 alma1 systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. Mar 2 08:49:32 alma1 systemd[1]: Finished Create Volatile Files and Directories. Mar 2 08:49:32 alma1 systemd[1]: Mounting RPC Pipe File System... Mar 2 08:49:32 alma1 systemd[1]: Starting Security Auditing Service... Mar 2 08:49:32 alma1 systemd[1]: Starting RPC Bind... Mar 2 08:49:32 alma1 systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var). Mar 2 08:49:32 alma1 systemd[1]: Update is Completed was skipped because all trigger condition checks failed. Mar 2 08:49:32 alma1 auditd[1021]: audit dispatcher initialized with q_depth=1200 and 1 active plugins Mar 2 08:49:32 alma1 systemd[1]: Started RPC Bind. _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender. If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.
On Thu, Mar 2, 2023 at 11:14 AM Travis Newton < Travis.Newton@hostingintellect.com> wrote:
I did a search on the ACPI BIOS error being reported and I was able to find this kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213023
It looks like that bug is still in 5.15.x. I checked the one AlmaLinux 9.1 VM we have running right now and it is running 5.14.0-162.12.1.el9_1.x86_64.
I'm not sure if that's what's actually causing the system to lock up, but it might be related. I'd probably install AlmaLinux 8 and see if the problem still exists.
Travis Newton
You can try installing ELRepo's kernel-ml on AlmaLinux 9. It always provides the latest kernel from kernel.org.
Akemi
I've installed 8.7 and so far it's has not crashed. Is the 9 crashes due to my hardware?
I would say your hardware is affected by https://bugzilla.kernel.org/show_bug.cgi?id=213023 then.
Travis Newton
Founder/Owner
Hosting Intellect, LLC
[Hosting Intellect, LLC Logo]
https://www.hostingintellect.com
________________________________ From: jdwirtz@cox.net jdwirtz@cox.net Sent: Sunday, March 5, 2023 3:19:13 PM To: users@lists.almalinux.org Subject: [AlmaLinux Users] Re: Alma 9 keep server up and running.
I've installed 8.7 and so far it's has not crashed. Is the 9 crashes due to my hardware? _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender. If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.
participants (4)
-
Akemi Yagi -
jdwirtz＠cox.net -
Stephen John Smoogen -
Travis Newton