Привет, у меня на Code: # pveversion
pve-manager/8.0.4/d258a813cfa6b390 (запущен ядро: 6.2.16-15-pve) возникла проблема: виртуальные машины перестали запускаться. У меня был полный раздел /var, в /lib/pve/local-btrfs/images были некорректные образы ВМ, которые на самом деле должны были находиться в пуле ZFS, и я заменил это большим разделом (LVM). Я синхронизировал все с старого /var на новый /var. И после перезагрузки сервера я хотел проверить ВМ командой 'qm list', но получаю только следующее: Code: # qm list
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused Между тем я заметил, что служба pve-cluster.service не была запущена: Code: # systemctl status pve-cluster.service
× pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-05-01 11:50:17 CEST; 8min ago
Process: 8392 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
CPU: 10ms
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem. и Code: # journalctl -xeu pve-cluster.service
May 01 11:50:16 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:16 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:16 neckar1 pmxcfs[8390]: fuse: mountpoint is not empty
May 01 11:50:16 neckar1 pmxcfs[8390]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] crit: fuse_mount error: File exists
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] crit: fuse_mount error: File exists
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:16 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
May 01 11:50:16 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: mountpoint is not empty
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: mountpoint is not empty
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem. and Code: pvecm --help
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused У вас есть какие-нибудь идеи, как это снова запустить? С уважением BrotherJ
pve-manager/8.0.4/d258a813cfa6b390 (запущен ядро: 6.2.16-15-pve) возникла проблема: виртуальные машины перестали запускаться. У меня был полный раздел /var, в /lib/pve/local-btrfs/images были некорректные образы ВМ, которые на самом деле должны были находиться в пуле ZFS, и я заменил это большим разделом (LVM). Я синхронизировал все с старого /var на новый /var. И после перезагрузки сервера я хотел проверить ВМ командой 'qm list', но получаю только следующее: Code: # qm list
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused Между тем я заметил, что служба pve-cluster.service не была запущена: Code: # systemctl status pve-cluster.service
× pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-05-01 11:50:17 CEST; 8min ago
Process: 8392 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
CPU: 10ms
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem. и Code: # journalctl -xeu pve-cluster.service
May 01 11:50:16 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:16 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:16 neckar1 pmxcfs[8390]: fuse: mountpoint is not empty
May 01 11:50:16 neckar1 pmxcfs[8390]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] crit: fuse_mount error: File exists
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] crit: fuse_mount error: File exists
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:16 neckar1 pmxcfs[8390]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:16 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:16 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
May 01 11:50:16 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: mountpoint is not empty
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: resolved node name 'neckar1' to '192.55.84.250' for default node IP address
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: mountpoint is not empty
May 01 11:50:17 neckar1 pmxcfs[8392]: fuse: if you are sure this is safe, use the 'nonempty' mount option
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] crit: fuse_mount error: File exists
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 pmxcfs[8392]: [main] notice: exit proxmox configuration filesystem (-1)
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
May 01 11:50:17 neckar1 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 01 11:50:17 neckar1 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 01 11:50:17 neckar1 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem. and Code: pvecm --help
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused У вас есть какие-нибудь идеи, как это снова запустить? С уважением BrotherJ
