Recurring errors in System Log

G

ghosthvj

New Member
Oct 9, 2025
2
0
1
Hello, since I updated to PVE 9 I am encountering these recurring errors in my System Log

Server EDGE

Code: 
16:36:59 edge pveproxy[2123204]: '/etc/pve/nodes/void/pve-ssl.pem' does not exist!
16:36:59 edge pveproxy[2125692]: proxy detected vanished client connection
16:44:29 edge pveproxy[2123204]: '/etc/pve/nodes/dream/pve-ssl.pem' does not exist!
16:44:39 edge pveproxy[2125692]: proxy detected vanished client connection

Server VOID

Code: 
16:36:00 void pveproxy[301465]: '/etc/pve/nodes/edge/pve-ssl.pem' does not exist!
16:36:10 void pveproxy[301465]: proxy detected vanished client connection
16:36:10 void pveproxy[301465]: '/etc/pve/nodes/dream/pve-ssl.pem' does not exist!
16:36:20 void pveproxy[301465]: proxy detected vanished client connection

Server DREAM

Code: 
16:35:57 dream pveproxy[416060]: '/etc/pve/nodes/edge/pve-ssl.pem' does not exist!
16:35:57 dream pveproxy[411809]: proxy detected vanished client connection
16:36:07 dream pveproxy[427145]: '/etc/pve/nodes/void/pve-ssl.pem' does not exist!
16:36:17 dream pveproxy[411809]: proxy detected vanished client connection

I have 3 servers with Proxmox on the local network but I do NOT have a cluster, I have never configured it nor do I intend to. The strange thing is that on each server I find these messages referencing the others, even recognizing the name of each host.

I've reinstalled all three servers with PVE 9, and they continue with this behavior; none of them have any references to the others.

Thank you in advance.
 
Hi,
on each node, what is the output of:
Code: 
ls -l /etc/pve/nodes
cat /etc/pve/.members
pvecm status
systemctl status pve-cluster.service
?
 
fiona said:
Hi,
on each node, what is the output of:
Code: 
ls -l /etc/pve/nodes
cat /etc/pve/.members
pvecm status
systemctl status pve-cluster.service
?
Click to expand...
Hello, this is the result for each host:

EDGE

Code: 
root@edge:~# ls -l /etc/pve/nodes
total 0
drwxr-xr-x 2 root www-data 0 Sep 15 18:25 edge

Code: 
root@edge:~# cat /etc/pve/.members

{
"nodename": "edge",
"version": 0
}

Code: 
root@edge:~# pvecm status

Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

Code: 
root@edge:~# systemctl status pve-cluster.service

● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/usr/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-10-09 21:34:55 CEST; 14h ago
 Invocation: be20d1886d644ceb8767b7f22526d0ce
    Process: 2315813 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 2315815 (pmxcfs)
      Tasks: 8 (limit: 8970)
     Memory: 40.3M (peak: 52.1M)
        CPU: 1min 13.603s
     CGroup: /system.slice/pve-cluster.service
             └─2315815 /usr/bin/pmxcfs

Oct 09 21:34:54 edge systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Oct 09 21:34:54 edge pmxcfs[2315813]: [main] notice: resolved node name 'edge' to '192.168.5.254' for default node IP address
Oct 09 21:34:54 edge pmxcfs[2315813]: [main] notice: resolved node name 'edge' to '192.168.5.254' for default node IP address
Oct 09 21:34:55 edge systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.

VOID
Code: 
root@void:~# ls -l /etc/pve/nodes

total 0
drwxr-xr-x 2 root www-data 0 Sep 26 23:58 void

Code: 
root@void:~# cat /etc/pve/.members

{
"nodename": "void",
"version": 0
}

Code: 
root@void:~# pvecm status

Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

Code: 
root@void:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/usr/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-10-09 21:34:14 CEST; 14h ago
 Invocation: d816cb745ccc490eb52c201bb4cb0219
    Process: 665541 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 665543 (pmxcfs)
      Tasks: 8 (limit: 71966)
     Memory: 36M (peak: 50.7M)
        CPU: 57.357s
     CGroup: /system.slice/pve-cluster.service
             └─665543 /usr/bin/pmxcfs

Oct 09 21:34:13 void systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Oct 09 21:34:13 void pmxcfs[665541]: [main] notice: resolved node name 'void' to '192.168.5.253' for default node IP address
Oct 09 21:34:13 void pmxcfs[665541]: [main] notice: resolved node name 'void' to '192.168.5.253' for default node IP address
Oct 09 21:34:14 void systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.

DREAM

Code: 
root@dream:~# ls -l /etc/pve/nodes
total 0
drwxr-xr-x 2 root www-data 0 Sep 20 20:04 dream

Code: 
root@dream:~# cat /etc/pve/.members

{
"nodename": "dream",
"version": 0
}

Code: 
root@dream:~# pvecm status

Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

Code: 
root@dream:~# systemctl status pve-cluster.service

● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/usr/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-10-09 21:34:59 CEST; 14h ago
 Invocation: a9f16dc91c4c4a6bb8807d115893e0c2
    Process: 567655 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 567657 (pmxcfs)
      Tasks: 8 (limit: 9118)
     Memory: 41M (peak: 47.6M)
        CPU: 57.853s
     CGroup: /system.slice/pve-cluster.service
             └─567657 /usr/bin/pmxcfs

Oct 09 21:34:57 dream systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Oct 09 21:34:58 dream pmxcfs[567655]: [main] notice: resolved node name 'dream' to '192.168.5.252' for default node IP address
Oct 09 21:34:58 dream pmxcfs[567655]: [main] notice: resolved node name 'dream' to '192.168.5.252' for default node IP address
Oct 09 21:34:59 dream systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.

It's a very strange thing because none of them are part of a cluster nor have they ever been
 
You must log in or register to reply here.
Top Bottom