El 23/03/12 18:56, Herbert Poetzl escribió:
> I'm not sure this is what you are actually seeing,
> probably a good way to verify it would be to remove
> the lock limit on the guest and see what lock counts
> you'll reach during normal operation (and if the
> problem goes away:)
After restart container all works fine,...
But in this case, for test and other things, I have another VPS (openvz)
with half on memory of the problematic VPS.
After install and test software in various servers and workstations,...,
I have installed de same software (centOS 6), with the same
configuration, and same apps in openvz VPS, different kernel:
Linux hostname 2.6.18-194.8.1.el5.028stab070.5 #1 SMP Fri Sep 17 19:10:36 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux
works without any problem.
For this reason, I think, the problem is in vserver platform(1), "strange limits"(2) of container by the hosting company
or red-bad-daemon(3) .
I can do various things:
a) Install linux-vserver in a workstation and do a test,...(1).
b) buy another vps-vserver with the same resources of problematic.(2).
c) ... do nothing ...
d) ... and finally "cry" for my bad luck(3).
Received on Fri Mar 23 22:07:26 2012