Search results

  1. O

    /etc/pve not writeable

    Is it just me or is a cluster of more then 8 servers a complete fantasy? Everytime it some what works it dies for no reason.
  2. O

    Moving proxmox to another network

    Then it's easy, just change the /etc/network/interfaces settings, the /etc/hosts and reboot the server.
  3. O

    Moving proxmox to another network

    Perhapse the best way is to dismantle the cluster at the old site, so remove all nodes from the cluster. And create a new cluster on the new location. Never tried it, but might work.
  4. O

    Moving proxmox to another network

    I've tried it once but it was no succes. Changing the external IPs of a cluster is, if I'm not mistaken, officially not possible.
  5. O

    /etc/pve not writeable

    We I finally got a lot of the servers joined, but 2 aren't able to join. They have decided to join to gether instead of with the rest. So got a set of 2 and a set of 9 server in the same cluster in the same IP space at the same switch... odd to say the least. Syslog states, so is it would...
  6. O

    /etc/pve not writeable

    No nothing special. All traffic runs over 1 switch within 1 vlan. All quite basic. What locks the cman from restarting? Because I think if you just loses it's current sync completely it can rejoin.
  7. O

    /etc/pve not writeable

    That's highly unlikely because if that was the case the cluster could never work. I verified is, and omping works: xxx.xxx.xxx.108 : unicast, seq=1, size=69 bytes, dist=0, time=0.123ms xxx.xxx.xxx.108 : multicast, seq=1, size=69 bytes, dist=0, time=0.138ms xxx.xxx.xxx.108 : unicast, seq=2...
  8. O

    /etc/pve not writeable

    Hi Dietmar, No HA, and no fencing device.
  9. O

    /etc/pve not writeable

    Hi Dietmar, If you mean cman, it's not running I assume: root@srv5:~# service cman restart Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... Timed-out waiting for cluster [FAILED] I've tried starting cman without quiting it first but...
  10. O

    /etc/pve not writeable

    Hi Dietmar, A lot of messages, I assume the important one is "crit: cpg_send_message failed", but how can I fix this? A partial dump: Jan 23 10:31:43 srv5 pmxcfs[558599]: [status] crit: cpg_send_message failed: 9 Jan 23 10:31:43 srv5 pmxcfs[558599]: [status] crit: cpg_send_message failed: 9...
  11. O

    /etc/pve not writeable

    srv2; pvecm nodes Node Sts Inc Joined Name 1 M 20284 2015-01-21 08:35:42 srv2 2 M 20300 2015-01-21 08:35:42 srv23 3 M 20348 2015-01-21 08:36:50 srv8 4 M 20340 2015-01-21 08:36:38 srv7 5 M 20296 2015-01-21 08:35:42 srv32 6 M...
  12. O

    /etc/pve not writeable

    proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve) pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1) pve-kernel-2.6.32-20-pve: 2.6.32-100 pve-kernel-2.6.32-29-pve: 2.6.32-126 pve-kernel-2.6.32-26-pve: 2.6.32-114 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve...
  13. O

    /etc/pve not writeable

    I Finaly got it working... then an hour later 1 servers load went us and everything broke AGAIN! Getting quite annoyed with this. The most stupid part is that most of the servers clustat say that all servers are online, which is not the case, there is not 1 server in the cluster able to restart...
  14. O

    /etc/pve not writeable

    pvecm nodes shows all nodes online. But on 1 machine it says that only that machine is online. Node Sts Inc Joined Name 1 M 20356 2015-01-21 08:36:51 srv2 2 M 20356 2015-01-21 08:36:51 srv23 3 M 20356 2015-01-21 08:36:51 srv8 4 M 20356...
  15. O

    /etc/pve not writeable

    Hi, I have a proxmox 3.2 cluster with a dozen nodes. When I run backups of a couple CTs in the weekend the cluster falls apart. I tried to remove the backup cron, but the /etc/pve is not writeable. Also creating new containers is not possible anymore. Any suggestions on how to debug...
  16. O

    Error restoring vzdump from PVE-2.3 on PVE-3.1

    Ok... writing stuff here makes things more clearly appently ;) I've removed the 103.mount file and nog it appears to work... Can anyone from the proxmox team confirm that this is the right way? Or did I just broke it at another place without noticing it (yet) :-)
  17. O

    Error restoring vzdump from PVE-2.3 on PVE-3.1

    What is the logic in this? SRC=/www/101 DST=/www And why does the other VM (101) have no /etc/pve/openvz/101.mount Is this a legacy issue?
  18. O

    Error restoring vzdump from PVE-2.3 on PVE-3.1

    I have an vzdump from an openvz container made on PVE 2.3, and trying to restore it on 3.1 but it throws this error: Starting container ... mount: special device /www/101 does not exist Error executing mount script /etc/pve/openvz/103.mount TASK ERROR: command 'vzctl start 103' failed: exit...
  19. O

    No Quorum in 2 server cluster

    That indeed was the problem. Thanks for the tip! One thing i'm trying to fix now... I had a VM on the second server (srv25) which I had to put there to sell the VM on it. But it's nog showing in the interface. I know it's not the correct way but is there a way to get the VM in the cluster? The...
  20. O

    No Quorum in 2 server cluster

    Hi, I've made proxmox clusters for quite a while now. And now I'm having difficulty putting 2 servers in a cluster (PVE 2.3). Node 1: srv3, created the cluster on this one. This server had in a previous 15 nodes in it, but they are removed, en now I want to add a new clean node. Node 2: srv25...

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 yours easily in our online shop.

Buy now!