Linux

55223 readers

1595 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Linux server hangs on shutdown (lemmy.fish)

submitted 1 week ago by potentiallynotfelix@lemmy.fish to c/linux@lemmy.ml

52 comments fedilink hide all child comments

I've had two server oses here: alma linux and debian(currently). On both of them, they will hang when I shut them down from cockpit, and they hang at the end of the shutdown.

Also, it takes an hour to a day to have this issue start. if it's restarted two times in a row quickly, it works perfectly fine for some reason.

What I've tried:

setting "acpi=off" and "acpi=force" kernel parameters in grub
removing my nvidia gpu(i was using nouveau drivers)
changing distros

nothing worked. here are some things that both distros had in common with eachother:

systemd
cockpit
libvirt & qemu
docker

does anyone have advice? nothing i've seen online has worked. thank you for suggestions

you are viewing a single comment's thread
view the rest of the comments

[–] truthfultemporarily@feddit.org 2 points 1 week ago (2 children)

Because you tried two different OSes and the point where it hangs is the point where the OS sends an APM/ACPI command to reboot / power off. This is the last thing the OS does. So if that's not happening something is wrong with the hardware, BIOS, or BIOS settings.

You could try the syslog (journalctl), but logging is probably already off at that point.

[–] potentiallynotfelix@lemmy.fish 2 points 1 week ago (1 children)

yeah journalctl logs show nothing relevant. I have disabled acpi and forced it(acpi=force), but that didn't fix this. There are a lot of different combinations of acpi settings I could try:

acpi=force noapic
nolapic
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off

But I found these from a guy which they didn't work on so I'm reluctant to try them.

[–] ReversalHatchery@beehaw.org 2 points 1 week ago (1 children)

did you check it /proc/cmdline if the params were taken into account? perhaps you edited the config but didn't update the initramfs

[–] potentiallynotfelix@lemmy.fish 2 points 1 week ago

Yes, I've always made sure to use update-grub and checked cmdline to make sure it has the correct parameters. Regardless of acpi=force or acpi=off, it would still hang.

[–] hendrik@palaver.p3x.de 1 points 1 week ago (1 children)

And I guess if you're in front of the computer, you could just press the reset button or unplug it at that point (after it sucessfully synchronized the disks). no need to let it sit, there is no harm or data to be lost at that point.

[–] potentiallynotfelix@lemmy.fish 2 points 1 week ago

that is what I end up doing right now, but if I'm on vacation and I need to reboot, I'm fucked.