Search results

This is great news for all users. But why aren't much users affected? I counted only 2 in this forum.

Hi @windinternet well, disabling NTP did unfortunately not solve the problem: All containers had a maximum ram usage of 70%. Altogether I assigned the following memory-values to my containers: 102: 24G 103: 40G 104: 16G 105: 24G 200: 1G = 105GB Additionally there is a KVM-machine using...

I do not know exactly what you mean with "what does your memory overcommit look like?" - I assume you mean ?

There is one point I mentioned: NTP was installed and activated by a software which was installed on all LXC-containers. This is - of course - not necessary on LXC, but maybe this could be a point? I turned off NTP on clients yesterday evening and the error did not occur again for almost 12...

Hello winternet, thanks again for your reply, here they are :-)

Thank you for your answer :-) No, the containers are using max 40% memory and they have 120GB vSwap. Even CPU-usage is low.

Hello, some minutes ago the error appeared again. This is my mount: Syslog shows the following

I just mentioned that the error happened just now: There was nothing with FPM in this moment.

Update: Now the VM is cloned (I do not know why) but it does not boot properly: During boot up I'm getting "unexpected incensestency" (http://d.pr/1bVdt )

Ah, I forgot to tell you the details: This is the resource usage on this machine: info version does not show anything because the VM is not running.

Hello, this is the output:

Hello, I would like to create a clone of a KVM machine - yesterday I was able to create a clone of the same machine within some minutes. Now it takes hours and is still stuck an "0%": I wonder why this is the case. The task is running (i restarted it some minutes ago) - http://d.pr/tJn4 Any...

Is it important where it is added?

Okay i did not express it correctly: I could increase the values for the most CPU-intensive container, Right? CPU-limit means the percentage of all CPU-time, correct?

Hello windinternet, At the moment the CPU-limit is set to 12 and there are 2048 CPU-units for all 5 containers. I thought it should be enough - maybe I should increase it to 4000 units?

Hello and thanks a lot for your reply :) Well, all containers are running, but all are having the same problem at the same time with top/htop, reloading/starting services using systemd. The output of systemctl --version on one of the containers (having this error now) Output of...

Sorry, I forgot to give you an update. I upgraded yesterday night to the following packages: The server already rebooted but the error occurred again.

Hello windinternet, unfortunately I'm still not able to reproduce this error. I'm also unable to fix it without rebooting the whole machine. I just do not have any idea how to fix that.. :-(

Its possible that the error appears on these events. I never saw it "live" - I always mentioned it later when I tried to restart services like dovecot or php5-fpm. So you would suggest to stop all containers, restart lxcfs (service lxcfs restart) and start containers again? What makes me crazy...

Hi windinternet, thanks a lot for your reply. I installed the new kernel - now I'm waiting for reboot and double-check if the problem persists. This is the output of journalctl -u lxcfs Edit: Character-limitation - full log is pasted here: http://d.pr/18cna