Search results

  1. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp no. normal pve repo. also got the problem that it lost connections to the VMs sockets.
  2. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp It where working without a problem for 2weeks. then after latest update it started to fail.
  3. problem with editiing conf files of kvm anc ct

    with the pvecm you can put a wote on the local machine and then restart i think its pve-cluster , or if its cman and then get write access.
  4. automatic/script VM delete possible?

    in console you can use qm to remove vm.
  5. problem with editiing conf files of kvm anc ct

    test service cmon restart; service pve-cluster restart
  6. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp Oct 9 14:07:22 cloud904 kernel: sd 5:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). Oct 9 14:07:26 cloud904 corosync[551453]: [TOTEM ] FAILED TO RECEIVE Oct 9 14:07:38 cloud904...
  7. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp it where the first node i did set up in this cluster. else from that its the same hardware as the rest of them. Best Regards Coffe
  8. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp tested multicast could not see any problem, its only this node.. the other 5 is working good. networkis not so heawy loaded .. did try to use the dedicated network for them but it selected to use this. all...
  9. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    Re: CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endp its lots of info this is the first sign after a restart of services that its goind to fail again:corosync[535241]: [TOTEM ] FAILED TO RECEIVE
  10. CLUSTER problem: pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint

    one of 6 nodes in my cluster keeps falling out. pvedaemon[481993]: WARNING: ipcc_send_rec failed: Transport endpoint is not connected notice its stops the cman. one way of getting it back for 1-30 min is to restart service cman and pve-cluster. is it any way of debugging the pvedeamon error ...
  11. request: in GUI have option of restoring to unique.

    As there as far as i know , no way when using kvm to clone a server, we use a template server that we backup and restore to get a new server. as the new gui of 2.* have nice restor backupfunctions it would be nice if it also did have the option of --unique. BR //Coffe
  12. Help with network settings needed

    second part i see . is that you should not give eth0 any ip, just the wmbr0 and set its port to eth0.
  13. Help with network settings needed

    Hello. What kind of networks are you going for ? i am not sure a bridge would work without a any ports.
  14. upgrading from 1.9

    seems like the VM i where testing with where created with scsi , the others all use virtio, so it works. tomorrow will be grand day of moving 40+ VMs. Tnx everyone :)
  15. upgrading from 1.9

    lvchange -ay /dev/volumegroupname/vm_id seems to worked. No. VM stills says it cant find any boot on it, so i did test to start it up in old cluster, ans there it did work.
  16. upgrading from 1.9

    Hi, Havent seen anything about creating cluster before adding VMs , If i try start it, it says it dont find HD image. but when checking the storage i can see it. but a ls /dev/mapper dont show it.
  17. upgrading from 1.9

    got 2 new questions. 1.i have moved the .conf file to the new server, but it seems the system dont connect to image in shared storage. how can i "mount" it so it finds it ? ( /dev/mapper/ ) 2. do i have to make the cluster before adding nodes ( its the first server in the cluster to be)...
  18. upgrading from 1.9

    So today we are going to install a new 2.* server to build the new cluster. as we only use iscsi will we run in to big problems if we have it shared between a 1.9 cluster and a 2.* ? Second question is whats the best way of moving a vm from the 1.9 cluster, seems litle strange to dump it and...
  19. upgrading from 1.9

    Seems like we are going to get a OK to upgade. So i just like to get som input. have today a cluster of 6 servers anv about 20VMs on all of them. My ide where to use a old server to install 2.* and then copy the clients over. but i dont like to keep that server in cluster so is there a easy...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!