After Update Reboot , GUI Not Working , Able to access Via SSH

A

amit bhatt

New Member
Jul 30, 2019
10
0
1
38
Hello Team,

i recently update my Proxmox and after update command line suggest me to reboot server as its Kernel Update.

i do the same but after that unable to access via GUI but able to access via SSH ,

after searching i try to figure out below things.

Code: 
● pve-cluster.service                                                            loaded failed failed    The Proxmox VE cluster fi
● pve-firewall.service                                                           loaded failed failed    Proxmox VE firewall
● pve-guests.service                                                             loaded failed failed    PVE guests
● pve-ha-crm.service                                                             loaded failed failed    PVE Cluster HA Resource M
● pve-ha-lrm.service                                                             loaded failed failed    PVE Local HA Resource Man
  pve-lxc-syscalld.service                                                       loaded active running   Proxmox VE LXC Syscall Da
  pvebanner.service                                                              loaded active exited    Proxmox VE Login Banner
  pvedaemon.service                                                              loaded active running   PVE API Daemon
  pvefw-logger.service                                                           loaded active running   Proxmox VE firewall logge
  pvenetcommit.service                                                           loaded active exited    Commit Proxmox VE network
  pveproxy.service                                                               loaded active running   PVE API Proxy Server
● pvesr.service                                                                  loaded failed failed    Proxmox VE replication ru
● pvestatd.service                                                               loaded failed failed    PVE Status Daemon



please help me .
 
Last edited:
Hi,

what does say the following command:
systemctl status pveproxy pvedaemon

have you seen any error in syslog or journalctl?
 
amit bhatt said:
pve-cluster.service
Click to expand...
Moayad said:
Hi,

what does say the following command:
systemctl status pveproxy pvedaemon

have you seen any error in syslog or journalctl?
Click to expand...

RESULT OF systemctl status pveproxy pvedaemon

Code: 
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-09-17 22:20:41 UTC; 9h ago
 Main PID: 29901 (pveproxy)
    Tasks: 4 (limit: 4915)
   Memory: 133.2M
   CGroup: /system.slice/pveproxy.service
           ├─29901 pveproxy
           ├─30514 pveproxy worker
           ├─30515 pveproxy worker
           └─30516 pveproxy worker

Sep 18 08:09:08 ns3132228 pveproxy[29901]: starting 2 worker(s)
Sep 18 08:09:08 ns3132228 pveproxy[29901]: worker 30514 started
Sep 18 08:09:08 ns3132228 pveproxy[29901]: worker 30515 started
Sep 18 08:09:08 ns3132228 pveproxy[30514]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or
Sep 18 08:09:08 ns3132228 pveproxy[30515]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or
Sep 18 08:09:08 ns3132228 pveproxy[30501]: worker exit
Sep 18 08:09:08 ns3132228 pveproxy[29901]: worker 30501 finished
Sep 18 08:09:08 ns3132228 pveproxy[29901]: starting 1 worker(s)
Sep 18 08:09:08 ns3132228 pveproxy[29901]: worker 30516 started
Sep 18 08:09:08 ns3132228 pveproxy[30516]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-09-17 22:20:30 UTC; 9h ago
 Main PID: 29779 (pvedaemon)
    Tasks: 4 (limit: 4915)
   Memory: 127.1M
   CGroup: /system.slice/pvedaemon.service
           ├─29779 pvedaemon
           ├─29780 pvedaemon worker
           ├─29781 pvedaemon worker
           └─29782 pvedaemon worker

Sep 17 22:20:30 ns3132228 systemd[1]: Starting PVE API Daemon...
Sep 17 22:20:30 ns3132228 pvedaemon[29779]: starting server
Sep 17 22:20:30 ns3132228 pvedaemon[29779]: starting 3 worker(s)
Sep 17 22:20:30 ns3132228 pvedaemon[29779]: worker 29780 started
Sep 17 22:20:30 ns3132228 pvedaemon[29779]: worker 29781 started
Sep 17 22:20:30 ns3132228 pvedaemon[29779]: worker 29782 started
Sep 17 22:20:30 ns3132228 systemd[1]: Started PVE API Daemon.
lines 3-42/42 (END)
 
amit bhatt said:
Sep 18 08:09:08 ns3132228 pveproxy[30514]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or
Sep 18 08:09:08 ns3132228 pveproxy[30515]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or
Click to expand...

please try pvecm updatecerts -f command if still not work please reboot the PVE node.

hope that helps :)
 
Moayad said:
please try pvecm updatecerts -f command if still not work please reboot the PVE node.

hope that helps :)
Click to expand...

RESULT OF pvecm updatecerts -f

Code: 
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
 
amit bhatt said:
Unable to load access control list: Connection refused
Click to expand...
please check your syslog if there any error or use journalctl -b after reboot the node

Is the upgrade completed?

Can you please try apt update && apt -f install command
 
Moayad said:
please check your syslog if there any error or use journalctl -b after reboot the node

Is the upgrade completed?

Can you please try apt update && apt -f install command
Click to expand...

I hire Freelancer guy and he fix issue.

thanks for your support also.
 
You must log in or register to reply here.
Top Bottom