Proxmox won't start after IP change

H

horizn

Well-Known Member
Aug 21, 2017
34
2
46
44
Hi,
I had working proxmox on Dell R700 server. Initially with private IP on WAN and LAN interface. I have changed WAN IP to external one and then Proxmox won't start with following error:

Code: 
Aug 22 22:25:56 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:56 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:56 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:57 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:57 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:57 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:25:58 gdynia systemd[1]: Starting The Proxmox VE cluster filesystem...
Aug 22 22:25:58 gdynia pmxcfs[17212]: [main] crit: Unable to get local IP address
Aug 22 22:25:58 gdynia pmxcfs[17212]: [main] crit: Unable to get local IP address
Aug 22 22:25:58 gdynia systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Aug 22 22:25:58 gdynia systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Aug 22 22:25:58 gdynia systemd[1]: pve-cluster.service: Unit entered failed state.
Aug 22 22:25:58 gdynia systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Aug 22 22:26:00 gdynia systemd[1]: Starting Proxmox VE replication runner...
Aug 22 22:26:01 gdynia pvesr[17232]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia pvesr[17232]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia pvesr[17232]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia systemd[1]: Started Proxmox VE replication runner.
Aug 22 22:26:01 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:01 gdynia cron[2500]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Aug 22 22:26:02 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:02 gdynia pvestatd[2571]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:06 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:06 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:06 gdynia pve-ha-crm[2592]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:07 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:07 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused
Aug 22 22:26:07 gdynia pve-ha-lrm[2598]: ipcc_send_rec failed: Connection refused

/etc/pve folder is empty. What else I should change/check to make it working back again?
 
If your /etc/pve folder is empty, you have issues.

Regarding your network issue, when you switch it back to the original configuration, does it work?

Also R700s are really old.
 
Hi,

please check the following files and if the ip addresses are correct.
/etc/hosts
/etc/corosync/corosync.conf
 
AaronWalker said:
If your /etc/pve folder is empty, you have issues.

Regarding your network issue, when you switch it back to the original configuration, does it work?

Also R700s are really old.
Click to expand...

It is actually PowerEdge R710 bought in 2012. I took it from my previous workplace (it was retired), and now I am using it for my private purposes. I can't restore original IP configuration because I don't have physical access.
 
Wouldn't be easier if I reinstall it? I have only only one VM installed so far.
 
Are the ip in the
/etc/hosts
for 'gdynia' entry resolvable?
 
wolfgang said:
Are the ip in the
/etc/hosts
for 'gdynia' entry resolvable?
Click to expand...

yes it is. My /etc/hosts file:

Code: 
127.0.0.1       localhost proxmox.domain.com  proxmox pvelocalhost gdynia
1.2.3.4  proxmox.domain.com    proxmox pvelocalhost gdynia
192.168.100.1   proxmox.domain.com    proxmox pvelocalhost gdynia

but when I am trying to run it:

Code: 
root@gdynia:~# /etc/init.d/pve-cluster start
[....] Starting pve-cluster (via systemctl): pve-cluster.serviceJob for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
 failed!
root@gdynia:~# 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 Wed 2017-08-23 21:42:21 BST; 11s ago
  Process: 15617 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Aug 23 21:42:21 gdynia systemd[1]: Starting The Proxmox VE cluster filesystem...
Aug 23 21:42:21 gdynia pmxcfs[15617]: [main] crit: Unable to get local IP address
Aug 23 21:42:21 gdynia systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Aug 23 21:42:21 gdynia systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Aug 23 21:42:21 gdynia systemd[1]: pve-cluster.service: Unit entered failed state.
Aug 23 21:42:21 gdynia systemd[1]: pve-cluster.service: Failed with result 'exit-code'.

System is Debian9.
 
I have reinstalled proxmox package with: apt-get install --reinstall proxmox-ve ssh postfix ksm-control-daemon open-iscsi systemd-sysv
and still my /etc/pve and /etc/corosync.d folders are empty. What else I can do to recover Proxmox without re-installation of entire OS?
 
you need to fix your /etc/hosts file, not reinstall packages. you need an entry resolving your short and qualified hostname to your new IP, and remove the entry resolving to the old one.
 
My /etc/hosts looks like:

1.2.3.4 proxmox.domain.com proxmox pvelocalhost gdynia
192.168.100.1 proxmox.domain.com proxmox pvelocalhost gdynia

what is wrong here?
 
if you still have that line:
Code: 
127.0.0.1       localhost proxmox.domain.com  proxmox pvelocalhost gdynia

it is probably the culprit. try dropping all hostnames but localhost from it.
 
I have removed that (127.0.0.1) line completely, and have still the same. Also it is complaining about:
Code: 
Sep  8 06:25:06 proxmox pveproxy[10022]: /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 1626.
but I am not sure if it related to /etc/hosts or not.
 
horizn said:
192.168.100.1 proxmox.domain.com proxmox pvelocalhost gdynia
Click to expand...

This line must be like this. Assume your server name is gdynia

Code: 
192.168.100.1 gdynia.domain.com gdynia pvelocalhost
[CODE]
 
wolfgang said:
This line must be like this. Assume your server name is gdynia

Code: 
192.168.100.1 gdynia.domain.com gdynia pvelocalhost
[CODE]
Click to expand...

Can I keep 1.2.3.4 (external IP) address in /etc/hosts or it should removed as well?
The reason I am asking is, because Proxmox is running on Debian9 server which also is doing NAT for small local network with NFS/SMB shares as well.
 
wolfgang said:
This line must be like this. Assume your server name is gdynia

Code: 
192.168.100.1 gdynia.domain.com gdynia pvelocalhost
[CODE]
Click to expand...

Even if I leave in /etc/hosts only:
Code: 
192.168.100.1 gdynia.domain.com gdynia pvelocalhost
it still doesn't work. All I can see in syslog is:
Code: 
Sep 10 22:08:52 gdynia pveproxy[2865]: worker 3261 started
Sep 10 22:08:52 gdynia pveproxy[3260]: /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 1626.
Sep 10 22:08:52 gdynia pveproxy[3261]: /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 1626.
Sep 10 22:08:56 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:56 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:56 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pveproxy[3259]: worker exit
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3259 finished
Sep 10 22:08:57 gdynia pveproxy[2865]: starting 1 worker(s)
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3262 started
Sep 10 22:08:57 gdynia pveproxy[3262]: /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 1626.
Sep 10 22:08:57 gdynia pveproxy[3260]: worker exit
Sep 10 22:08:57 gdynia pveproxy[3261]: worker exit
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3261 finished
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3260 finished
Sep 10 22:08:57 gdynia pveproxy[2865]: starting 2 worker(s)
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3263 started
Sep 10 22:08:57 gdynia pveproxy[2865]: worker 3264 started
Sep 10 22:08:57 gdynia pveproxy[3263]: /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 1626.
Sep 10 22:08:57 gdynia pveproxy[3264]: /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 1626.
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:08:57 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:00 gdynia systemd[1]: Starting Proxmox VE replication runner...
Sep 10 22:09:00 gdynia pvesr[3273]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:00 gdynia pvesr[3273]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:00 gdynia pvesr[3273]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:00 gdynia systemd[1]: Started Proxmox VE replication runner.
Sep 10 22:09:01 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:01 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:01 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:02 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:02 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:02 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:02 gdynia pveproxy[3262]: worker exit
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3262 finished
Sep 10 22:09:02 gdynia pveproxy[2865]: starting 1 worker(s)
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3275 started
Sep 10 22:09:02 gdynia pveproxy[3275]: /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 1626.
Sep 10 22:09:02 gdynia pveproxy[3263]: worker exit
Sep 10 22:09:02 gdynia pveproxy[3264]: worker exit
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3263 finished
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3264 finished
Sep 10 22:09:02 gdynia pveproxy[2865]: starting 2 worker(s)
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3276 started
Sep 10 22:09:02 gdynia pveproxy[2865]: worker 3277 started
Sep 10 22:09:02 gdynia pveproxy[3276]: /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 1626.
Sep 10 22:09:02 gdynia pveproxy[3277]: /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 1626.
Sep 10 22:09:06 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:06 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:06 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pveproxy[3275]: worker exit
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3275 finished
Sep 10 22:09:07 gdynia pveproxy[2865]: starting 1 worker(s)
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3278 started
Sep 10 22:09:07 gdynia pveproxy[3278]: /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 1626.
Sep 10 22:09:07 gdynia pveproxy[3276]: worker exit
Sep 10 22:09:07 gdynia pveproxy[3277]: worker exit
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3277 finished
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3276 finished
Sep 10 22:09:07 gdynia pveproxy[2865]: starting 2 worker(s)
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3279 started
Sep 10 22:09:07 gdynia pveproxy[2865]: worker 3280 started
Sep 10 22:09:07 gdynia pveproxy[3279]: /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 1626.
Sep 10 22:09:07 gdynia pveproxy[3280]: /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 1626.
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:07 gdynia pvestatd[2845]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:11 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:11 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:11 gdynia pve-ha-crm[2861]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:12 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:12 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:12 gdynia pve-ha-lrm[2870]: ipcc_send_rec failed: Connection refused
Sep 10 22:09:12 gdynia pveproxy[3278]: worker exit
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3278 finished
Sep 10 22:09:12 gdynia pveproxy[2865]: starting 1 worker(s)
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3292 started
Sep 10 22:09:12 gdynia pveproxy[3292]: /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 1626.
Sep 10 22:09:12 gdynia pveproxy[3279]: worker exit
Sep 10 22:09:12 gdynia pveproxy[3280]: worker exit
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3279 finished
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3280 finished
Sep 10 22:09:12 gdynia pveproxy[2865]: starting 2 worker(s)
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3293 started
Sep 10 22:09:12 gdynia pveproxy[2865]: worker 3294 started
Sep 10 22:09:12 gdynia pveproxy[3293]: /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 1626.
Sep 10 22:09:12 gdynia pveproxy[3294]: /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 1626.

/etc/pve/local/pve-ssl.key exists.

/var/log/pve/tasks/index:
Code: 
UPID:gdynia:00001B5E:0002EB5D:5985BD60:qmstart:100:root@pam: 5985BD63 OK
UPID:gdynia:00001BA2:0002EDE9:5985BD67:vncproxy:100:root@pam: 5985BD69 OK
UPID:gdynia:00001BBC:0002EED7:5985BD69:vncproxy:100:root@pam: 5985BD6A Failed to run vncproxy.
UPID:gdynia:00001BC5:0002F22B:5985BD72:vncproxy:100:root@pam: 5985BD73 Failed to run vncproxy.
UPID:gdynia:00001BD9:0002F32D:5985BD74:qmstart:100:root@pam: 5985BD76 OK
UPID:gdynia:00001C45:0002FC91:5985BD8C:vncproxy:100:root@pam: 5985BE13 OK
UPID:gdynia:00001D04:00033157:5985BE14:vncproxy:100:root@pam: 5985BE14 Failed to run vncproxy.
UPID:gdynia:00002AE1:00062A6B:5985C5B0:qmcreate:101:root@pam: 5985C5B0 OK
UPID:gdynia:00002B77:00064F93:5985C60F:qmstart:101:root@pam: 5985C610 OK
UPID:gdynia:00002BBB:000652F1:5985C618:vncproxy:101:root@pam: 5985C655 OK
UPID:gdynia:00002C0A:00066AC1:5985C655:qmstop:101:root@pam: 5985C656 OK
UPID:gdynia:00002C17:00066B26:5985C656:vncproxy:101:root@pam: 5985C656 Failed to run vncproxy.
UPID:gdynia:00002C53:00067B27:5985C67F:qmstart:101:root@pam: 5985C681 OK
UPID:gdynia:00002C97:00067DA6:5985C685:vncproxy:101:root@pam: 5985CE96 OK
UPID:gdynia:00003708:0009A478:5985CE96:vncproxy:101:root@pam: 5985CE97 Failed to run vncproxy.
UPID:gdynia:00003756:0009BA70:5985CECF:vncproxy:100:root@pam: 5985CECF Failed to run vncproxy.
UPID:gdynia:00003764:0009BE1B:5985CED8:qmdestroy:100:root@pam: 5985CEDB OK
UPID:gdynia:00003817:0009D8FC:5985CF1D:stopall::root@pam: 5985CF1D OK
UPID:gdynia:000007A9:000022AA:599327DE:startall::root@pam: 59932818 unexpected status
UPID:gdynia:000006E4:0000235E:59932926:startall::root@pam: 5993372B received interrupt
UPID:gdynia:00000865:0000236C:59933864:startall::root@pam: 5999C724 unexpected status
UPID:gdynia:00000A2D:00000C8E:5999C7F7:startall::root@pam: 599DF714 unexpected status
UPID:gdynia:00000A30:00000D56:599DF7E8:startall::root@pam: 59B00B82 received interrupt
UPID:gdynia:00000B1F:00000D64:59B06636:startall::root@pam: 59B06637 OK
UPID:gdynia:00001229:00874549:59B1C05E:stopall::root@pam: 59B1C05E OK
UPID:gdynia:00000B4B:00000A55:59B1C12B:startall::root@pam: 59B1C12B OK
UPID:gdynia:000069BE:01855372:59B5A5BC:stopall::root@pam: 59B5A5BC OK
UPID:gdynia:00000B5A:00000A6D:59B5A689:startall::root@pam: 59B5A689 OK
UPID:gdynia:00001026:0000EB9C:59B5A8C8:stopall::root@pam: 59B5A8C8 OK
UPID:gdynia:00000B6A:00000B89:59B5A997:startall::root@pam: 59B5A997 OK
 
you need to restart the pve-cluster service after editing the hosts file.. (based on your logs, it is not mounted)
 
fabian said:
you need to restart the pve-cluster service after editing the hosts file.. (based on your logs, it is not mounted)
Click to expand...

I know, I tried it before. Unfortunately pve-cluster won't restart. It is complaining about:
Code: 
# /etc/init.d/pve-cluster restart
[....] Restarting pve-cluster (via systemctl): pve-cluster.serviceJob for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
 failed!

# 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 Mon 2017-09-11 09:29:11 BST; 8s ago
  Process: 31239 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Sep 11 09:29:11 gdynia systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 11 09:29:11 gdynia pmxcfs[31239]: fuse: mountpoint is not empty
Sep 11 09:29:11 gdynia pmxcfs[31239]: fuse: if you are sure this is safe, use the 'nonempty' mount option
Sep 11 09:29:11 gdynia pmxcfs[31239]: [main] crit: fuse_mount error: File exists
Sep 11 09:29:11 gdynia pmxcfs[31239]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 11 09:29:11 gdynia systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Sep 11 09:29:11 gdynia systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 11 09:29:11 gdynia systemd[1]: pve-cluster.service: Unit entered failed state.
Sep 11 09:29:11 gdynia systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
 
that means you have put files into /etc/pve while it was not mounted. (re) move them and then restart the pve-cluster service.
 
  • Like
Reactions: horizn
fabian said:
that means you have put files into /etc/pve while it was not mounted. (re) move them and then restart the pve-cluster service.
Click to expand...
That was the issue. Problem solved. Thank you for your patience.
 
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
Back