Can't access web interface

[danaleight]

Hi yesterday I shuted down my server like everyday but today I can't access the web interface.
Can you help me please I can't resolve this problem myself ?

Here is a part of the journalctl -xe :

Jun 16 12:55:23 pve pveproxy[1757]: worker 2231 started
Jun 16 12:55:23 pve pveproxy[2231]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Jun 16 12:55:24 pve pveproxy[2229]: worker exit
Jun 16 12:55:24 pve pveproxy[2230]: worker exit
Jun 16 12:55:24 pve pveproxy[1757]: worker 2229 finished
Jun 16 12:55:24 pve pveproxy[1757]: worker 2230 finished
Jun 16 12:55:24 pve pveproxy[1757]: starting 2 worker(s)
Jun 16 12:55:24 pve pveproxy[1757]: worker 2232 started
Jun 16 12:55:24 pve pveproxy[1757]: worker 2233 started
Jun 16 12:55:24 pve pveproxy[2232]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Jun 16 12:55:24 pve pveproxy[2233]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.

Here is the /etc/hosts :

127.0.0.1 localhost.localdomain localhost
10.0.0.10 pve.routeur pve

Here is systemctl status pveproxy :

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-06-16 12:46:02 CEST; 18min ago
    Process: 1750 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
    Process: 1751 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1757 (pveproxy)
      Tasks: 4 (limit: 18975)
     Memory: 203.5M
        CPU: 38.421s
     CGroup: /system.slice/pveproxy.service
             ├─1757 pveproxy
             ├─3134 pveproxy worker
             ├─3135 pveproxy worker
             └─3136 pveproxy worker

Jun 16 13:05:00 pve pveproxy[1757]: starting 2 worker(s)
Jun 16 13:05:00 pve pveproxy[1757]: worker 3134 started
Jun 16 13:05:00 pve pveproxy[1757]: worker 3135 started
Jun 16 13:05:00 pve pveproxy[3134]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Jun 16 13:05:00 pve pveproxy[3135]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Jun 16 13:05:00 pve pveproxy[3133]: worker exit
Jun 16 13:05:00 pve pveproxy[1757]: worker 3133 finished
Jun 16 13:05:00 pve pveproxy[1757]: starting 1 worker(s)
Jun 16 13:05:00 pve pveproxy[1757]: worker 3136 started
Jun 16 13:05:00 pve pveproxy[3136]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.

Here is the pvedaemon status :

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-06-16 12:46:01 CEST; 19min ago
    Process: 1728 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1745 (pvedaemon)
      Tasks: 4 (limit: 18975)
     Memory: 145.2M
        CPU: 1.264s
     CGroup: /system.slice/pvedaemon.service
             ├─1745 pvedaemon
             ├─1746 pvedaemon worker
             ├─1747 pvedaemon worker
             └─1748 pvedaemon worker

Jun 16 12:45:53 pve systemd[1]: Starting PVE API Daemon...
Jun 16 12:46:01 pve pvedaemon[1745]: starting server
Jun 16 12:46:01 pve pvedaemon[1745]: starting 3 worker(s)
Jun 16 12:46:01 pve pvedaemon[1745]: worker 1746 started
Jun 16 12:46:01 pve pvedaemon[1745]: worker 1747 started
Jun 16 12:46:01 pve pvedaemon[1745]: worker 1748 started
Jun 16 12:46:01 pve systemd[1]: Started PVE API Daemon.

If you need more file you can ask me.

 

[nunner]

Hi,

is your server running in a cluster? What's the output of systemctl status pve-cluster?

 

[danaleight]

Hi,

is your server running in a cluster? What's the output of systemctl status pve-cluster?

Hi! I have only one server here is the output of the systemctl status pve cluster :

● 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 Fri 2023-06-16 12:45:54 CEST; 37min ago
    Process: 1736 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 9ms

Jun 16 12:45:54 pve pmxcfs[1736]: [database] crit: DB load failed
Jun 16 12:45:54 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 16 12:45:54 pve pmxcfs[1736]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jun 16 12:45:54 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 16 12:45:54 pve pmxcfs[1736]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 16 12:45:54 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jun 16 12:45:54 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 16 12:45:54 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jun 16 12:45:54 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 16 12:45:54 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.

 

[nunner]

Does the database file exist (ls -l /var/lib/pve-cluster/config.db)? I would do a health check on the disks to see whether they are failing or not. Did you do anything special before shutting down the server yesterday?

 

[danaleight]

Does the database file exist (ls -l /var/lib/pve-cluster/config.db)? I would do a health check on the disks to see whether they are failing or not. Did you do anything special before shutting down the server yesterday?

Yes it does exist and it is not empty. There is keys inside.

 

[danaleight]

Did you do anything special before shutting down the server yesterday?

No I didn't I shutted it down like everytime, I never changed the hostname either.