Search results

I issued the command on all servers, problem stil exist 2017-08-20 11:11:30 shutdown CT 101 2017-08-20 11:11:30 # lxc-stop -n 101 --timeout 180 2017-08-20 11:11:32 # lxc-wait -n 101 -t 5 -s STOPPED 2017-08-20 11:11:34 starting migration of CT 101 to node 'Server2' (192.168.100.12) 2017-08-20...

It works only on the Server where was created at the beginning...

Uhmm no. I didn't touch it. See image attached... Still can't understand.

root@Server2:~# systemctl status lxc@101.service ● lxc@101.service - LXC Container: 101 Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled) Drop-In: /usr/lib/systemd/system/lxc@.service.d └─pve-reboot.conf Active: failed (Result: exit-code)...

uhm yes, after ha-manager set ct:101 --state disabled i was able to migrate back CT from Server 2 to 3 which is where was created. If i try again to migrate from 3 to 2 i get this: Task viewer: CT 101 - Start OutputStatus Stop Job for lxc@101.service failed because the control process...

Okay, Solved. I tried to open an SSH connection between servers and i trusted the ssh connection. but somethings goes wrong anyway Task viewer: HA 101 - Migrate Output Status Stop Requesting HA migration for CT 101 to node Server3 service 'ct:101' in error state, must be disabled and fixed...

Hi guys, i'm trying to migrate a CT from Server 3 to Sever2 HA avaibility is configured right... i get this type of error: task started by HA resource agent 2017-08-18 10:49:23 # /usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=Server2' root@192.168.100.12 /bin/true 2017-08-18 10:49:23 Host...

So if i would like to install more than a VM, on the LVM i should unflag it? Thanks Anto

Hi guys, when we are going to create a shared storage iscsi what does it means "Use LUN's Directly"? When we should flag it? and when we should do not? i'm using two LUN's Thanks

Yes, you were right... i tried to destroy and to build again without any partition table an Hdd on the shared storage and now i'm able to create at least one LUN but not two... i'm able to map LVM0 to Shared0, but not LVM1 to Shared1. On the freeBSD side a configured to LUNs of 50Gb per each...

Yeeeah that works. I have another question releated to LVM and shared storage iSCSI, i need to open a new thread? Thanks Anto

Nice. Work for VMs, but not for container. If i go on the resources tab of the container i can't delete the HardDisk Any suggestions? Thanks

I deleted it completely. Those images does not exit anymore. But what does it means? remove the HD? Thanks

Hi team, after i changed some setting on my shared storage iSCSI i'm not able to delete VMs and container via proxmox GUI. There is a way in order to delete them via command line interface? See image attached. Thanks :) Antonino

So, i created two LUNs on the FreeBSD iscsi configuration side. Then i goes to proxmox GUI and i created 2 iscsi one point to LUN0 (50Gb) and the second one pointing to LUN1 (50Gb). Then i created two LVM and i choose as based storage "Exiting Volume Groups", if i choose as based storage...

So, i need to create anyway fist the iSCSI pointing to the shared storage from Datacenter ----> Storage ----> add on proxmox right? Then i have to create an LVM? Thanks

Hi guys, i need a clarification i'm using 3 server in a cluster all connected to a shared storage. Shared storage as a HDD of 128gb for VMdata Is if possible let's say to create 2 LUN's of 60GB on the shared storage, then connect the LUN via LVM on the proxmox and install let's say 5 Vm's...

Any suggestions...?

Hi guys, I build up an environment like that, i have 3 proxmox servers in clustering mode, they are also connected to a shared storage. All server are virtualized, HA works and every things was set up properly to gain minimal functions. I'm using one HDD 2on the shared storage about 128Gb...

Okay, thanks... :)