Proxmox clustering with running VM`s

M

Mecanik

Well-Known Member
Mar 2, 2017
173
5
58
33
I am facing a hard dilemma here. I am running Proxmox 4.x with vm's on it, and it's reaching the resource limits, so I want to setup clustering.

I have setup another server with the same Proxmox 4.x ( but no vm's, just empty ) and I would like to add it to my primary one that is currently running vm's.

My question is, can I setup clustering on server A ( with running vm's ) and connect to it server B ( empty ) without the risk of loosing all the vm's on server A ?

Any recommendation, advice or information is much appreciated!
 
I already searched on Google quite some time about this, but I cannot get a guaranteed answer. Please advise...
 
Mecanik said:
My question is, can I setup clustering on server A ( with running vm's ) and connect to it server B ( empty ) without the risk of loosing all the vm's on server A ?
Click to expand...

Yes, but you need to connect server B (emtpy) to server A (where you create the cluster first).
 
Yes, thank you for your reply. That`s exactly my plan, although I have never setup clustering with Proxmox before... if I by some any chance loose the VM's or they stop or whatever... can I "fix" them ?

Server A has 20+ VM's running at the moment and Server B is completely empty.

PS: My server A has: Virtual Environment 4.3-1/e7cdc165 while the server B has: Virtual Environment 4.4-12/e71b7a74 - does this create a conflict ?

Many thanks again.
 
Mecanik said:
if I by some any chance loose the VM's or they stop or whatever... can I "fix" them ?
Click to expand...

Here are two recommendation

1.) Always make backups of your VMs (make sure you can restore them - test this at regular intervals)
2.) Try to get practice on a test environment before you do such jobs on your production servers.

Mecanik said:
PS: My server A has: Virtual Environment 4.3-1/e7cdc165 while the server B has: Virtual Environment 4.4-12/e71b7a74 - does this create a conflict ?
Click to expand...

I recommend to update them to the same version.
 
@dietmar Thank you, but I don`t know how to update server A to be exactly like server B without downtime... ( sorry, I`m new to proxmox )

@udo Thank you, I will try to do this.
 
Following this tutorial: https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster I am afraid of this warning:

WARNING: Adding a node to the cluster will delete it's current /etc/pve/storage.cfg. If you have VMs stored on the node, be prepared to add back your storage locations if necessary. Even though the storage locations disappear from the GUI, your data is still there.

This would not be my case, because I have Server B empty which I am attaching to Server A (with running VM's) no ?
 
Mecanik said:
Following this tutorial: https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster I am afraid of this warning:

WARNING: Adding a node to the cluster will delete it's current /etc/pve/storage.cfg. If you have VMs stored on the node, be prepared to add back your storage locations if necessary. Even though the storage locations disappear from the GUI, your data is still there.

This would not be my case, because I have Server B empty which I am attaching to Server A (with running VM's) no ?
Click to expand...
Hi,
if you define the cluster on node a (where the VMs run) the "not-cluster-config" will be the same (and you have an backup ;-) ).

Should be not an problem!

Udo
 
I understand, thank you for answering. Amazing forum an people around here. But I am still afraid to do this :( Because if I do something wrong, and my customers are affected... then I don't see a "way out" of this.

In the same time, I am "forced" to do clustering...
 
Mecanik said:
I understand, thank you for answering. Amazing forum an people around here. But I am still afraid to do this :( Because if I do something wrong, and my customers are affected... then I don't see a "way out" of this.

In the same time, I am "forced" to do clustering...
Click to expand...
Hi,
be not afraid, but think about what you are doing.

If you do an backup of /etc/pve you have all important config files.
If you make an mistake and the config is gone, you can't access the webgui perhaps - but all running VMs are still running!!
But you have than perhaps no quorum to start an new VM.

So the situation is not bad - even if something go wrong. But do no reboots of node a or so on...

Udo
 
Thank you, by the way is vlan really needed ? Many videos and tutorials show usage of vlan, but my current situation... cannot do that.
 
If I click on server A "package versions", I get this:

proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve) pve-manager: not correctly installed (running version: 4.3-1/e7cdc165) pve-kernel-4.2.8-1-pve: 4.2.8-41 pve-kernel-4.4.19-1-pve: 4.4.19-66 lvm2: 2.02.116-pve3 corosync-pve: not correctly installed libqb0: 1.0-1 pve-cluster: not correctly installed qemu-server: 4.0-88 pve-firmware: not correctly installed libpve-common-perl: 4.0-73 libpve-access-control: not correctly installed libpve-storage-perl: not correctly installed pve-libspice-server1: not correctly installed vncterm: not correctly installed pve-qemu-kvm: not correctly installed pve-container: 1.0-75 pve-firewall: not correctly installed pve-ha-manager: not correctly installed ksm-control-daemon: 1.2-1 glusterfs-client: not correctly installed lxc-pve: not correctly installed lxcfs: not correctly installed criu: 1.6.0-1 novnc-pve: 0.5-8 zfsutils: 0.6.5.7-pve10~bpo80

Please dont tell me I messed up :(

I ran again apt-get upgrade, and now the message is this:

Job for pve-firewall.service failed. See 'systemctl status pve-firewall.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up pve-docs (4.4-3) ...
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
 
Last edited:
Well I failed, I tried to add server B (empty), but something failed and now I cannot retry anymore:

can't create shared ssh key database '/etc/pve/priv/authorized_keys'
cluster not ready - no quorum?
unable to add node: command failed (ssh xx.xx.xxx.xx -o BatchMode=yes pvecm addnode ns395767 --force 1)

Any advice ?

And now I have this status on server A:

Code: 
root@ns3030900:~# pvecm status
Quorum information
------------------
Date:             Sat Mar  4 11:06:10 2017
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1/4
Quorate:          No

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 xx.xx.xxx.xx (local)

UPDATE:

Because I failed adding server B to the cluster, I am reinstalling server B, and removed the partially added server B in server A by following:

Code: 
# stop service
$ systemctl stop pvestatd.service
$ systemctl stop pvedaemon.service
$ systemctl stop pve-cluster.service

# edit through sqlite, check, delete, verify
$ sqlite3 /var/lib/pve-cluster/config.db
sqlite> select * from tree where name = 'corosync.conf';
254327|0|254329|0|1480944811|8|corosync.conf|totem {
version: 2
[...]
sqlite> delete from tree where name = 'corosync.conf';
sqlite> select * from tree where name = 'corosync.conf';
sqlite> .quit

# start service
$ systemctl start pve-cluster.service
$ systemctl start pvestatd.service
$ systemctl start pvedaemon.service

I did not reboot server A and I do not intend to either, waiting for server B to reinstall and I will try again...

UPDATE 2:

Failed again, and now on server A I cannot see the VM`s anymore, but they run in the background...

Additional logs:
Code: 
root@ns3030900:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: failed (Result: exit-code) since Sat 2017-03-04 13:37:11 CET; 15s ago
  Process: 9770 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 10399 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
 Main PID: 9768 (code=exited, status=0/SUCCESS)

Mar 04 13:37:01 ns3030900 pmxcfs[10399]: [main] notice: unable to aquire pmxcfs lock - trying again
Mar 04 13:37:01 ns3030900 pmxcfs[10399]: [main] notice: unable to aquire pmxcfs lock - trying again
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] notice: exit proxmox configuration filesystem (-1)
Mar 04 13:37:11 ns3030900 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Mar 04 13:37:11 ns3030900 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Mar 04 13:37:11 ns3030900 systemd[1]: Unit pve-cluster.service entered failed state.
root@ns3030900:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: failed (Result: exit-code) since Sat 2017-03-04 13:37:11 CET; 26s ago
  Process: 9770 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 10399 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
 Main PID: 9768 (code=exited, status=0/SUCCESS)

Mar 04 13:37:01 ns3030900 pmxcfs[10399]: [main] notice: unable to aquire pmxcfs lock - trying again
Mar 04 13:37:01 ns3030900 pmxcfs[10399]: [main] notice: unable to aquire pmxcfs lock - trying again
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Mar 04 13:37:11 ns3030900 pmxcfs[10399]: [main] notice: exit proxmox configuration filesystem (-1)
Mar 04 13:37:11 ns3030900 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Mar 04 13:37:11 ns3030900 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Mar 04 13:37:11 ns3030900 systemd[1]: Unit pve-cluster.service entered failed state.

UPDATE 3:

Now even the GUI doesnt work anymore... just all of a sudden :(
 
Last edited:
It`s messed up... situation is critical :( I still have the VM's running, but the web GUI does not work at all... don't know what to do :(
 
I even tried to restore configuration: tar -xvf /root/etc_pve.tar -C /etc/pve
But failed:

Code: 
etc/pve/
etc/pve/.debug
tar: etc/pve/.debug: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.debug: Cannot change mode to rw-r-----: Function not implemented
etc/pve/local
tar: etc/pve/local: Cannot create symlink to ‘n’: Function not implemented
etc/pve/.version
tar: etc/pve/.version: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.version: Cannot change mode to r--r-----: Function not implemented
etc/pve/.rrd
tar: etc/pve/.rrd: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.rrd: Cannot change mode to r--r-----: Function not implemented
etc/pve/.vmlist
tar: etc/pve/.vmlist: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.vmlist: Cannot change mode to r--r-----: Function not implemented
etc/pve/openvz
tar: etc/pve/openvz: Cannot create symlink to ‘n’: Function not implemented
etc/pve/lxc
tar: etc/pve/lxc: Cannot create symlink to ‘n’: Function not implemented
etc/pve/.clusterlog
tar: etc/pve/.clusterlog: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.clusterlog: Cannot change mode to r--r-----: Function not implemented
etc/pve/qemu-server
tar: etc/pve/qemu-server: Cannot create symlink to ‘n’: Function not implemented
etc/pve/.members
tar: etc/pve/.members: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.members: Cannot change mode to r--r-----: Function not implemented
etc/pve/user.cfg
tar: etc/pve/user.cfg: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/user.cfg: Cannot change mode to rw-r-----: Function not implemented
etc/pve/pve-www.key
tar: etc/pve/pve-www.key: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/pve-www.key: Cannot change mode to rw-r-----: Function not implemented
etc/pve/priv/
etc/pve/priv/authorized_keys
tar: etc/pve/priv/authorized_keys: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/priv/lock/
etc/pve/priv/shadow.cfg
tar: etc/pve/priv/lock: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/priv/shadow.cfg: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/priv/authkey.key
tar: etc/pve/priv/authkey.key: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/priv/known_hosts
tar: etc/pve/priv/known_hosts: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/priv/pve-root-ca.key
tar: etc/pve/priv/pve-root-ca.key: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/priv/pve-root-ca.srl
tar: etc/pve/priv/pve-root-ca.srl: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/datacenter.cfg
tar: etc/pve/priv: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/datacenter.cfg: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/datacenter.cfg: Cannot change mode to rw-r-----: Function not implemented
etc/pve/authkey.pub
tar: etc/pve/authkey.pub: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/authkey.pub: Cannot change mode to rw-r-----: Function not implemented
etc/pve/storage.cfg
tar: etc/pve/storage.cfg: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/storage.cfg: Cannot change mode to rw-r-----: Function not implemented
etc/pve/pve-root-ca.pem
tar: etc/pve/pve-root-ca.pem: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/pve-root-ca.pem: Cannot change mode to rw-r-----: Function not implemented
etc/pve/vzdump.cron
tar: etc/pve/vzdump.cron: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/vzdump.cron: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/
etc/pve/nodes/ns3030900/
etc/pve/nodes/ns3030900/priv/
etc/pve/nodes/ns3030900/openvz/
tar: etc/pve/nodes/ns3030900/priv: Cannot change ownership to uid 0, gid 33: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/
tar: etc/pve/nodes/ns3030900/openvz: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/openvz: Cannot change mode to rwxr-xr-x: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/118.conf
tar: etc/pve/nodes/ns3030900/qemu-server/118.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/118.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/116.conf
tar: etc/pve/nodes/ns3030900/qemu-server/116.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/116.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/125.conf
tar: etc/pve/nodes/ns3030900/qemu-server/125.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/125.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/122.conf
tar: etc/pve/nodes/ns3030900/qemu-server/122.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/122.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/123.conf
tar: etc/pve/nodes/ns3030900/qemu-server/123.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/123.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/124.conf
tar: etc/pve/nodes/ns3030900/qemu-server/124.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/124.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/113.conf
tar: etc/pve/nodes/ns3030900/qemu-server/113.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/113.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/107.conf
tar: etc/pve/nodes/ns3030900/qemu-server/107.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/107.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/100.conf
tar: etc/pve/nodes/ns3030900/qemu-server/100.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/100.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/121.conf
tar: etc/pve/nodes/ns3030900/qemu-server/121.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/121.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/102.conf
tar: etc/pve/nodes/ns3030900/qemu-server/102.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/102.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/111.conf
tar: etc/pve/nodes/ns3030900/qemu-server/111.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/111.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/104.conf
tar: etc/pve/nodes/ns3030900/qemu-server/104.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/104.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/105.conf
tar: etc/pve/nodes/ns3030900/qemu-server/105.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/105.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/103.conf
tar: etc/pve/nodes/ns3030900/qemu-server/103.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/103.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/115.conf
tar: etc/pve/nodes/ns3030900/qemu-server/115.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/115.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/110.conf
tar: etc/pve/nodes/ns3030900/qemu-server/110.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/110.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/109.conf
tar: etc/pve/nodes/ns3030900/qemu-server/109.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/109.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/112.conf
tar: etc/pve/nodes/ns3030900/qemu-server/112.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/112.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/119.conf
tar: etc/pve/nodes/ns3030900/qemu-server/119.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/119.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/qemu-server/114.conf
tar: etc/pve/nodes/ns3030900/qemu-server/114.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server/114.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/pve-ssl.pem
tar: etc/pve/nodes/ns3030900/qemu-server: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/qemu-server: Cannot change mode to rwxr-xr-x: Function not implemented
tar: etc/pve/nodes/ns3030900/pve-ssl.pem: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/pve-ssl.pem: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/pve-ssl.key
tar: etc/pve/nodes/ns3030900/pve-ssl.key: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/pve-ssl.key: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/lrm_status
tar: etc/pve/nodes/ns3030900/lrm_status: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/lrm_status: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/lxc/
etc/pve/nodes/ns3030900/pveproxy-ssl.key
tar: etc/pve/nodes/ns3030900/lxc: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/lxc: Cannot change mode to rwxr-xr-x: Function not implemented
tar: etc/pve/nodes/ns3030900/pveproxy-ssl.key: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/pveproxy-ssl.key: Cannot change mode to rw-r-----: Function not implemented
etc/pve/nodes/ns3030900/pveproxy-ssl.pem
tar: etc/pve/nodes/ns3030900/pveproxy-ssl.pem: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900/pveproxy-ssl.pem: Cannot change mode to rw-r-----: Function not implemented
etc/pve/.le/
tar: etc/pve/nodes/ns3030900: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes/ns3030900: Cannot change mode to rwxr-xr-x: Function not implemented
tar: etc/pve/nodes: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/nodes: Cannot change mode to rwxr-xr-x: Function not implemented
etc/pve/.le/account.key
tar: etc/pve/.le/account.key: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.le/account.key: Cannot change mode to rw-r-----: Function not implemented
etc/pve/.le/account.conf
tar: etc/pve/.le/account.conf: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.le/account.conf: Cannot change mode to rw-r-----: Function not implemented
etc/pve/firewall/
tar: etc/pve/.le: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/.le: Cannot change mode to rwxr-xr-x: Function not implemented
etc/pve/firewall/119.fw
tar: etc/pve/firewall/119.fw: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/firewall/119.fw: Cannot change mode to rw-r-----: Function not implemented
etc/pve/firewall/111.fw
tar: etc/pve/firewall/111.fw: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/firewall/111.fw: Cannot change mode to rw-r-----: Function not implemented
tar: etc/pve/firewall: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve/firewall: Cannot change mode to rwxr-xr-x: Function not implemented
tar: etc/pve: Cannot change ownership to uid 0, gid 33: Function not implemented
tar: etc/pve: Cannot change mode to rwxr-xr-x: Function not implemented
tar: Exiting with failure status due to previous errors

UPDATE:

I have restored the old configuration:

tar -xvf /root/etc_pve.tar --no-same-owner -C /etc/pve

And restarted pveproxy, and now the web GUI is working, but still the VM's are not showing up...
 
Last edited:
I would really appreciate if someone would answer me, and give me some directions with my problem, because this is a production server and I'm basically fucked with this proxmox...

The latest errors I have:

- No VM's can be created
- The GUI does not show any VM's

And running this command shows me:

root@ns3030900:~# pmxcfs -l
[database] crit: select returned error: database disk image is malformed
[database] crit: DB load failed
[main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
[main] notice: exit proxmox configuration filesystem (-1)
 
Mecanik said:
I would really appreciate if someone would answer me, and give me some directions with my problem, because this is a production server and I'm basically fucked with this proxmox...

The latest errors I have:

- No VM's can be created
- The GUI does not show any VM's

And running this command shows me:

root@ns3030900:~# pmxcfs -l
[database] crit: select returned error: database disk image is malformed
[database] crit: DB load failed
[main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
[main] notice: exit proxmox configuration filesystem (-1)
Click to expand...

This forum is mainly user to user support, if you have a production enviornment and have an issue that's effecting you then your probably best opening a Support Ticket and working directly with Proxmox.

If not wait for one of the dev team to pop past the forum and offer some guidance.
 
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