OpenVZ Forum - RDF feed
type: channel
items: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel errors
items: Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro

Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel errors
type: item
description: Hi there, not sure if this should be a bug report, or if there is a strange configuraiton issue on my server. Running a CentOS 5.9 x86_64 server, recelntly rebooted into the 2.6.18-308.8.2.el5.028stab101.1 kernel last weekend. Upon booting into the new kernel I saw many kernel CPT ERR's while starting the containers: " Jan 20:46:08 vz02 last message repeated 8 times Jan 26 20:46:12 vz02 kernel: CT: 104: started Jan 26 20:46:14 vz02 kernel: CPT ERR: ffff81031e46a000,104 :open_listening_socket: sock_create_kern: -97 Jan 26 20:46:14 vz02 kernel: CPT ERR: ffff81031e46a000,104 :rst_sockets: open_listening_socket: -97 Jan 26 20:46:14 vz02 kernel: CPT ERR: ffff81031e46a000,104 :rst_sockets: -97 Jan 26 20:46:14 vz02 kernel: CT: 104: stopped Jan 26 20:46:15 vz02 kernel: CT: 104: started Jan 26 20:46:17 vz02 kernel: CT: 105: started Jan 26 20:46:19 vz02 kernel: CPT ERR: ffff81032156a000,105 :NLMERR: -22 Jan 26 20:46:19 vz02 last message repeated 8 times Jan 26 20:46:19 vz02 kernel: CPT ERR: ffff81032156a000,105 :open_listening_socket: sock_create_kern: -97 Jan 26 20:46:19 vz02 kernel: CPT ERR: ffff81032156a000,105 :rst_sockets: open_listening_socket: -97 Jan 26 20:46:19 vz02 kernel: CPT ERR: ffff81032156a000,105 :rst_sockets: -97 Jan 26 20:46:19 vz02 kernel: CT: 105: stopped Jan 26 20:46:21 vz02 kernel: CT: 105: started Jan 26 20:46:24 vz02 gconfd (root-8825): GConf server is not in use, shutting down. Jan 26 20:46:24 vz02 gconfd (root-8825): Exiting Jan 26 20:46:24 vz02 kernel: CT: 106: started Jan 26 20:46:26 vz02 kernel: CPT ERR: ffff8103185f3000,106 :NLMERR: -22 Jan 26 20:46:26 vz02 last message repeated 8 times Jan 26 20:46:26 vz02 kernel: CPT ERR: ffff8103185f3000,106 :open_listening_socket: sock_create_kern: -97 Jan 26 20:46:26 vz02 kernel: CPT ERR: ffff8103185f3000,106 :rst_sockets: open_listening_socket: -97 Jan 26 20:46:26 vz02 kernel: CPT ERR: ffff8103185f3000,106 :rst_sockets: -97 Jan 26 20:46:27 vz02 kernel: CT: 106: stopped Jan 26 20:46:28 vz02 kernel: CT: 106: …
creator: PJF5000
date: 2013-01-28T18:01:03-00:00

Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro
type: item
description: Did you ever get a response to this? I'm seeing this today: Mar 16 10:47:34 MyVMName kernel: CPT ERR: ffff8101fe2c5000,252224 :NLMERR: -17 [root@MyVMName1 ~]# uname -a Linux MyVMName.someplace.com 2.6.18-371.3.1.el5.028stab110.1 #1 SMP Fri Dec 13 15:01:51 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux My biggest complaint with OpenVZ is just the forums don't get a lot of traffic so when you find problems it's like a ghost town. CJ
creator: bithead2
date: 2014-03-16T17:52:03-00:00

Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro
type: item
description: Hi, Good to know I'm not the only person who experiences this. I ended up posting on OpenVZ's bugzilla and did indeed get a reply. I can't seem to find the bug now, it's been closed or removed maybe? It's not resolved for me, I have to restart the containers after a reboot by hand to get them online. Out of curiosity, how many network cards do you have on this server? I have many OpenVZ servers and this one has 3 physical network cards, all the others have 2 network cards and do not experience this issue. Could be totally unrelated...
creator: PJF5000
date: 2014-03-17T16:44:35-00:00