Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Node Issue / VPS shuts of randomly
New on LowEndTalk? Please Register and read our Community Rules.

Node Issue / VPS shuts of randomly

SunnSunn Member
edited March 2014 in Help

Hello LET members,

I have an issue, I am using an Intel E3 V2 for my KVM VPS, but for some reason after making somewhere around 12 vps, vps just shut of randomly.

Issue, on which i believe: The VPS's are loosing connection to the network bridge.

If anyone can fix this, please message me you're skype.

Log:: device kvm134.0 entered promiscuous mode
br0: port 5(kvm134.0) entering forwarding state
kvm134.0: no IPv6 routers present
br0: port 5(kvm134.0) entering forwarding state
br0: port 6(kvm135.0) entering disabled state
device kvm135.0 left promiscuous mode
br0: port 6(kvm135.0) entering disabled state
device kvm135.0 entered promiscuous mode
br0: port 6(kvm135.0) entering forwarding state
kvm135.0: no IPv6 routers present
br0: port 6(kvm135.0) entering forwarding state
ip_tables: (coffee) 2000-2006 Netfilter Core Team
device kvm139.0 entered promiscuous mode
br0: port 11(kvm139.0) entering forwarding state
br0: port 11(kvm139.0) entering disabled state
device kvm139.0 left promiscuous mode
br0: port 11(kvm139.0) entering disabled state
device kvm139.0 entered promiscuous mode
br0: port 11(kvm139.0) entering forwarding state
kvm139.0: no IPv6 routers present
br0: port 11(kvm139.0) entering forwarding state
br0: port 6(kvm135.0) entering disabled state
device kvm135.0 left promiscuous mode
br0: port 6(kvm135.0) entering disabled state
device kvm135.0 entered promiscuous mode
br0: port 6(kvm135.0) entering forwarding state
kvm135.0: no IPv6 routers present
br0: port 6(kvm135.0) entering forwarding state
device kvm141.0 entered promiscuous mode
br0: port 12(kvm141.0) entering forwarding state
kvm141.0: no IPv6 routers present
br0: port 12(kvm141.0) entering forwarding state
br0: port 12(kvm141.0) entering disabled state
device kvm141.0 left promiscuous mode
br0: port 12(kvm141.0) entering disabled state
device kvm141.0 entered promiscuous mode
br0: port 12(kvm141.0) entering forwarding state
kvm141.0: no IPv6 routers present
br0: port 12(kvm141.0) entering forwarding state
device kvm142.0 entered promiscuous mode
br0: port 13(kvm142.0) entering forwarding state
kvm142.0: no IPv6 routers present
br0: port 13(kvm142.0) entering forwarding state
br0: port 13(kvm142.0) entering disabled state
device kvm142.0 left promiscuous mode
br0: port 13(kvm142.0) entering disabled state
device kvm142.0 entered promiscuous mode
br0: port 13(kvm142.0) entering forwarding state
kvm142.0: no IPv6 routers present
br0: port 13(kvm142.0) entering forwarding state
device kvm116.0 entered promiscuous mode
br0: port 14(kvm116.0) entering forwarding state
kvm116.0: no IPv6 routers present
br0: port 14(kvm116.0) entering forwarding state
br0: port 14(kvm116.0) entering disabled state
device kvm116.0 left promiscuous mode
br0: port 14(kvm116.0) entering disabled state
device kvm116.0 entered promiscuous mode
br0: port 14(kvm116.0) entering forwarding state
kvm116.0: no IPv6 routers present
br0: port 14(kvm116.0) entering forwarding state
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 left promiscuous mode
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 entered promiscuous mode
br0: port 4(kvm133.0) entering forwarding state
kvm133.0: no IPv6 routers present
br0: port 4(kvm133.0) entering forwarding state
br0: port 14(kvm116.0) entering disabled state
device kvm116.0 left promiscuous mode
br0: port 14(kvm116.0) entering disabled state
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 left promiscuous mode
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 entered promiscuous mode
br0: port 4(kvm133.0) entering forwarding state
kvm133.0: no IPv6 routers present
br0: port 4(kvm133.0) entering forwarding state
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 left promiscuous mode
br0: port 4(kvm133.0) entering disabled state
device kvm133.0 entered promiscuous mode
br0: port 4(kvm133.0) entering forwarding state
kvm133.0: no IPv6 routers present
br0: port 4(kvm133.0) entering forwarding state
device kvm122.0 entered promiscuous mode
br0: port 14(kvm122.0) entering forwarding state
kvm122.0: no IPv6 routers present
br0: port 14(kvm122.0) entering forwarding state
br0: port 14(kvm122.0) entering disabled state
device kvm122.0 left promiscuous mode
br0: port 14(kvm122.0) entering disabled state
device kvm122.0 entered promiscuous mode
br0: port 14(kvm122.0) entering forwarding state
kvm122.0: no IPv6 routers present
br0: port 14(kvm122.0) entering forwarding state
device kvm129.0 entered promiscuous mode
br0: port 15(kvm129.0) entering forwarding state
kvm129.0: no IPv6 routers present
br0: port 15(kvm129.0) entering forwarding state
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 left promiscuous mode
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 entered promiscuous mode
br0: port 15(kvm129.0) entering forwarding state
kvm129.0: no IPv6 routers present
br0: port 15(kvm129.0) entering forwarding state
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 left promiscuous mode
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 entered promiscuous mode
br0: port 15(kvm129.0) entering forwarding state
kvm129.0: no IPv6 routers present
br0: port 15(kvm129.0) entering forwarding state
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 left promiscuous mode
br0: port 15(kvm129.0) entering disabled state
device kvm129.0 entered promiscuous mode
br0: port 15(kvm129.0) entering forwarding state
kvm129.0: no IPv6 routers present
br0: port 15(kvm129.0) entering forwarding state
device kvm130.0 entered promiscuous mode
br0: port 16(kvm130.0) entering forwarding state
kvm130.0: no IPv6 routers present
br0: port 16(kvm130.0) entering forwarding state
br0: port 16(kvm130.0) entering disabled state
device kvm130.0 left promiscuous mode
br0: port 16(kvm130.0) entering disabled state
device kvm130.0 entered promiscuous mode
br0: port 16(kvm130.0) entering forwarding state
kvm130.0: no IPv6 routers present
br0: port 16(kvm130.0) entering forwarding state
device kvm143.0 entered promiscuous mode
br0: port 17(kvm143.0) entering forwarding state
kvm143.0: no IPv6 routers present
br0: port 17(kvm143.0) entering forwarding state
br0: port 16(kvm130.0) entering disabled state
device kvm130.0 left promiscuous mode
br0: port 16(kvm130.0) entering disabled state
device kvm130.0 entered promiscuous mode
br0: port 16(kvm130.0) entering forwarding state
kvm130.0: no IPv6 routers present
br0: port 16(kvm130.0) entering forwarding state
br0: port 8(kvm137.0) entering disabled state
device kvm137.0 left promiscuous mode
br0: port 8(kvm137.0) entering disabled state
kvm: 13990: cpu0 unhandled rdmsr: 0x345
kvm: 13990: cpu0 unhandled wrmsr: 0x680 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x6c0 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x681 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x6c1 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x682 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x6c2 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x683 data 0
kvm: 13990: cpu0 unhandled wrmsr: 0x6c3 data 0
device kvm137.0 entered promiscuous mode
br0: port 8(kvm137.0) entering forwarding state
kvm137.0: no IPv6 routers present
br0: port 8(kvm137.0) entering forwarding state
br0: port 8(kvm137.0) entering disabled state
device kvm137.0 left promiscuous mode
br0: port 8(kvm137.0) entering disabled state
device kvm137.0 entered promiscuous mode
br0: port 8(kvm137.0) entering forwarding state
kvm137.0: no IPv6 routers present
br0: port 8(kvm137.0) entering forwarding state
br0: port 9(kvm138.0) entering disabled state
device kvm138.0 left promiscuous mode
br0: port 9(kvm138.0) entering disabled state
device kvm138.0 entered promiscuous mode
br0: port 9(kvm138.0) entering forwarding state
kvm138.0: no IPv6 routers present
br0: port 9(kvm138.0) entering forwarding state
br0: port 9(kvm138.0) entering disabled state
device kvm138.0 left promiscuous mode
br0: port 9(kvm138.0) entering disabled state
device kvm138.0 entered promiscuous mode
br0: port 9(kvm138.0) entering forwarding state
kvm138.0: no IPv6 routers present
br0: port 9(kvm138.0) entering forwardi...

Comments

  • FlorisFloris Member
    edited March 2014

    Please use the <>pre and </> pre (put pre inside and before /) tags around those errors, it makes it easier to analyze for us.

  • SunnSunn Member

    @Floris said:
    Please use the <>pre and </> pre (put pre inside and before /) tags around those errors, it makes it easier to analyze for us.

    Done.

  • FlorisFloris Member
    edited March 2014

    Seems to be a problem with your network card, try doing:
    netstat -r

  • SunnSunn Member

    @Floris said:

    Seems to be a problem with your internet hardware, try doing:
    netstat -r


    Destination Gateway Genmask Flags MSS Window irtt Iface
    198.24.164.232 * 255.255.255.248 U 0 0 0 br0
    192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0
    link-local * 255.255.0.0 U 0 0 0 br0
    default 198.24.164.233 0.0.0.0 UG 0 0 0 br0
    >

  • FlorisFloris Member
    edited March 2014

    @Sunn said:
    Floris said:
    >

    I don´t see anything wrong here, but after some googling of random errors out of your logs, I saw a few common errors that multiple people had recently (a Kernel problem),

    I'm not a linux expert, just trying to help here!

  • perennateperennate Member, Host Rep

    Try switching driver to ide disk / e1000 network.

  • AlexanderMAlexanderM Member, Top Host, Host Rep

    Doesn't your company have a SYSAdmin capable of fixing such issues?

  • VirtovoVirtovo Member

    Firstly, the above; however:

    1) Do they shut off or just drop network?

    2) Which drivers are you using for network on the VPS

    3) Any Kernel messages on the host?

  • ATHKATHK Member

    @AlexanderM said:
    Doesn't your company have a SYSAdmin capable of fixing such issues?

    You assume he is a provider because he is using virtulization? I must also be one then! ... ;)

    Thanked by 2perennate raindog308
  • Shoaib_AShoaib_A Member

    @ATHK said:
    You assume he is a provider because he is using virtulization? I must also be one then! ... ;)

    http://lowendtalk.com/discussion/24212/www-kvmvps-us-l-50-off-l-vps-starting-3-50-l-usa#latest

  • AlexanderMAlexanderM Member, Top Host, Host Rep

    @ATHK said:
    You assume he is a provider because he is using virtulization? I must also be one then! > ... ;)

    Nope, his last thread was a KVM offer :P

    Alexander

  • forthcloudforthcloud Member

    @AlexanderM said:

    http://lowendtalk.com/discussion/24212/www-kvmvps-us-l-50-off-l-vps-starting-3-50-l-usa

    Probably the hard drive(s) in his KVM node failed.

  • ATHKATHK Member

    @AlexanderM said:

    Ohhhhhhhhhh must of missed that one :)

  • SunnSunn Member

    @AlexanderM said:
    Doesn't your company have a SYSAdmin capable of fixing such issues?

    yes we do, but we were not able to figure out this issue. Thats the whole point of this thread..

  • SunnSunn Member

    @forthcloud said:
    Probably the hard drive(s) in his KVM node failed.

    No that is not a reason for the connections to drop, Our hard drive did not fail.

  • George_FusionedGeorge_Fusioned Member

    Does cat /var/log/messages* | grep cgroup give any output?

Sign In or Register to comment.