OpenVZ Forum


Home » General » Support » OpenVZ HN became sluggish
Re: OpenVZ HN became sluggish [message #51908 is a reply to message #51818] Sat, 07 March 2015 00:16 Go to previous message
spoke2u
Messages: 12
Registered: September 2013
Junior Member
This may not be any help but I checked my Hardware node syslog and had alot of __ratelimit: callbacks suppressed messages and plenty of eth1: received packet with own address as source address

i had the same problem. But it could be different

Check your syslog

[   38.967702] __ratelimit: 104 callbacks suppressed
[   38.967705] eth1: received packet with own address as source address
[   38.968283] eth1: received packet with own address as source address
[   38.969402] eth1: received packet with own address as source address
[   39.028349] eth1: received packet with own address as source address
[   39.029152] eth1: received packet with own address as source address
[   39.030352] eth1: received packet with own address as source address
[   39.067343] eth1: received packet with own address as source address
[   39.067940] eth1: received packet with own address as source address
[   39.108797] eth1: received packet with own address as source address
[   39.176829] eth1: received packet with own address as source address
[   44.025167] __ratelimit: 50 callbacks suppressed
[   44.025169] eth1: received packet with own address as source address
[   44.284032] eth1: received packet with own address as source address
[   44.524232] eth1: received packet with own address as source address
[   44.705052] eth1: received packet with own address as source address
[   44.803056] eth1: received packet with own address as source address
[   44.983080] eth1: received packet with own address as source address
[   45.097899] eth1: received packet with own address as source address
[   45.232783] eth1: received packet with own address as source address
[   45.760855] eth1: received packet with own address as source address
[   45.864921] eth1: received packet with own address as source address


After researching that it was not in fact changing mac address or routing I found someone posted it was the switch and I swapped out to a spare switch and all my weird lag and time outs where fixed.

anything in the logs?


--
I am unable to see

[Updated on: Sat, 07 March 2015 00:17]

Report message to a moderator

 
Read Message
Read Message
Read Message
Previous Topic: Ploop. Deleted files from container, no free space
Next Topic: Debian 6 container not starting after vzctl/kernel upgrade
Goto Forum:
  


Current Time: Wed Sep 10 21:39:48 GMT 2025

Total time taken to generate the page: 0.08831 seconds