Search results

Did you guys look at this thread? https://forum.proxmox.com/threads/pve-suddunly-stopped-working-all-cts-unrecheable.26458

Could it be that there has been a change of /proc/sys/kernel/pid_max?

Ok, can it be that your container comes under memory pressure during backup? If you cannot execute commands and the container is not freezing or frozen then maybe there is a lack of memory or disk IO is stuck. Can you use ps listings from the host of the container processes? Can you execute...

I suspect you will have to look in the backup logs. I am guessing you are using a suspend mode backup, and containers are getting stuck in "freezing" state. You can look at the status of containers with lxc-info, and stop the freezing process with lxc-unfreeze. But there may still be hanging...

Do you run the machine with SWAP on ZFS? That will be unstable under low memory even if you turn off every feature on rpool/swap. It just became more pronounced on newer kernels. The arc_max is not a hard limit, because then machines with ZFS would be prone to complete lockups on heavy IO, it is...

There is a known problem with the default ZFS Raid-1 setup. Read about it here: https://forum.proxmox.com/threads/zfs-swap-crashes-system.25208/#post-126215

Is it really the disk IO that is causing a long backup duration? There can be problems with the suspend mode of backup on LXC containers where the suspension itself can hang for a long time. Long wait times on connection are often a sign of DNS problems.

I wonder, are these virtual machines on ZVOLs? They are the same kind of virtual device on ZFS that has shown the tendency to reboot the machine under low memory conditions in Proxmox 4 very easily and under Proxmox 3 a little bit harder when used for SWAP. I find there is a little bit too much...

An important note on running with SWAP disabled. It may lead to unexpected OOM kills. I can't absolutely positively confirm this, but based on a recent experience it seems as if Linux runs with an implicit vm.overcommit_memory=2 setting if you turn SWAP completely off. And because the default...

If I look at servers that were running for a long time, they usually acquire about three quarters of a gigabyte of cruft that gets parked in SWAP and is never used. So, switching of swapping is indeed not completely without disadvantage, because over the course of a couple of days or weeks it...

Whether there is a difference between the id list in the tasks file and that in the cgroup.procs file, and whether by the output of the ps -exf -ostat,comm.pid command you can see if there is any process not in "D" state. All of which is meant to find what process is stopping the cgroup from...

RAID is not a magical bullet. Whether you use raid with LVM, mdadm, dmraid, zfs, fakeraid, hardware raid, or whatever, there will always be instances that it is not going to help. A powersupply delivering a voltage spike internally, a fan that resonates the enclosures, heat buildup, sooner or...

But where are the other processes, the ones that run inside the container? There should at the very least be an init process and some gettys etc.

@RobFantini So, you see a lxc-freeze stuck in the process list? Can you look in the process list of the container if there are processes in a different state? All frozen processes should be listed as state "D". ps -exf -ostat,pid,comm Also: The /sys/fs/cgroup/freezer/lxc/containerid/tasks...

@whyitsderp No, it is not solved yet. It seems to happen mostly on systems with NFS. Does your system use NFS mounts also? Snapshot and suspend both use lxc-freeze. I suppose you could temporarily divert lxc-freeze to a wrapper /usr/bin/lxc-freeze with a timeout, like this: #!/bin/bash...

No, you are not wrong. But, I don't know if the i965 module is included with Wheezy out of the box. You can install it with the aforementioned package, but then I don't know if it will be binary compatible with the Proxmox kernel. If the bios settings work, that is simpler.

At least if you followed the article you have the GPT layout. I think if you take a live cd you can verify if one of the disks at least still has that layout. LVM is already included in the kernel, so I think the problem has more to do with the raid metadata areas being unrecognized. With the...

http://www.system-rescue-cd.org/Download

It is possible to do a wheezy install first with i965 module and then install the Proxmox repositories. Although that would make it more difficult to use a ZFS filesystem if you allocated all disk space already. But if you are interested in new techniques, then I think Proxmox 4.1 would be...

Look at this, section about lxc-start problems. https://www.flockport.com/lxc-configuration-and-troubleshooting/