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

› › BuyVM LV is down?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

BuyVM LV is down?

adanforestadanforest Member
in General

seems like i can't open ssh even i can't able to ping.

Comments

  • ManishPantManishPant Member, Host Rep

    Mine works fine

    Thanked by 1adanforest
  • BilohBucksBilohBucks Member
    edited March 14

    Seems like DDoS Protected IP's are affected. (Mine is down as well)
    Most likely related to this:
    https://status.path.net/incidents/7v85g51fd4pb

    Thanked by 1adanforest
  • WeblogicsWeblogics Member

    @BilohBucks said:
    Seems like DDoS Protected IP's are affected. (Mine is down as well)
    Most likely related to this:
    https://status.path.net/incidents/7v85g51fd4pb

    The path page says: This incident affects: Europe (Amsterdam, Netherlands).
    OP mentioned LV which to me is Las Vegas. My VPS in LV is up.
    Am I missing something here?

  • matey0matey0 Member

    @BilohBucks said:
    Seems like DDoS Protected IP's are affected. (Mine is down as well)
    Most likely related to this:
    https://status.path.net/incidents/7v85g51fd4pb

    Common Path L

  • BilohBucksBilohBucks Member

    @Weblogics said:

    @BilohBucks said:
    Seems like DDoS Protected IP's are affected. (Mine is down as well)
    Most likely related to this:
    https://status.path.net/incidents/7v85g51fd4pb

    The path page says: This incident affects: Europe (Amsterdam, Netherlands).
    OP mentioned LV which to me is Las Vegas. My VPS in LV is up.
    Am I missing something here?

    Oh, my bad. Network in LU was down for me too

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @BilohBucks said:
    Oh, my bad. Network in LU was down for me too

    Path had an outage in EU somewhere that caused the DDOS IP's in LUX to break:

    https://status.path.net/incidents/7v85g51fd4pb

    Unprotected IP's were fine. I'll have to think of a way to work around this. The symmetrical route makes it annoying to automate anything on the juniper side.

    It's resolved now at least.

    Francisco

    Thanked by 2BilohBucks adanforest
  • packetnextpacketnext Member

    as for the thread "Path.net Drama 2.0 - 5 or more Exchanges suspend them for unpaid bills."

    Might be a good idea to switch to another supplier?

  • SetsuraSetsura Member

    @packetnext said:
    as for the thread "Path.net Drama 2.0 - 5 or more Exchanges suspend them for unpaid bills."

    Might be a good idea to switch to another supplier?

    Not that I don't believe you considering path's rep, but do you have any link to a source? I'm surprised people still do business with them considering everything I've heard about them.

  • packetnextpacketnext Member

    @Setsura said:

    @packetnext said:
    as for the thread "Path.net Drama 2.0 - 5 or more Exchanges suspend them for unpaid bills."

    Might be a good idea to switch to another supplier?

    Not that I don't believe you considering path's rep, but do you have any link to a source? I'm surprised people still do business with them considering everything I've heard about them.

    Go to the thread mentioned, go to for example the De-cix member list for Frankfurt and....... Path is not there anymore.

  • adanforestadanforest Member

    oh my bad it’s LUX not LV.
    sorry for mistake. and server is working fine

  • adanforestadanforest Member

    Luxembourg
    down again.

  • FranciscoFrancisco Top Host, Host Rep, Veteran
    edited March 28

    @adanforest said: Luxembourg
    down again.

    Single node, KVM30, is acting up (buggy NIC firmware<>driver in this kernel).

    I got it doing an emergency update and it'll be back in 5 - 10 minutes.

    Francisco

    Thanked by 1adanforest
  • FranciscoFrancisco Top Host, Host Rep, Veteran

    It basically looks like this in our logging:

    Mar 27 00:03:06 KVM-30 kernel: [69075957.632924] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633024] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633107] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633199] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633294] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5

    Some said it could be related to PCI power savings, but so far just upgrading from 4.19 -> 6.x+ has fixed it.

    Anyway, node just rebooted a couple minutes ago so we should be spinning everyone in a few minutes.

    Francisco

  • BruhGamer12BruhGamer12 Member

    2 minute response time - does @Francisco have some software that scans the forum for any mention of his name company or have any thread mentioning it bookmarked or something :)

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @BruhGamer12 said: 2 minute response time - does @Francisco have some software that scans the forum for any mention of his name company or have any thread mentioning it bookmarked or something

    Nope, reloaded the page and saw the reply.

    Was around 10ish minutes for all the updates to apply.

    Francisco

  • adanforestadanforest Member

    @Francisco said:
    It basically looks like this in our logging:

    Mar 27 00:03:06 KVM-30 kernel: [69075957.632924] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633024] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633107] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633199] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5
Mar 27 00:03:06 KVM-30 kernel: [69075957.633294] mlx4_en: eth2: CQE error - vendor syndrome: 0xf9 syndrome: 0x5

    Some said it could be related to PCI power savings, but so far just upgrading from 4.19 -> 6.x+ has fixed it.

    Anyway, node just rebooted a couple minutes ago so we should be spinning everyone in a few minutes.

    Francisco

    my server not started

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @adanforest said:
    my server not started

    Did another pass for any I missed, let me know or ticket.

    Francisco

  • adanforestadanforest Member

    @Francisco said:

    @adanforest said:
    my server not started

    Did another pass for any I missed, let me know or ticket.

    Francisco

    fixed thanks, but do not do anything without mail, i mean maintain or upgrade.
    i have few traffic on my website if your vps down i got error on google webmaster console. :'(

  • kevindskevinds Member, LIR

    @BruhGamer12 said:
    2 minute response time - does Francisco have some software that scans the forum for any mention of his name company

    The forum software has this built in..

    Edit Profile
    Notification Preferences

  • Deepak_lebDeepak_leb Member

    @adanforest said:

    @Francisco said:

    @adanforest said:
    my server not started

    Did another pass for any I missed, let me know or ticket.

    Francisco

    fixed thanks, but do not do anything without mail, i mean maintain or upgrade.
    i have few traffic on my website if your vps down i got error on google webmaster console. :'(

    Ouch

  • FranciscoFrancisco Top Host, Host Rep, Veteran
    edited March 28

    @adanforest said: but do not do anything without mail, i mean maintain or upgrade.

    When this happens it's unplanned. We have nodes that have 1000+ day uptimes and it hasn't acted up. When it acts up it's sudden and there's nothing we can do to calm it down. Customers just suffer until it's fixed.

    Thing is, for end users you'll feel connections dropping, downloads not working, etc, so the node might as well be offline anyway.

    Doing an announcement would be nice, but 'hey youre going to have to suffer for 24 hours instead of just ripping the bandaid off' doesn't always work.

    Sorry, it's a lose/lose on our end other than 'well at least that node wont do it again' once complete.

    Francisco

    Thanked by 1adanforest
Sign In or Register to comment.