Bleh, ok, looks like we installed the new sources but did not reboot
into the new kernel. So, we are still on 2.6.18. Based on this post
http://community.livejournal.com/openvz/31703.html we should probably go
ahead and move to .32.
Our dev server is on 2.6.27 for sure. Of course, it is a completely
different workload and does not have these issues. That could mean
something and it could not.
Brian.
--------
http://brian.moonspot.net/
On 7/6/10 3:05 PM, Carl-Daniel Hailfinger wrote:
On 06.07.2010 20:00, Brian Moon wrote:
You probably already know this but it doesn't hurt to mention,
2.6.27.x is not a "stable" OpenVZ kernel branch.
Yes, we upgraded to that in hopes it would solve our problems. It
seemed to have no affect either way.
Wait a second. uname said 2.6.18, not 2.6.27.
Regards,
Carl-Daniel
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
