Search results

Interesting, problem seems to be load related. Backups are done using rsync which shouldn't cause issues with local storage. Have you tried looking at system stats while backup is in progress? I personally like nmon which lets me to look at all the stats(disk io, network, cpu, ram) at the same...

Are containers stored on the same nfs server as the backups? That sounds like the problem I had with ZFS sync option, because they were killed exactly when doing backups. By default NFS uses async mode, meaning it won't wait for local storage to finish writing data and respond to client as soon...

I've already fixed it, at least in my own case. I was using ZFS as underlying storage for NFS, which had default sync option. So in that case storage being under load would cause containers to get killed. My fix was disable syncronous writes, and so far it's running 2 weeks without a single...

I am running proxmox in a cluster with HA enabled, from time to time(2-5 day intervals) every lxc container gets killed for no apparent reason. Containers seem to get restarted without any logs, I am only seeing restarts from uptimes. When looking at dmesg output I've found that some containers...

Didn't knew bugzilla existed, already filling report, thanks.

You can try using lxc-start -n #VMID --logfile lxc.log and then post contents of the lxc.log

vzdump doesn't correctly handle sparse files. I have 459G sparse file, that happens because I've implemented SSO based on FreeIPA, and users usually have high user id, and lastlog creates sparse file which gets as big as 459G. ipadmin@proxy:/var/log$ ls -slh lastlog 16K -rw-r--r-- 1 root root...

I have quite a strange problem, since a couple weeks back I can't shutdown proxmox host. It seems to get stuck on stopping iSCSI targets. To be clear I don't use iSCSI. I am using NFS, which might be related. It did work previously, so I'm guessing it might be bug after I did updates...

Thanks, works like a charm!

I am implementing SSO with FreeIPA and Proxmox LXC containers. I've encountered numerous errors while trying to setup kerberos5 keytab. Problem seems to be default hostname resolution in /etc/hosts Specifically this part: # --- BEGIN PVE --- 127.0.1.1 sssd-testing # --- END PVE --- Which...

It seems my problem is the nfs server itself, my zfs filesystem is faulty which does return generic io error even if I try read the type of container disk, by running `file vm-xxx.raw`. Thanks for help!

Already tried that, and checked that the storage is actually mounted, which it is.

I am using lxc containers on nfs storage. It was working well, until yesterday I had to restart my NFS server and proxmox won't boot my existing containers. I can create a new container which does boot up, but it won't start existing containers. I am getting: lxc-start: lxc_start.c: main: 344...

Thank for clear explanation! Is there a way to contribute to documentation?

I am trying automate lxc container creation using proxmox API. So far I have been able to create container using /nodes/{node}/lxc api call. Looking I'm looking at documentation http://pve.proxmox.com/pve2-api-doc/ but cannot seem to find parameter for disk size, am I missing something?

That works! I was following https://pve.proxmox.com/wiki/Linux_Container which clearly shows that password can be passed via parameters. And man doesn't mention it as well. I'm just discovered that there is even easier method using API instead.

I know for sure you can do it using libvirt, but proxmox doesn't seem to have virsh command out of the box. I'm not sure if it wouldn't interfere with proxmox installation. But definately it's doable.

I'm not sure what are you trying to achieve by export/import, I could try it on my own system 4.2 with ZoL, which might give some more insight. It works like a charm by sharing ZFS over network.

Hey guys, I am trying to automate container creation by using pct command. Password option doesn't seem to work. So the command in question is: pct create 113 /var/lib/vz/template/cache/centos-7-default_20160205_amd64.tar.xz -password changeit 400 too many arguments pct create <vmid>...