Search results

What CPU is the host? Maybe it is too old for RHEL 10.

I think you need to give it a package name to reinstall. ETA: Just so you are aware, there are so-called "man pages" that document most commands. See "man apt" for example.

You installed a script that modifies the PVE code. It apparently needs an update for PVE9. Maybe you could do "apt install --reinstall pveproxy" and don't install your patches to get back to a working system.

Removing subscription nag from UI.. There's the problem. You likely used one of the "community scripts" to remove the subscription nag and it installed a hook to re-apply the patch on updates, But when you go between major versions the patch is wrong because the code has changed and said...

I don't think PVE copies PAM user info to the other members of the cluster. If that is true you'd have to create the user on all cluster members.

Wouldn't life be simpler if you just use Linux to run Linux things? Install Ubuntu in a VM and take the rest of the day off.

Debian 13 uses a version of systemd that requires nesting. So it is in fact needed.

It is probably a system user that some package installs. Like "sshd" or "saned".

I've been doing it wrong for 25 years then :). Having a mail alias seems better than having to log in as root to read root's mail.

Try creating an /etc/aliases file (see man aliases for the format) and then run "newaliases". ETA: I don't think .forward files ever re-wrote the To address, just the so-called "envelope sender" that it gives to the receiving server.

It does the same thing on PVE 8 if you use xterm.js as the console.

I said there were guides for Debian, not PVE. What you did allows access to the GUI, which is what most people what. If you want SSH access you need to join the server itself to your AD domain from the command line using samba/winbind or sssd. This will allow logging in to the PAM realm rather...

You will have to join your PVE server to the AD domain. There are many guides on how to do this for Debian.

Even a dedicated RT kernel won't provide real-time guarantees unless the processes that want such guarantees use the FIFO or RR schedulers, which isn't the default. Which means code changes are needed to make it work. There's also this (from the thread @insatomcat linked): for both kernel and...

Also, this link might be useful for the future: https://wiki.debian.org/DontBreakDebian

Because apt will upgrade things to the newest version it finds in the configured repositories. It can't read your mind you know. Recovery from this will be a bit difficult, might be easier to just re-install the container. Then learn about apt pinning. Or that. Or from Debian backports (which...

BIOS time should be set to UTC for Proxmox, not local time (unless your time zone is UTC). Don't know about your other issues.

That's because you have an old service unit for the one you compiled yourself (Debian never puts anything in /usr/local, that's strictly for the admin). I would uninstall both versions and reinstall the Debain one. This is why you never install things manually if it can be helped. ETA: Never...

Have you tried just hitting the ENTER key? Or just typing "root" and your password? It looks like it is actually booting and showing the login screen.

Is there a reason you can't just "apt install glances"?