Search results

I checked and i get this message: Jul 14 18:41:00 route03 systemd[1]: Starting Proxmox VE replication runner... Jul 14 18:41:00 route03 pvesr[2137]: Unable to create new inotify object: Too many open files at /usr/share/perl5/PVE/INotify.pm line 397. Jul 14 18:41:00 route03 systemd[1]...

Hello, i have the problem on my new pve 5 host system that sometimes the message "unable to fork worker - No space left on device" appears. But i have over 100GB left on my storage. Sometimes i cannot login via ssh and within the lxc containers this message also appears. I have about 50 lxc...

Hello, i am currently using the latest version of Proxmox VE (version 5.4) and i have the problem that i configure for example 1GB of swap for a lxc container, but inside of this container the sum of assigned ram and the configured swap is displayed as swap amount. So when i configure e.g. 2GB...

Is it possible to make the limiting with the number of cores? Is there a way to only see a certain number of cores?

Hello, is there a way - like in Proxmox 3 with OpenVZ - to limit the number of cores of a LXC container in Proxmox 4? Thanks for answers

I killed the process with the PID 651001 and tested it again, but the process started itself again: INFO: Can not suspend container: Resource temporarily unavailable INFO: Error: task 651052,651052(ld-linux-x86-64) is traced. Checkpointing is impossible. INFO: Error: suspend is impossible...

Ok, but why are coming these messages? INFO: Error: task 651001,651001(ld-linux-x86-64) is traced. Checkpointing is impossible. INFO: Error: suspend is impossible now. INFO: Error: task 651001,651001(ld-linux-x86-64) is traced. Checkpointing is impossible. INFO: Error: suspend is impossible...

There is no difference between these 2 containers. Only the resource configuration (diffent ram, cpu-cores, etc.) and ip address

This message comes for every vm when i take a backup. It says, that it uses suspend mode instead. And this mode works perfectly for other containers, but only for this not. Here is the log for a container on which this message also comes but the snapshot works perfectly...

Hello, i want to take automatic backups of all vm's. Everything is working fine, but on only one of my vm's there is an error when taking a backup. In the email from the automatic backup there is standing this: "command 'vzctl --skiplock chkpnt 155 --suspend' failed: exit code 16" When i...

Thanks! And how can i see which container is causing the most traffic (e.g. in a given time)?

Hello, is it possible to see how much rx and tx a container currently is using? Thanks for helping :)