Recent content by hugosxm

It is not possible to store a lxc on a lvm2 Then snap the lvm Do the backup with the snap And delete the snap when backup complete ? Lxc is just a bunch of file dropped on a ext4 filesystem or there is a specific lxc filesystem ?

I tried that but this is not working :/ I really don't understand why you don't keep BOTH ! lvm thin for who want VM snapshot And classic lvm for who want the snapshot backup mode ... As i understand, with lvm thin pool you create a LV ( thin type ) then you store several CT on the same...

iIsee that lvm on proxmox now support LXC but when i do a backup in snapshot mode, it does not create a lvm snap and try to do it in suspend mode which is verrrryyyyyy loooonnnnnggg ... is this normal ? I also tested snapshot mode with zfs on my other server that have ECC... 53 seconds back up...

I have reinstalled proxmox on the two nodes, and when i create the cluster on the first one, corosync does not want to start... the only thing that corosync can tell me is that it is exiting with code 1... How can i try to solve this ?! maybe there is a debug mode ?

ys i know but this is not working :/ root@proxmox2:~# pvecm status Cannot initialize CMAP service root@proxmox2:~# pvecm expected 1 Cannot initialize CMAP service here is more info : nov. 01 20:27:14 proxmox2 corosync[1624]: [SERV ] Service engine loaded: corosync configuration map...

up ! i am still trying to figuring it out :/ i want to modify the corosync.conf in the second node cat /etc/pve/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: proxmox nodeid: 1 quorum_votes: 1 ring0_addr: proxmox } node {...

i did what you said, now i have this in the log : oct. 28 15:25:09 proxmox2 pve-ha-crm[2067]: ipcc_send_rec failed: Connexion refuséeoct. 28 15:25:09 proxmox2 pve-ha-crm[2067]: ipcc_send_rec failed: Connexion refuséeoct. 28 15:25:09 proxmox2 pve-ha-crm[2067]: ipcc_send_rec failed: Connexion...

Thnaks for the help but the real problem is that corosync does not want to start on node 2The log is not showing helpfull information :/ PLease see what i have just found on the node 2 journal : Starting Corosync Cluster Engine... oct. 28 10:13:06 proxmox2 corosync[11907]: [MAIN ] Corosync...

on primary node root@proxmox /home/admin # systemctl status corosync ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled) Active: active (running) since lun. 2015-10-26 10:14:48 CET; 25min ago Process: 12004...

i followed the wiki created the cluster on the first node then when i add the second one : Are you sure you want to continue connecting (yes/no)? yes root@172.20.50.254's password: copy corosync auth key stopping pve-cluster service backup old database Job for corosync.service failed. See...

Thanks for the answer :) The procedure is still the same as pve 3.4? I need to put the "two-nodes" tag in the configuration file?

Hi ! I am understanding that we cannot do HA with only two nodes in PVE4 But can i create a cluster to have unified management of the two hypervisor ? Or it is not possible because i will not have quorum and backup will fail etc etc ... ? I don't want to enable HA, just create a basic...

i am ssssooo sorry ! i figured it out ! i edited manually the interfaces files and put eth0, now it is working but this is strange that the installer have not done that ?! i was so afraid that my new server came with a faulty motherboard :S

Hi guys ! i have a brandnew supermicro 1u server with 4 gig port but they are not working Switch and server are blinking during bios then when proxmox boots up, every card became dark and dead mii-tool show no link can it be a watchdog related problem ? thanks by advance PS : proxmox...

OK thanks I will try swap but the drive are directly connected to motherboard, Maybe there is a bad cable... I opened a RMA at Western digital just in case :)