Search results

@porli, if you look at the mentioned thread about the swap issue, you will find a command listing to get to a configuration that at least in an emulated server makes it more stable.

Hmm.. Even 1 second of loss of synchronous database writes can cause a lot of work trying to recover your database if you don't have recent backups, so I wouldn't underestimate that particular risk. When the synchronous write returns, the database program has every right to assume the data is...

I think if you are using raw or qcow2 files, it is to be expected that ZFS will not be very fast, especially at first start, when, for example mysql would be creating a log file. On the upside you can take snapshots at any time, but with qcow2 this is redundant, so you should really be using raw...

If you take care to not have overlapping container id's and networks in them, then you could probably keep a copy of your config files under /etc/pve and change paths for the roots. This can also be informative I think: https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_%28pmxcfs%29

Hello @martinmp, I just did some quick testing. You can make a tap device in the following way: Set this in your Proxmox LXC config file /etc/pve/lxc/<nnn>.conf (Don't do this directly in /var/lib/lxc/<nnn>/config because it will be overwritten on next start of the container.)...

Ok, the problem is probably with the virtio causing segmentation offload problems in the interface between host and guest, eventually shutting down all network communication with the guest. The newer kernel in the guest will try to use such functions. I guess if you can access the qm tool from...

Little caution, this is not the preferred way to do this, it can you give you trouble later if Proxmox would use modified versions or there is a bug update. The preferred way is to lookup the correct package and install that. For example: apt-cache search perl crypt::openssl::rsa

Could you do a: dpkg -l | grep perl And show the output?

With network device I meant, the device you selected in the KVM configuration: virtio, e1000, vmware, realtek With Kernel 3.X/2.6(l26) you mean 3.x in the guest and 2.6.26 on the host (PVE 3.4?).

Hello @steve87 It looks like your RPC environment is not running, so the webapplication generates a task, but it cannot be executed. At a guess I would say the necessary thing to do is: systemctl daemon-reload systemctl restart rpcbind systemctl restart pvestatd Then check netstat -plnt to...

@Darkie What network device are you using with these KVM machines? And what kernel and system version are the guests running?

@hvisage The zfs list shows that /surf-p4/images doesn't have a mountpoint yet. The solution should be simply to give it one: zfs set mountpoint=/surf-p4/images surf-p4/images

Hello, Maybe, it is informative to see the modification time and contents of the file: /var/lib/lxc/201/config The error itself seems to imply cgmanager, but could also mean incomplete configuration or binary components. This last explanation has already been ruled out. It would do no harm on...

Also I have been putting a Proxmox with systemd jessie and centos containers with nginx and php-fpm under pressure, but haven't yet found a reproduce of lxcfs problems. I am wondering about something though, if a system has this problem what is the output of this on the host: df /run

For info about the cpu-limit, cpu-unit settings look at this thread. https://forum.proxmox.com/threads/q-lxc-configuration-wizard-what-is-cpu-limit-cpu-unit.22661

Hello M, What happened? Sometimes syslogging can be affected, in return leading to a block on many programs that are refused to output log lines, like SSH does on logging in. If you have physical access you can use the sysrq key to safely sync and shutdown your machine. See...

You're welcome, The apt tool keeps extensive history in /var/log/apt/ files. More lowlevel logging is in /var/log/dpkg.log.

@vadavo, Can you try to do a apt-get update apt-get upgrade It seems this cgm error is connected to having components of the LXC system in different incompatible versions.

Hello Zamana, The pveproxy script is included in package pve-manager First install the repositories https://pve.proxmox.com/wiki/Package_repositories Then you can do: apt-get install pve-manager If that tells you it is already installed, then you can do: apt-get install --reinstall...

Great. I overlooked some possibilities for the boot failing. It may have been that the previous system remembered the previous correct boot inside grubenv but wouldn't use this on the new KVM through a difference of disk controller between the two KVMs leading it to use the default newest...