Search results

Occasionally I'm having issues when trying to exit CTs that I've used pct enter to enter. I usually use ctrl-d to exit but I've found that typing exit gives the same result. I have cloned one of the CTs to 100 and am using to test this. When I exit the terminal hangs as in the image below...

pve-zsync seems to have got stuck last night pve-zsync list SOURCE NAME STATE LAST SYNC TYPE CON 1000 1000 ok 2018-09-11_22:32:48 lxc ssh 1001 1001 ok...

If I have pve-zsync running every 15 minutes using, for example, --maxsnap 2 and take a snapshot backup that takes 6 hours will the snapshot created by the backup interfere with the removal of pve-zsync snapshots? Do I need to pve-zsync disable in this situation?

My containers are not obeying their allocated swap. For example container 111 has been allocated 128MB swap. arch: amd64 cores: 1 cpulimit: 1 cpuunits: 100 hostname: XXX memory: 2048 net0: name=eth0,bridge=vmbr0,gw=10.0.0.1,hwaddr=36:1F:BC:1B:78:47,ip=10.0.0.111/32,type=veth ostype: ubuntu...

I have a bash script in one of my LXC which involves the opening of a file at a certain line using nano +LINE This had recently stopped working and the file is now opened at the top as if the +LINE wasn't entered. This is true for all users in that LXC and is the same if I do nano +LINE...

Current Proxmox is running ZoL 0.7.7 which I believe has a serious bug. Any ideas when 0.7.8 will be available? Also will the eventual update require a server reboot to apply? Thanks in advance Edit - also will downgrading to 0.7.6 work while we wait?

LXC container with LAMP installed pct start 999 && pct enter 999 Running top I can see that a couple of processes are running eg rsyslogd, upstart* It takes 1-2 minutes for apache etc to start Why is this? Is it editable? Sorry if this has already been covered but I've not found anything...

pveversion -v proxmox-ve: 4.4-86 (running kernel: 4.4.49-1-pve) pve-manager: 4.4-13 (running version: 4.4-13/7ea56165) pve-kernel-4.4.49-1-pve: 4.4.49-86 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+1 libqb0: 1.0.1-1 pve-cluster: 4.0-49 qemu-server: 4.0-110 pve-firmware: 1.1-11...

I've been running Proxmox @ OVH for years with very little problem. I've now hit something that I'm stuck on. Whenever I move a large-ish volume of data across folders on a single Prox node I end up with iowait issues. The cpu will be next to idle but the load will shoot up to ridiculous...

Quick question... I'm running Shorewall on my Proxmox, will the new Proxmox firewall have any effect on this setup ? I presume that both are front ends for iptables but better safe than sorry. Thanks

Does anyone here have any experience of installing / using Compcache with Proxmox ? Trying to squeeze as much out of my machine as possible and since I'm mainly memory bound I'm wondering if this could help.

I see that the OpenNode project is supporting soft RAID. Is there any chance of a port at any time ? Would this even be considered ? Not everyone has the funding for a nice hard RAID set up and running production sans RAID is quite unthinkable. Although I really like Proxmox and prefer Debian...

Just updated from 1.7, now running : pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.27-1pve1 vzdump: 1.2-13...

I have a couple of questions concerning shutdown, stop and vzdump. Firstly, what is the difference between shutdown and stop, command wise ? The reason I ask is because when I do a stop on one of my OpenVZs, running Zimbra on 8.04, it fails to startup again unless I reset it a second time...