jerim79

New Member
Dec 18, 2020
14
1
3
43
Rebooted machine, it came back up with no obvious error messages. Web GUI won't come up in any browser. I searched the internet for answers. Been working on this for three days now.

Command: pveversion
pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve)

Command: nano /etc/hosts
127.0.0.1 localhost.localdomain localhost
#127.0.1.1 localhost.localdomain localhost
10.74.48.202 proxmox proxmox.server.com

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

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

Command: systemctl status pve-cluster.service
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 2020-12-18 13:13:01 CST; 1min 15s ago
Process: 4146 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Dec 18 13:13:01 proxmox systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 18 13:13:01 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Dec 18 13:13:01 proxmox systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 18 13:13:01 proxmox systemd[1]: pve-cluster.service: Start request repeated too quickly.
Dec 18 13:13:01 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 18 13:13:01 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.

Command: journalctl -xe
Dec 18 13:15:42 proxmox pveproxy[4279]: worker exit
Dec 18 13:15:42 proxmox pveproxy[1401]: worker 4279 finished
Dec 18 13:15:42 proxmox pveproxy[1401]: starting 1 worker(s)
Dec 18 13:15:42 proxmox pveproxy[1401]: worker 4282 started
Dec 18 13:15:42 proxmox pveproxy[4282]: /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 1775.
Dec 18 13:15:43 proxmox pveproxy[4280]: worker exit
Dec 18 13:15:43 proxmox pveproxy[4281]: worker exit
Dec 18 13:15:43 proxmox pveproxy[1401]: worker 4280 finished
Dec 18 13:15:43 proxmox pveproxy[1401]: worker 4281 finished
Dec 18 13:15:43 proxmox pveproxy[1401]: starting 2 worker(s)
Dec 18 13:15:43 proxmox pveproxy[1401]: worker 4283 started
Dec 18 13:15:43 proxmox pveproxy[1401]: worker 4284 started
Dec 18 13:15:43 proxmox pveproxy[4283]: /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 1775.
Dec 18 13:15:43 proxmox pveproxy[4284]: /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 1775.
Dec 18 13:15:47 proxmox pveproxy[4282]: worker exit
Dec 18 13:15:47 proxmox pveproxy[1401]: worker 4282 finished
Dec 18 13:15:47 proxmox pveproxy[1401]: starting 1 worker(s)
Dec 18 13:15:47 proxmox pveproxy[1401]: worker 4285 started
Dec 18 13:15:47 proxmox pveproxy[4285]: /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 1775.
Dec 18 13:15:48 proxmox pveproxy[4283]: worker exit
Dec 18 13:15:48 proxmox pveproxy[4284]: worker exit
Dec 18 13:15:48 proxmox pveproxy[1401]: worker 4283 finished
Dec 18 13:15:48 proxmox pveproxy[1401]: worker 4284 finished
Dec 18 13:15:48 proxmox pveproxy[1401]: starting 2 worker(s)
Dec 18 13:15:48 proxmox pveproxy[1401]: worker 4286 started
Dec 18 13:15:48 proxmox pveproxy[1401]: worker 4287 started
Dec 18 13:15:48 proxmox pveproxy[4286]: /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 1775.
Dec 18 13:15:48 proxmox pveproxy[4287]: /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 1775.
Dec 18 13:15:52 proxmox pveproxy[4285]: worker exit
Dec 18 13:15:52 proxmox pveproxy[1401]: worker 4285 finished
Dec 18 13:15:52 proxmox pveproxy[1401]: starting 1 worker(s)
Dec 18 13:15:52 proxmox pveproxy[1401]: worker 4288 started
Dec 18 13:15:52 proxmox pveproxy[4288]: /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 1775.
Dec 18 13:15:53 proxmox pveproxy[4286]: worker exit
Dec 18 13:15:53 proxmox pveproxy[4287]: worker exit
Dec 18 13:15:53 proxmox pveproxy[1401]: worker 4286 finished
Dec 18 13:15:53 proxmox pveproxy[1401]: worker 4287 finished
Dec 18 13:15:53 proxmox pveproxy[1401]: starting 2 worker(s)
Dec 18 13:15:53 proxmox pveproxy[1401]: worker 4289 started
Dec 18 13:15:53 proxmox pveproxy[1401]: worker 4290 started
Dec 18 13:15:53 proxmox pveproxy[4289]: /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 1775.

Command: pvecm updatecerts --force
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

Command: hostname --ip-address
10.74.48.202

Command: nano /etc/network/interfaces
auto lo
iface lo inet loopback

auto enp0s31fs
iface enp0s31f6 inet dhcp

auto vmbr0
iface vmbr0 inet static
address 10.74.48.202
netmask 255.255.252.0
gateway 10.74.48.1
bridge_ports enp0s31f6
bridge_stp off
bridge_fd 0

iface vmbr0 inet6 static
address 0:0:0:0:0:ffff:a4a:30ca
netmask 22
gateway 0:0:0:0:0:FFFF:0A4A:3001
bridge_ports enp0s31f6
bridge_stp off
bridge_fd 0
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,751
143
68
29
Vienna
shop.maurer-it.com
Hi,

Please check the journalctl -u pve-manager to see if there another hint in your log.

and please post the output of the following commands:

Bash:
apt-get install -f
apt-get install -V proxmox-ve pve-manager
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
Command: journalctl -u pve-manager
root@proxmox.server.com:~# journalctl -u pve-manager
-- Logs begin at Mon 2020-12-21 04:43:10 CST, end at Mon 2020-12-21 13:15:35 CST. --
-- No entries --
root@proxmox.server.com:~#

Command: apt install -f
root@proxmox.server.com:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@proxmox.server.com:~#

Command: apt-get install -V proxmox-ve pve-manager
root@proxmox.server.com:~# apt-get install -V proxmox-ve pve-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (6.3-1).
pve-manager is already the newest version (6.3-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@proxmox.server.com:~#
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
I am behind a corporate proxy. Here is what I have done to configure the system to get through the proxy.

Command: nano /etc/profile.d/proxy.sh
export http_proxy="http://proxy.server.com:8082/"
export https_proxy="http://proxy.server.com:8082/"
export HTTP_PROXY="http://proxy.server.com:8082/"
export HTTPS_PROXY="http://proxy.server.com:8082/"

chmod +x /etc/profile.d/proxy.sh
source /etc/profile.d/proxy.sh
env | grep -i proxy

touch /etc/apt/apt.conf.d/99verify-peer.conf \ && echo >>/etc/apt/apt.conf.d/99verify-peer.conf "Acquire { https::Verify-Peer false }"

Command: nano /etc/apt/apt.conf.d/80proxy
Acquire::http { Proxy "http://proxy.server.com:8082/"; };
Acquire::https { Proxy "http://proxy.server.com:8082/"; };
Acquire::ftp { Proxy "ftp://proxy.server.com:8082/"; };

Command: nano ~/.wgetrc
use_proxy = on
http_proxy = http://proxy.server.com:8082/
https_proxy = http://proxy.server.com:8082/
ftp_proxy = ftp://proxy.server.com:8082/
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,751
143
68
29
Vienna
shop.maurer-it.com
Have you checked for hostname node?


Also please post the output of the following commands:


Bash:
~ hostname -A
~ hostname -I
~ ip -c a
~ journalctl -u pve-cluster
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@servername:~# hostname -A
servername servername

root@servername:~# hostname -I
10.74.48.202 ::ffff:10.74.48.202

root@servername:~# ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether f8:75:a4:e7:73:4e brd ff:ff:ff:ff:ff:ff
3: wlp82s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether f8:e4:e3:3e:7e:ed brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f8:75:a4:e7:73:4e brd ff:ff:ff:ff:ff:ff
inet 10.74.48.202/22 brd 10.74.51.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 ::ffff:10.74.48.202/22 scope global
valid_lft forever preferred_lft forever
inet6 fe80::fa75:a4ff:fee7:734e/64 scope link
valid_lft forever preferred_lft forever
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:~# journalctl -u pve-cluster
-- Logs begin at Mon 2020-12-21 20:20:11 CST, end at Tue 2020-12-22 04:45:09 CST. --
Dec 22 02:11:08 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 22 02:11:08 server pmxcfs[1440]: fuse: mountpoint is not empty
Dec 22 02:11:08 server pmxcfs[1440]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Dec 22 02:11:08 server pmxcfs[1440]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1440]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server pmxcfs[1440]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1440]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 22 02:11:08 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Dec 22 02:11:08 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 22 02:11:08 server pmxcfs[1450]: fuse: mountpoint is not empty
Dec 22 02:11:08 server pmxcfs[1450]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Dec 22 02:11:08 server pmxcfs[1450]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1450]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server pmxcfs[1450]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1450]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 22 02:11:08 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Dec 22 02:11:08 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 22 02:11:08 server pmxcfs[1454]: fuse: mountpoint is not empty
Dec 22 02:11:08 server pmxcfs[1454]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Dec 22 02:11:08 server pmxcfs[1454]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1454]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server pmxcfs[1454]: [main] crit: fuse_mount error: File exists
Dec 22 02:11:08 server pmxcfs[1454]: [main] notice: exit proxmox configuration filesystem (-1)
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 22 02:11:08 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 02:11:08 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Dec 22 02:11:08 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 22 02:11:08 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 22 02:11:08 server pmxcfs[1457]: fuse: mountpoint is not empty
 

Moayad

Proxmox Staff Member
Staff member
Jan 2, 2020
1,751
143
68
29
Vienna
shop.maurer-it.com
Try to stop pve-cluster service and use pmxcfs with -f flag (Do not daemonize server):

Bash:
systemctl stop pve-cluster
pmxcfs -f
[wait, then C^c]
systemctl start pve-cluster
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:~# systemctl stop pve-cluster
root@server:~# pmxcfs -f
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
[main] crit: fuse_mount error: File exists
[main] notice: exit proxmox configuration filesystem (-1)

root@server:~# systemctl start pve-cluster
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:~# journalctl -xe
Dec 22 05:53:18 server pveproxy[12610]: worker exit
Dec 22 05:53:18 server pveproxy[27156]: worker 12610 finished
Dec 22 05:53:18 server pveproxy[27156]: starting 1 worker(s)
Dec 22 05:53:18 server pveproxy[27156]: worker 12613 started
Dec 22 05:53:18 server pveproxy[12613]: /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 17Dec 22 05:53:20 server pveproxy[12611]: worker exit
Dec 22 05:53:20 server pveproxy[12612]: worker exit
Dec 22 05:53:20 server pveproxy[27156]: worker 12611 finished
Dec 22 05:53:20 server pveproxy[27156]: worker 12612 finished
Dec 22 05:53:20 server pveproxy[27156]: starting 2 worker(s)
Dec 22 05:53:20 server pveproxy[27156]: worker 12614 started
Dec 22 05:53:20 server pveproxy[27156]: worker 12615 started
Dec 22 05:53:20 server pveproxy[12614]: /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 17Dec 22 05:53:20 server pveproxy[12615]: /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 17Dec 22 05:53:23 server pveproxy[12613]: worker exit
Dec 22 05:53:23 server pveproxy[27156]: worker 12613 finished
Dec 22 05:53:23 server pveproxy[27156]: starting 1 worker(s)
Dec 22 05:53:23 server pveproxy[27156]: worker 12616 started
Dec 22 05:53:23 server pveproxy[12616]: /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 17Dec 22 05:53:25 server pveproxy[12614]: worker exit
Dec 22 05:53:25 server pveproxy[12615]: worker exit
Dec 22 05:53:25 server pveproxy[27156]: worker 12614 finished
Dec 22 05:53:25 server pveproxy[27156]: worker 12615 finished
Dec 22 05:53:25 server pveproxy[27156]: starting 2 worker(s)
Dec 22 05:53:25 server pveproxy[27156]: worker 12617 started
Dec 22 05:53:25 server pveproxy[27156]: worker 12618 started
Dec 22 05:53:25 server pveproxy[12617]: /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 17Dec 22 05:53:25 server pveproxy[12618]: /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 17Dec 22 05:53:28 server pveproxy[12616]: worker exit
Dec 22 05:53:28 server pveproxy[27156]: worker 12616 finished
Dec 22 05:53:28 server pveproxy[27156]: starting 1 worker(s)
Dec 22 05:53:28 server pveproxy[27156]: worker 12619 started
Dec 22 05:53:28 server pveproxy[12619]: /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 17Dec 22 05:53:30 server pveproxy[12617]: worker exit
Dec 22 05:53:30 server pveproxy[12618]: worker exit
Dec 22 05:53:30 server pveproxy[27156]: worker 12618 finished
Dec 22 05:53:30 server pveproxy[27156]: worker 12617 finished
Dec 22 05:53:30 server pveproxy[27156]: starting 2 worker(s)
Dec 22 05:53:30 server pveproxy[27156]: worker 12620 started
Dec 22 05:53:30 server pveproxy[27156]: worker 12621 started
Dec 22 05:53:30 server pveproxy[12620]: /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 17Dec 22 05:53:30 server pveproxy[12621]: /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 17
root@server:~# systemctl status pve-cluster.service
● 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 Tue 2020-12-22 05:52:32 CST; 2min 56s ago
Process: 12570 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Dec 22 05:52:32 server systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 05:52:32 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Dec 22 05:52:32 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 22 05:52:32 server systemd[1]: pve-cluster.service: Start request repeated too quickly.
Dec 22 05:52:32 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 22 05:52:32 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:~# ls /etc/pve/
local
root@server:~# ls /etc/pve/local
root@server:~#
 
Last edited:

jerim79

New Member
Dec 18, 2020
14
1
3
43
Command: pvecm updatecerts --force
root@server:~# pvecm updatecerts --force
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
root@server:~#
 

aaron

Proxmox Staff Member
Staff member
Jun 3, 2019
2,943
465
88
root@server:~# ls /etc/pve/
local
root@server:~# ls /etc/pve/local
root@server:~#
Remove the local dir in /etc/pve und try to restart the pve-cluster service, systemctl restart pve-cluster.

This service provides the config files in /etc/pve as a FUSE file system. If it is not empty, it cannot be mounted.
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:/etc/pve# rmdir local
root@server:/etc/pve# systemctl restart pve-cluster
root@server:/etc/pve# 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: active (running) since Sun 2020-12-27 17:53:54 CST; 1min 33s ago
Process: 24731 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 24739 (pmxcfs)
Tasks: 5 (limit: 4915)
Memory: 2.7M
CGroup: /system.slice/pve-cluster.service
└─24739 /usr/bin/pmxcfs

Dec 27 17:53:53 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 27 17:53:54 server systemd[1]: Started The Proxmox VE cluster filesystem.
root@server#

When I go to https://10.74.48.202:8006/ it doesn't load anything. Says the site can't be reached.
1609113655440.png
 

aaron

Proxmox Staff Member
Staff member
Jun 3, 2019
2,943
465
88
Check if the pvedaemon and pvecluster services are running. The /etc/pve directory now contains quite a few more files and directories right?
 

jerim79

New Member
Dec 18, 2020
14
1
3
43
root@server:~# ls /etc/pve/local
lrm_status lxc openvz priv pve-ssl.key pve-ssl.pem qemu-server
root@server:~# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-12-27 19:22:19 CST; 13min ago
Process: 1399 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 1430 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 135.8M
CGroup: /system.slice/pvedaemon.service
├─1430 pvedaemon
├─1431 pvedaemon worker
├─1432 pvedaemon worker
└─1433 pvedaemon worker

Dec 27 19:22:18 server systemd[1]: Starting PVE API Daemon...
Dec 27 19:22:19 server pvedaemon[1430]: starting server
Dec 27 19:22:19 server pvedaemon[1430]: starting 3 worker(s)
Dec 27 19:22:19 server pvedaemon[1430]: worker 1431 started
Dec 27 19:22:19 server pvedaemon[1430]: worker 1432 started
Dec 27 19:22:19 server pvedaemon[1430]: worker 1433 started
Dec 27 19:22:19 server systemd[1]: Started PVE API Daemon.
root@server:~# 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: active (running) since Sun 2020-12-27 19:22:18 CST; 13min ago
Process: 1256 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 1272 (pmxcfs)
Tasks: 6 (limit: 4915)
Memory: 35.3M
CGroup: /system.slice/pve-cluster.service
└─1272 /usr/bin/pmxcfs

Dec 27 19:22:17 server systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 27 19:22:18 server systemd[1]: Started The Proxmox VE cluster filesystem.
root@server:~#
 

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!

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 your own in 60 seconds.

Buy now!