8.1 Update Hung/Failed

B

bossmanc

New Member
Nov 25, 2023
8
0
1
Hey, looking for some insight on an issue during upgrade from 8.0.4 to 8.1.3.

The update hung at setting up pve-manager, so I've tried rebooting the system, running apt update and upgrade from cli, etc. Everything "seems" to be working fine, however in package versions I've got some "not correctly installed" for pve-manager & proxmox-ve though, which i've tried to manually apt install them both and they both hang as well.

If I run apt upgrade it also hangs at 20% in cli and does nothing. After killing the hung upgrade I get dpkg was interrupted, manually run configure blah blah, but it still hangs if I run that.



Here is my versions. Kernel upgrade seems to have succeeded.

Code: 
proxmox-ve: not correctly installed (running kernel: 6.5.11-4-pve)
pve-manager: not correctly installed (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.0.9
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.5: 6.5.11-4
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.4
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.9
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.2
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3

Any help would be appreciated.
 
Last edited:
bossmanc said:
Hey, looking for some insight on an issue during upgrade from 8.0.4 to 8.1.3.

The update hung at setting up pve-manager, so I've tried rebooting the system, running apt update and upgrade from cli, etc. Everything "seems" to be working fine, however in package versions I've got some "not correctly installed" for pve-manager & proxmox-ve though, which i've tried to manually apt install them both and they both hang as well.

If I run apt upgrade it also hangs at 20% in cli and does nothing. After killing the hung upgrade I get dpkg was interrupted, manually run configure blah blah, but it still hangs if I run that.



Here is my versions. Kernel upgrade seems to have succeeded.

Code: 
proxmox-ve: not correctly installed (running kernel: 6.5.11-4-pve)
pve-manager: not correctly installed (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.0.9
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.5: 6.5.11-4
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.4
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.9
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.2
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3

Any help would be appreciated.
Click to expand...
Hi,
please run dpkg --configure -a and see if that runs without issues.
 
bossmanc said:
It does not, fails at the same point.
Click to expand...
Please make sure that the node is quorate (if part of a cluster) and post the output of ps auxwf. This might tell us where exactly the package configuration hangs.

Edit: On a side note, never use apt upgrade, always use apt dist-upgrade for Proxmox products, as this also solves possible dependency issues by removing packages.
 
Last edited:
Chris said:
Please make sure that the node is quorate (if part of a cluster) and post the output of ps auxwf. This might tell us where exactly the package configuration hangs.

Edit: On a side note, never use apt upgrade, always use apt dist-upgrade for Proxmox products, as this also solves possible dependency issues by removing packages.
Click to expand...
I initially started the update from the GUI, not moving to CLI until it failed. (Node is not part of a cluster)

Here is the relevant output of ps auxwf:

Code: 
root        9961  0.0  0.0  20408  9408 ?        Ss   01:35   0:00 /lib/systemd/systemd --user
root        9962  0.0  0.0 169988  5680 ?        S    01:35   0:00  \_ (sd-pam)
root       10147  0.0  0.0   2576   896 ?        S    01:36   0:00 /bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 8.0.4
root       10235  0.0  0.0  16424  4032 ?        S    01:36   0:00  \_ systemctl reload-or-restart pvescheduler.service
root       10236  0.0  0.0      0     0 ?        Z    01:36   0:00      \_ [systemd-tty-ask] <defunct>
root       11057  7.9  4.0 14774592 5322996 ?    Sl   01:38  10:38 /usr/bin/kvm -id 126 -name --redacted--,debug-threads=on -no-shu
root       18947  0.0  0.0   5872   896 tty1     Ss+  01:59   0:00 /sbin/agetty -o -p -- \u --noclear - linux
root@hv:~#
 
Hmm, so there is a zombie process for what should probably be the systemd-tty-ask-password-agent, which blocks the reloading/restarting of pvescheduler and therefore the package configuration hangs.

Can you check the current status of systemctl status polkit.service.

Edit: service is called polkit.service, not polkitd.service as written initially.
 
Last edited:
Chris said:
Hmm, so there is a zombie process for what should probably be the systemd-tty-ask-password-agent, which blocks the reloading/restarting of pvescheduler and therefore the package configuration hangs.

Can you check the current status of systemctl status polkitd.service.
Click to expand...
I'm getting
Code: 
Unit polkitd.service could not be found.
 
bossmanc said:
I'm getting
Code: 
Unit polkitd.service could not be found.
Click to expand...
Sorry, the service is called polkit.service, not polkitd.service. I updated the previous post accordingly.
 
I am having the same issue. On uprade to 8.1 from 8, the upgrade hangs at Setting up pve-manager (8.1.3) .... Running systemctl status polkit.service returns Unit polkit.service could not be found.. I have not yet rebooted the node.The node is also not part of a cluster, and the output of ps auxwf is similar:
Code: 
root      753414  0.0  0.0   5308  1920 ?        Ss   Nov24   0:00 /usr/sbin/qmeventd /var/run/qmeventd.sock
root      753415  0.0  0.0   2576  1536 ?        S    Nov24   0:00 /bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 8.0.9
root      753530  0.0  0.0  13444  5376 ?        S    Nov24   0:00  \_ systemctl reload-or-restart pvescheduler.service
root      753531  0.0  0.0      0     0 ?        Z    Nov24   0:00      \_ [systemd-tty-ask] <defunct>
root      758439  2.2  3.8 5184972 2551364 ?     Sl   Nov24  20:23 /usr/bin/kvm -id 585 -name theCLR,debug-threads=on -no-shutdown -
root      775411  0.0  0.1 351180 112460 ?       Ss   Nov24   0:04 pve-ha-lrm
root      775457  0.0  0.1 351688 113120 ?       Ss   Nov24   0:02 pve-ha-crm
root      775458  0.0  0.0   2576  1536 ?        S    Nov24   0:00 /bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 8.0.9
root      775542  0.0  0.0  13444  5504 ?        S    Nov24   0:00  \_ systemctl reload-or-restart pvescheduler.service
root      775543  0.0  0.0      0     0 ?        Z    Nov24   0:00      \_ [systemd-tty-ask] <defunct>
root      824561  0.0  0.0  79184  1792 ?        Ssl  00:00   0:02 /usr/sbin/pvefw-logger
root      967092  0.0  0.0  19368 10880 ?        Ss   10:49   0:00 /lib/systemd/systemd --user
root      967093  0.0  0.0 171260  7316 ?        S    10:49   0:00  \_ (sd-pam)
www-data  968930  0.1  0.2 366916 164272 ?       Ss   10:56   0:00 pveproxy
www-data  969111  0.1  0.2 375676 146504 ?       S    10:57   0:00  \_ pveproxy worker
www-data  969112  0.1  0.2 379640 152264 ?       S    10:57   0:01  \_ pveproxy worker
www-data  969113  0.1  0.2 375848 146504 ?       S    10:57   0:01  \_ pveproxy worker
 
I'm starting to worry I might be looking at a reinstall of the base OS. Anyone have any other ideas before I end up going that route?
 
Please post your systemd version, which you get via systemctl --version. Was Proxmox VE installed on top of Debian or from an ISO installer? Are you able to restart the pvescheduler.service from cli by running systemctl reload-or-restart pvescheduler.service or does this hang as well.

Some users encountered the same issue in the past, without finding the underlying cause they fixed their install by removing the service restart from the dpkg post-install hook and doing it manually afterwards, see https://forum.proxmox.com/threads/u...grade-hangs-on-setting-up-pve-manager.128226/

Also, please double check that you really do not have a cluster by posting the output of pvecm status and provide systemctl status pve-cluster.service, for reference also see https://forum.proxmox.com/threads/proxmox-update-broke.136872/page-2#post-608330
 
Systemd Version:

Code: 
systemd 252 (252.17-1~deb12u1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified

Proxmox was installed from ISO.
I do seem to be able to reload-restart the scheduler.

pvecm status:

Code: 
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

pvecluster.service output:

Code: 
pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Sun 2023-11-26 20:16:04 MST; 8h ago
    Process: 4176 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 4202 (pmxcfs)
      Tasks: 7 (limit: 154472)
     Memory: 59.4M
        CPU: 27.963s
     CGroup: /system.slice/pve-cluster.service
             └─4202 /usr/bin/pmxcfs

Nov 26 20:16:03 hv systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Nov 26 20:16:03 hv pmxcfs[4176]: [main] notice: resolved node name 'hv' to '10.10.8.5' for default node IP>
Nov 26 20:16:03 hv pmxcfs[4176]: [main] notice: resolved node name 'hv' to '10.10.8.5' for default node IP>
Nov 26 20:16:04 hv systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.

I will take a shot at those links and report back tomorrow.
 
My node was installed through the ISO.

https://forum.proxmox.com/threads/u...grade-hangs-on-setting-up-pve-manager.128226/ reviewing this thread, where does it explain removing the service restart from the postinstall hook? I followed the suggestions outlined and I'm having the same issues as OP -- no polkit, systemd daemon-reload doesn't change anything.

systemctl reload-or-restart pvescheduler.service does indeed hang.

here is my output as well:
systemd version:
Code: 
systemd 252 (252.17-1~deb12u1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified

pvecm status:
Code: 
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

pve-cluster.service status:
Code: 
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-11-22 11:10:10 EST; 4 days ago
   Main PID: 857 (pmxcfs)
      Tasks: 11 (limit: 76727)
     Memory: 65.3M
        CPU: 5min 27.405s
     CGroup: /system.slice/pve-cluster.service
             └─857 /usr/bin/pmxcfs

Nov 22 11:10:09 pve systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Nov 22 11:10:09 pve pmxcfs[838]: [main] notice: resolved node name 'pve' to '192.168.1.50' for default node IP address
Nov 22 11:10:09 pve pmxcfs[838]: [main] notice: resolved node name 'pve' to '192.168.1.50' for default node IP address
Nov 22 11:10:10 pve systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
 
Well, I can report that everything seems to be working as intended. However I'm moderately unsure how I got there.

Basically all I did was move the /var/lib/dpkg folder to a directory I created at /var/lib/temp; and then copied it back to its original location.
Once the copy was done I ran dpkg --configure -a and it ran correctly. I then ran dpkg-reconfigure pve-manager to confirm and it worked as well.

Now package versions are reporting correctly:

Code: 
proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.0.9
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.5: 6.5.11-4
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.4
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.9
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.2
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3
 
bossmanc said:
Basically all I did was move the /var/lib/dpkg folder to a directory I created at /var/lib/temp; and then copied it back to its original location.
Once the copy was done I ran dpkg --configure -a and it ran correctly. I then ran dpkg-reconfigure pve-manager to confirm and it worked as well.
Click to expand...

I tried this but I am still experiencing the same hang with dpkg --configure -a at Setting up pve-manager (8.1.3) ...
 
commenting out line 133 and removing pvescheduler.service from UNITS= on line 143 in /var/lib/dpkg/info/pve-manager.postinst made it so the upgrade no longer hanged on Setting up pve-manager (8.1.3) ... but I was still unable to restart pvescheduler.service. Once I rebooted, I was able to restart the service.
 
Last edited:
bergamot said:
commenting out line 133 and removing pvescheduler.service from UNITS= on line 143 in /var/lib/dpkg/info/pve-manager.postinst made it so the upgrade no longer hanged on Setting up pve-manager (8.1.3) ... but I was still unable to restart pvescheduler.service. Once I rebooted, I was able to restart the service.
Click to expand...
Same here. one of 3 in a cluster ended up in this state after updating from within proxmox. nodes are identical hardware/software wise.
Tried your suggestion of removing the service from line 143, this resulted in dpkg-reconfigure to finish, but pvescheduler services refuses to start, also after a reboot.
 
slekkus said:
Same here. one of 3 in a cluster ended up in this state after updating from within proxmox. nodes are identical hardware/software wise.
Tried your suggestion of removing the service from line 143, this resulted in dpkg-reconfigure to finish, but pvescheduler services refuses to start, also after a reboot.
Click to expand...
Please double check if that node is part of the quorate part of the cluster by running pvecm status on that node. If you say that it refuses to restart, what exactly do you mean? Does it hang as described above? Double check also the output of ps auxwf and journalctl -u pvescheduler.service.
 
Chris said:
Please double check if that node is part of the quorate part of the cluster by running pvecm status on that node. If you say that it refuses to restart, what exactly do you mean? Does it hang as described above? Double check also the output of ps auxwf and journalctl -u pvescheduler.service.
Click to expand...
Restarting pvescheduler service just hangs, no output. Experiencing exactly the same as OP.

Code: 
root@mosh:~# pvecm status
Cluster information
-------------------
Name:             proxcluster
Config Version:   4
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Wed Nov 29 22:24:34 2023
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1.14e3
Quorate:          No

Votequorum information
----------------------
Expected votes:   4
Highest expected: 4
Total votes:      1
Quorum:           3 Activity blocked
Flags:

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.10.10.201 (local)

Code: 
root@mosh:~# ps auxwf
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           2  0.0  0.0      0     0 ?        S    22:19   0:00 [kthreadd]
root           3  0.0  0.0      0     0 ?        I<   22:19   0:00  \_ [rcu_gp]
<...>
root         619  0.0  0.0      0     0 ?        I    22:19   0:00  \_ [kworker/1:3-mm_percpu_wq]
root         636  0.0  0.0      0     0 ?        I<   22:19   0:00  \_ [tls-strp]
root        1159  0.0  0.0   2460  1024 ?        S    22:19   0:00  \_ bpfilter_umh
root        3070  0.0  0.0      0     0 ?        I    22:24   0:00  \_ [kworker/0:1-events]
root        3098  0.0  0.0      0     0 ?        I    22:25   0:00  \_ [kworker/u8:0-events_unbound]
root           1  0.4  0.0 169684 13896 ?        Ss   22:19   0:01 /sbin/init
root         309  0.0  0.2  71760 39936 ?        Ss   22:19   0:00 /lib/systemd/systemd-journald
root         318  0.0  0.1  80580 24960 ?        SLsl 22:19   0:00 /sbin/dmeventd -f
root         332  0.0  0.0  27068  6728 ?        Ss   22:19   0:00 /lib/systemd/systemd-udevd
root         573  0.0  0.0  79184  2304 ?        Ssl  22:19   0:00 /usr/sbin/pvefw-logger
_rpc         576  0.0  0.0   7876  3840 ?        Ss   22:19   0:00 /sbin/rpcbind -f -w
ceph         587  0.0  0.0  20304 13056 ?        Ss   22:19   0:00 /usr/bin/python3 /usr/bin/ceph-crash
message+     590  0.0  0.0   9128  4864 ?        Ss   22:19   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --sy
root         593  0.0  0.0 152748  2432 ?        Ssl  22:19   0:00 /usr/bin/lxcfs /var/lib/lxcfs
root         594  0.0  0.0 278156  3712 ?        Ssl  22:19   0:00 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/
root         597  0.0  0.0  11908  6144 ?        Ss   22:19   0:00 /usr/sbin/smartd -n -q never
root         599  0.0  0.0   7064  1868 ?        S    22:19   0:00 /bin/bash /usr/sbin/ksmtuned
root        3023  0.0  0.0   5464  1664 ?        S    22:24   0:00  \_ sleep 60
root         601  0.0  0.0  25396  7808 ?        Ss   22:19   0:00 /lib/systemd/systemd-logind
root         602  0.0  0.0   2332  1280 ?        Ss   22:19   0:00 /usr/sbin/watchdog-mux
root         604  0.0  0.0 101388  5504 ?        Ssl  22:19   0:00 /usr/sbin/zed -F
root         605  0.0  0.0   5308  1152 ?        Ss   22:19   0:00 /usr/sbin/qmeventd /var/run/qmeventd.sock
root         735  0.0  0.0   5024  2560 ?        Ss   22:19   0:00 /usr/libexec/lxc/lxc-monitord --daemon
_chrony      768  0.0  0.0  18860  3076 ?        S    22:19   0:00 /usr/sbin/chronyd -F 1
_chrony      781  0.0  0.0  10532  2456 ?        S    22:19   0:00  \_ /usr/sbin/chronyd -F 1
root         770  0.0  0.0  15408  9216 ?        Ss   22:19   0:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root        2435  0.0  0.0  17972 11136 ?        Ss   22:21   0:00  \_ sshd: root@pts/0
root        2442  0.0  0.0   8748  5632 pts/0    Ss   22:21   0:00      \_ -bash
root        3157  0.0  0.0  11084  4736 pts/0    R+   22:25   0:00          \_ ps auxwf
root         780  0.0  0.0   6120  3868 tty1     Ss   22:19   0:00 /bin/login -p --
root        1803  0.0  0.0   8508  5248 tty1     S+   22:19   0:00  \_ -bash
root         838  0.0  0.0 440632  3272 ?        Ssl  22:19   0:00 /usr/bin/rrdcached -B -b /var/lib/rrdcached/db/ -j /var/lib/rrdcached/jour
root         851  0.0  0.2 521736 34320 ?        Ssl  22:19   0:00 /usr/bin/pmxcfs
root         952  0.0  0.0  42656  4500 ?        Ss   22:19   0:00 /usr/lib/postfix/sbin/master -w
postfix      955  0.0  0.0  43044  6912 ?        S    22:19   0:00  \_ pickup -l -t unix -u -c
postfix      956  0.0  0.0  43092  6912 ?        S    22:19   0:00  \_ qmgr -l -t unix -u
ceph         974  0.1  0.2 266520 47360 ?        Ssl  22:19   0:00 /usr/bin/ceph-mon -f --cluster ceph --id mosh --setuser ceph --setgroup ce
root         981  0.4  1.0 299508 168540 ?       SLsl 22:19   0:01 /usr/sbin/corosync -f
root         984  0.0  0.0   6608  2688 ?        Ss   22:19   0:00 /usr/sbin/cron -f
root        1152  0.0  0.6 157312 98752 ?        Ss   22:19   0:00 pve-firewall
root        1155  0.2  0.5 152244 94696 ?        Ss   22:19   0:00 pvestatd
root        3149  0.2  0.6 548968 101532 ?       Sl   22:25   0:00  \_ pverados
root        1270  0.0  0.8 233172 137348 ?       Ss   22:19   0:00 pvedaemon
root        1271  0.0  0.8 233456 137992 ?       S    22:19   0:00  \_ pvedaemon worker
root        1272  0.0  0.8 233456 137864 ?       S    22:19   0:00  \_ pvedaemon worker
root        1273  0.0  0.8 233456 137864 ?       S    22:19   0:00  \_ pvedaemon worker
root        1390  0.0  0.6 219304 111828 ?       Ss   22:19   0:00 pve-ha-crm
root        1788  0.0  0.0  19084 10496 ?        Ss   22:19   0:00 /lib/systemd/systemd --user
root        1789  0.0  0.0 170744  6780 ?        S    22:19   0:00  \_ (sd-pam)
www-data    1945  0.0  0.8 234628 138536 ?       Ss   22:20   0:00 pveproxy
www-data    1946  0.0  0.8 234892 142888 ?       S    22:20   0:00  \_ pveproxy worker
www-data    1947  0.0  0.8 234892 142888 ?       S    22:20   0:00  \_ pveproxy worker
www-data    1948  0.0  0.8 234892 142888 ?       S    22:20   0:00  \_ pveproxy worker
www-data    1953  0.0  0.3  80792 53400 ?        Ss   22:20   0:00 spiceproxy
www-data    1954  0.0  0.3  81020 54172 ?        S    22:20   0:00  \_ spiceproxy worker
root        1955  0.0  0.6 218700 111276 ?       Ss   22:20   0:00 pve-ha-lrm
root        1957  0.2  0.9 234348 156988 ?       Ss   22:20   0:00 /usr/bin/perl /usr/bin/pvesh --nooutput create /nodes/localhost/startall
root        1958  0.0  0.8 234216 131052 ?       Ss   22:20   0:00  \_ task UPID:mosh:000007A6:00001308:6567AB14:startall::root@pam:
ceph        3061  0.2  0.1 131932 29440 ?        Ssl  22:24   0:00 /usr/bin/ceph-mgr -f --cluster ceph --id mosh --setuser ceph --setgroup ce
ceph        3081  0.1  0.2 142404 35968 ?        Ssl  22:24   0:00 /usr/bin/ceph-osd -f --cluster ceph --id 1 --setuser ceph --setgroup ceph

journalctl remains empty while restarting the service.
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back