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

  • catloaf@lemm.eeEnglish
    6·
    2 months ago

    Hardware? Do they shut down properly if you do it from the console or ssh?

      • catloaf@lemm.eeEnglish
        2·
        2 months ago

        Interesting. BIOS update? Maybe check through all the settings, or do a factory reset on the BIOS? I have a similar board (H510 something) running proxmox and it works fine.

        • potentiallynotfelix@lemmy.fishOP
          3·
          2 months ago

          I would like to note that this may have been caused by a bios update, as it started sometime after it. i’ll try another update now.

          edit: already on the latest bios version.

  • nanook@friendica.eskimo.com
    62·
    2 months ago

    @potentiallynotfelix As a diagnostic, I would suggest trying shutting them down by ssh in and then using systemctl to shut them down, if that works then you know the issue is with cockpit. If it hangs even when systemd is asked to halt then I would consider reverting to the previous bios and see if the problem persists.

  • FauxLiving@lemmy.world
    2·
    2 months ago

    reboot: machine restart

    This makes me think it’s a motherboard issue.

    The system is done with its shutdown process and issued the reboot command, but the motherboard didn’t restart.

    There could be some electronics components which get wedged over time. My sound card will occasionally not boot unless it has been completely powered off for 30 seconds or so.

    • potentiallynotfelix@lemmy.fishOP
      2·
      2 months ago

      thanks for the suggestion, could you elaborate on what this would do differently from the regular shutdown command that systemctl uses? thanks again

      • undrwater@lemmy.world
        2·
        2 months ago

        My understanding is that ‘halt’ had been an alias for ‘halt -p’, but that changed recently. -p tells the command to power off. Without it, it just shuts down process.

  • just_another_person@lemmy.world
    11·
    2 months ago

    Your machine isn’t shutting down, it’s trying to sleep.

    You also have active KVM instances which are fighting to keep it alive.

    • potentiallynotfelix@lemmy.fishOP
      1·
      2 months ago

      can you elaborate on why you suspect this? The cockpit reboot or shutdown button uses the shutdown command directly along with a --reboot or --poweroff flag.

          onSubmit(event) {
        const Dialogs = this.context;
        const arg = this.props.shutdown ? "--poweroff" : "--reboot";
        if (!this.props.shutdown)
            cockpit.hint("restart");

        cockpit.spawn(["shutdown", arg, this.state.when, this.state.message], { superuser: "require", err: "message" })
                .then(this.props.onClose || Dialogs.close)
                .catch(e => this.setState({ error: e.toString() }));

        event.preventDefault();
        return false;
    }

      (source)