Promox not working anymore

M

MarcusS

New Member
Sep 11, 2022
6
0
1
Hy,

Sorry to say, but I´m really not an expert in promox and Linux. But I build a promox on a NUC 6 months ago and its working fine.
Yesterday evening I recognised that my iobroker is not working anymore and I startet to search the error. I did not changed anythink.

What I found out:
I could not connect to promox via webinterface
via putty I could still connect to the NUC

service pveproxy restart
Job for pveproxy.service failed because the control process exited with error code. See "systemctl status pveproxy.service" and "journalctl -xe" for details.

Sorry for my really stuped questions. But what could I do next?

Thank you in advance!!
 
Try
Bash: 
systemctl start pveproxy.service
# or
systemctl status pveproxy.service

If the webui doesnt start, look at
Code: 
journalctl -xe

to see any error messages.

What is your disk utilisation?

Code: 
df -h
should give you something like this
Code: 
Filesystem                    Size  Used Avail Use% Mounted on
udev                           63G     0   63G   0% /dev
tmpfs                          13G  1.4M   13G   1% /run
rpool/ROOT/pve-1              225G  1.9G  223G   1% /
tmpfs                          63G   40M   63G   1% /dev/shm
tmpfs                         5.0M     0  5.0M   0% /run/lock
rpool                         223G  128K  223G   1% /rpool
rpool/ROOT                    223G  128K  223G   1% /rpool/ROOT
rpool/data                    223G  128K  223G   1% /rpool/data
rpool/data/subvol-910-disk-0  8.0G  293M  7.8G   4% /rpool/data/subvol-910-disk-0
/dev/fuse                     128M   16K  128M   1% /etc/pve
tmpfs                          13G     0   13G   0% /run/user/0
 
Thank you very much for your fast help!
Attached the informationes from the commands. I hope it help you / me :)


systemctl start pveproxy.service
Job for pveproxy.service failed because the control process exited with error code. See "systemctl status pveproxy.service" and "journalctl -xe" for details.

systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor pres> Active: failed (Result: exit-code) since Sun 2022-09-11 13:40:05 CEST; 46s> Process: 38274 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exite> Process: 38275 ExecStart=/usr/bin/pveproxy start (code=exited, status=127) CPU: 484ms Sep 11 13:40:05 pve systemd[1]: pveproxy.service: Scheduled restart job, restar> Sep 11 13:40:05 pve systemd[1]: Stopped PVE API Proxy Server. Sep 11 13:40:05 pve systemd[1]: pveproxy.service: Start request repeated too qu> Sep 11 13:40:05 pve systemd[1]: pveproxy.service: Failed with result 'exit-code> Sep 11 13:40:05 pve systemd[1]: Failed to start PVE API Proxy Server.

journalctl -xe

root@pve:~# journalctl -xe ░░ ░░ Startup of the manager took 41688 microseconds. Sep 11 13:42:23 pve systemd[1]: Started User Manager for UID 0. ░░ Subject: A start job for unit user@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit user@0.service has finished successfully. ░░ ░░ The job identifier is 26695. Sep 11 13:42:23 pve systemd[1]: Started Session 12 of user root. ░░ Subject: A start job for unit session-12.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit session-12.scope has finished successfully. ░░ ░░ The job identifier is 26786. Sep 11 13:43:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:44:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:45:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:46:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:47:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> lines 5362-5384/5384 (END) ░░ ░░ Startup of the manager took 41688 microseconds. Sep 11 13:42:23 pve systemd[1]: Started User Manager for UID 0. ░░ Subject: A start job for unit user@0.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit user@0.service has finished successfully. ░░ ░░ The job identifier is 26695. Sep 11 13:42:23 pve systemd[1]: Started Session 12 of user root. ░░ Subject: A start job for unit session-12.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit session-12.scope has finished successfully. ░░ ░░ The job identifier is 26786. Sep 11 13:43:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:44:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:45:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:46:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d> Sep 11 13:47:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d>

df -h
Filesystem Size Used Avail Use% Mounted on udev 7.6G 0 7.6G 0% /dev tmpfs 1.6G 1.3M 1.6G 1% /run /dev/mapper/pve-root 55G 21G 32G 40% / tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda2 511M 328K 511M 1% /boot/efi tmpfs 1.6G 0 1.6G 0% /run/user/0
 
Last edited:
There are problems with an symlink

Code: 
Sep 11 13:45:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d>
Sep 11 13:46:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d>
Sep 11 13:47:01 pve cron[924]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d>

It should show like this:
Code: 
root@pve05:~# ll /etc/cron.d/
total 10
-rw-r--r-- 1 root root 201 Jun  7  2021 e2scrub_all
lrwxrwxrwx 1 root root  20 Sep 11 10:24 vzdump -> /etc/pve/vzdump.cron
-rw-r--r-- 1 root root 377 Jul  9  2021 zfsutils-linux

I think your pve-Filesystem is down.

What ist the output of
Code: 
systemctl status pve-cluster.service

I think a reboot is a good option
 
I tried several reboots, but unfortunallty withour success.

The output:

Code: 
root@pve:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor p>
     Active: failed (Result: exit-code) since Sun 2022-09-11 13:52:24 CEST; 2h >
    Process: 1019 ExecStart=/usr/bin/pmxcfs (code=exited, status=127)
        CPU: 3ms

Sep 11 13:52:26 pve systemd[1]: Failed to start The Proxmox VE cluster filesyst>
Sep 11 13:52:27 pve systemd[1]: pve-cluster.service: Start request repeated too>
Sep 11 13:52:27 pve systemd[1]: pve-cluster.service: Failed with result 'exit-c>
Sep 11 13:52:27 pve systemd[1]: Failed to start The Proxmox VE cluster filesyst>
Sep 11 13:52:28 pve systemd[1]: pve-cluster.service: Start request repeated too>
Sep 11 13:52:28 pve systemd[1]: pve-cluster.service: Failed with result 'exit-c>
Sep 11 13:52:28 pve systemd[1]: Failed to start The Proxmox VE cluster filesyst>
Sep 11 13:52:29 pve systemd[1]: pve-cluster.service: Start request repeated too>
Sep 11 13:52:29 pve systemd[1]: pve-cluster.service: Failed with result 'exit-c>
Sep 11 13:52:29 pve systemd[1]: Failed to start The Proxmox VE cluster filesyst>
lines 1-16/16 (END)
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-09-11 13:52:24 CEST; 2h 59min ago
    Process: 1019 ExecStart=/usr/bin/pmxcfs (code=exited, status=127)
        CPU: 3ms

Sep 11 13:52:26 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 11 13:52:27 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Sep 11 13:52:27 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 11 13:52:27 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 11 13:52:28 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Sep 11 13:52:28 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 11 13:52:28 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 11 13:52:29 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Sep 11 13:52:29 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 11 13:52:29 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 
Das grundlegende PVE-Filessystem startet bei Dir nicht. Die Ursache ist in den Ausgaben aber nicht zu sehen.

Durchsuch mal das Systemlog von hinten nach Ursachen, warum pve-cluster.service nicht startet.

Bash: 
journalctl -e

und dann mit Bild-Auf, Bild-Ab scrollen
 
OK - dann auch gerne auf Deutsch :) Kann das hier die Ursache sein?
Code: 
Sep 11 16:22:22 pve smartd[685]: Device: /dev/sda [SAT], 17 Currently unreadable (pending) sectors
Sep 11 16:22:22 pve smartd[685]: Device: /dev/sda [SAT], 9 Offline uncorrectable sectors

Nochmal der Hintergrund:
Wir haben gestern gegen 17:00 das Haus verlassen da lief die Kiste noch. Als wir gegen 0:00 zurück gekommen sind war sie nicht mehr erreichbar.
Warum, wieso weshalb ist die große frage... Ist die SSD hops gegangen...?
 
Ja, das wird es sein.

Dann am besten neu installieren, gleich auf zwei Platten mit ZFS Raid1 und die VM Backups wiederherstellen. Ist am saubersten.

Falls alles auf der alten SSD lag, diese in einem anderen Linux versuchen zu mounten, um an die Backup Dateien zu kommen.

Falls Du das Cluster Filesystem noch einmal brauchst. Das steht alles in einer DB. https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)
 
Naja, Proxmox kann ja nicht unbedingt etwas für Hardware-Defekte. Und die PVE-Installation ist vermutlich schneller wieder eingerichtet, als die ioBroker-Installation, oder?

Sehr gut, dass Du die Backups vom Server holen konntest. Falls Du ein NAS hast, kannst Du sie ja in Zukunft direkt runter synchronisieren.
 
Hi,

ich will nochmal ein letztes Feedback geben. Ich habe Promox neu installiert, Backup eingespielt und läuft alles wieder.
Die größte Arbeit dabei war das Netzwerkkabel durch das Haus zum Fernseher zu legen und den NUC anzuschließen. Normalerweise liegt der ja im Keller im Netzwerkschrank - nur habe ich dort keinen Bildschirm :D

PS: So richtig glaube ich noch immer nicht an einen Hardware-Defekt. Ich bin ja weiterhin an alle Daten gekommen und auch jetzt läuft er wieder ohne Probleme. Aber egal - jetzt läuft es wieder.

Vielen Dank für die Unterstützung!
 
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