Hi all, Now I'm on 2.6.32-042stab088.4 and got exactly same problem again, but now during load tests (not so hogh load though). Randomly it works or not. When issue occurs I just can't telnet to any port - connection times out.
19.05.2014, 12:46, "Denis Zinevich" <l...@ngc.net.ua>: > 19.05.2014, 00:12, "Kir Kolyshkin" <k...@openvz.org>: >> On 05/18/2014 03:01 AM, Bogdan-Stefan Rotariu wrote: >>>> On May 18, 2014, at 11:30, Denis Zinevich <l...@ngc.net.ua> wrote: >>>> >>>> juts got fresh info which narrows problem: >>>> I was comparing normal and faulty containers, and found that they are >>>> using different kernels (on one server containers were not restarted after >>>> yum upgrade) >>>> so normal one was using 2.6.32-042stab084.26 >>>> and faulty - 2.6.32-042stab085.20 >>>> Then I've restarted normal container (084.26), so now it uses 085.20. >>>> Got same problem on previously normal container - no more connection to >>>> localhost. >>> Not directly related to this problem, I had strange oops and other >>> issues(internal clock not working properly) with 2.6.32-042stab085.20. >> Please always file bugs to https://bugzilla.openvz.org/ for such stuff. >>> I recommend not to use kernel 2.6.32-042stab085.20. >> The latest stable kernel is currently 042stab088.4, released a month ago. >> I suggest everyone to use the latest stable kernel. > > Hello, > yesterday I've updated to 042stab088.4, problem seems to be gone. I think > there is no sense opening bug for 085.20 since new version works fine. > Thanks for your attention. > > -- > Denis _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
