OpenVZ Forum: Support » Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel errors

Home » General » Support » Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel errors (After upgrading my CentOS 5.9 server to 2.6.18-308.8.2.el5.028stab101.1 I'm having issues with networking in containers working and kernel CPT ERR's)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro [message #51239 is a reply to message #48963]

Sun, 16 March 2014 17:52

bithead2
Messages: 5
Registered: July 2009

Junior Member

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

Report message to a moderator

[Message index]

		Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel errors By: PJF5000 on Mon, 28 January 2013 18:01
		Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro By: bithead2 on Sun, 16 March 2014 17:52
		Re: Container networking broken after upgrade to 2.6.18-308.8.2.el5.028stab101.1, stange kernel erro By: PJF5000 on Mon, 17 March 2014 16:44

Previous Topic:	Public IP via VETH seen as the bridge interface IP
Next Topic:	Time inside container

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 24 09:13:01 GMT 2025

Total time taken to generate the page: 0.09864 seconds