Howdy, Stranger!

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

Sign In with OpenID
Advertise on LowEndTalk.com

In this Discussion

ServerBear script causing heavy IO and got my VPS suspended

ServerBear script causing heavy IO and got my VPS suspended

ChanChan Member
edited September 2012 in General

Hello everyone,

I tried to run ServerBear on my Edis VRS earlier today, it seems to have started fine but it got stuck at the "Running FIO benchmark..." bit

Checking server stats... Running dd I/O benchmark... Running IOPing I/O benchmark... Running FIO benchmark...

I thought it was going to take awhile so I went away for a cup of tea, but when I got back I got this in my mail

This is a notification that your service has now been suspended. The details of this suspension are below: Product/Service: VRS ADVANCED Domain: HK: XXX.XXX.XXX.XXX Amount: EUR 13.49 Due Date: 25/09/2012 Suspension Reason: ToS Violation heavy I/O Please contact us as soon as possible to get your service reactivated. Nonpayment will result in deletion of the service and all associated data. Best regards Yours, EDIS team

It sounds to me that the IO test is repeating itself/not stopping, hence causing the heavy IO which got my VRS suspended. Does anyone have a clue what did I do wrong or is it a bug from the ServerBear script? Here's the log if anyone's interested: http://pastebin.com/QeqitPjn

@serverbear: if you need any info on my VPS feel free to ask me after my VPS is reactivated :D @William: please reactivated my VRS (just sent a ticket)....

Thanks guys

Comments

  • this is interesting.. first issue with the script

  • TazTaz Disabled

    @Chan said: Hello everyone,

    I tried to run ServerBear on my Edis VRS earlier today, it seems to have started fine but it got stuck at the "Running FIO benchmark..." bit

    Checking server stats... Running dd I/O benchmark... Running IOPing I/O benchmark... Running FIO benchmark...

    I thought it was going to take awhile so I went away for a cup of tea, but when I got back I got this in my mail

    This is a notification that your service has now been suspended. The details of this suspension are below: Product/Service: VRS ADVANCED Domain: HK: XXX.XXX.XXX.XXX Amount: EUR 13.49 Due Date: 25/09/2012 Suspension Reason: ToS Violation heavy I/O Please contact us as soon as possible to get your service reactivated. Nonpayment will result in deletion of the service and all associated data. Best regards Yours, EDIS team

    It sounds to me that the IO test is repeating itself/not stopping, hence causing the heavy IO which got my VRS suspended. Does anyone have a clue what did I do wrong or is it a bug from the ServerBear script? Here's the log if anyone's interested: http://pastebin.com/QeqitPjn

    @serverbear: if you need any info on my VPS feel free to ask me after my VPS is reactivated :D @William: please reactivated my VRS (just sent a ticket)....

    Thanks guys

    Duh. You are doing load testing after all. What did you expect? If it is a loaded server and 3 or more people starts to run server bear at the same time, I am willing to shoot my self.

    Time is good and also bad. Life is short and that is sad. Dont worry be happy thats my style. No matter what happens i won't lose my smile!

  • @Randy said: this is interesting.. first issue with the script

    No, it's not Randy.

    RamNode: High Performance SSD and SSD-Cached VPS
    New York - Atlanta - Seattle - Netherlands - IPv6 - DDoS Protection - AS3842
    Thanked by 2Taz William
  • Edis is my hero.

    I am no longer affiliated with IPXcore.
  • @Taz_NinjaHawk said: Duh. You are doing load testing after all. What did you expect? If it is a loaded server and 3 or more people starts to run server bear at the same time, I am willing to shoot my self.

    And how am I supposed to know whether the server is full or not? I'm pretty sure most people just run serverbear on their servers at random times (after all it wouldn't be fair if you can only run it when your host allows you to...), and how is it that I'm the only one who got my VPS suspended? As I checked on the serverbear's site, 3 other people have ran the script on other Edis's and they got away with it

    Just my 2 cents

  • @Randy Stop posting crap in threads. You're like the awkward third wheel who hovers in the background.

  • TazTaz Disabled

    @Chan said: And how am I supposed to know whether the server is full or not? I'm pretty sure most people just run serverbear on their servers at random times (after all it wouldn't be fair if you can only run it when your host allows you to...), and how is it that I'm the only one who got my VPS suspended? As I checked on the serverbear's site, 3 other people have ran the script on other Edis's and they got away with it

    Well, providers are here to provide vps for usage not for benchmarking after all ;)

    Time is good and also bad. Life is short and that is sad. Dont worry be happy thats my style. No matter what happens i won't lose my smile!

    Thanked by 1marrco
  • TazTaz Disabled

    @AsadHaider How good are you with greasemonkey?

    Time is good and also bad. Life is short and that is sad. Dont worry be happy thats my style. No matter what happens i won't lose my smile!

  • @Taz_NinjaHawk When I get home, I'm going to work on it. I'll post it in a new thread.

  • @Taz_NinjaHawk said: Well, providers are here to provide vps for usage not for benchmarking after all ;)

    Indeed, I ended up adding sb.sh to my abusers kill script.

    I am no longer affiliated with IPXcore.
    Thanked by 1marrco
  • With busy VPS nodes there really is no perfect way to benchmark effectively and accurately without having an effect on others on the node. I probably wouldn't recommend running that script on a node too close to capacity. Unfortunately, the results won't be exactly what the node will look like at 100% capacity, unless the capacity is low (in which case price is usually high). That's just the unfortunate reality.

  • RandyRandy Disabled
    edited September 2012

    Sorry. i meant it could be an error with the script(there are chances of an eror too)

    or the node could be busy

    just my point of view.

  • @Randy said: just my point of view.

    That is the problem, your point of view is in every single thread. Take a chill, go outside, visit friends, find a girl, just stop posting everything your brain says to. Count to 100 before hitting submit, then ask yourself after pause, are you adding anything of value?

    Hostigation High Resource Hosting - SolusVM OpenVZ/KVM VPS
  • Wow gang up on @Randy day. Did everybody wake up and have somebody piss in there wheaties?

    back to topic - not sure of Edis setup but if they are on a load balanced setup and it jumped you to another node like ours would do maybe it caused the script to loop.

    Thanked by 1Randy
  • @Damian said: Edis is my hero.

    I am also thinking this will make ppl think twice, at least I do. M

    top - 22:32:38 up 906 days, 2:58, 1 user, load average: 3.94, 5.13, 8.38

  • AsadHaiderAsadHaider Member
    edited September 2012

    I had multi grain cheerios this morning.

    Thanked by 1ElliotJ
  • ChanChan Member
    edited September 2012

    @Maounique said: I am also thinking this will make ppl think twice, at least I do.

    Well I'm not trying to say Edis is bad in anyway, this is like the 4th VPS I've got from them and it has been alright till now. (even though that my reactivate ticket isn't replied yet but i guess waiting for a few hour wouldn't hurt...., I probably was banned automatically by a bot or something)

    And also most importantly, this is probably not their fault. The serverbear script might have bugged and triggered bots on Edis's side to suspend me (which will in turn be my fault as the ServerBear is provided as-is)

  • @Chan What's the purpose of running ServerBear? What're you trying to get out of? Here is the benchmark, blah blah, so what?

    Thanked by 1marrco
  • It is good to know the benchmarks, however overhyping about the benchmarks could result in some hosts starting to optimize especially for benchmarks (i.e. like turning on SSD writeback caching) which could result to less reliability and potential data loss.

  • Serverbear already did benchmark, just reference it.

  • ChanChan Member
    edited September 2012

    @LAKid said: @Chan What's the purpose of running ServerBear? What're you trying to get out of? Here is the benchmark, blah blah, so what?

    To see what I'm paying for? Why don't you give me other ways of comparing VPSes? You may say that they aren't accurate but with those results I can easily tell which VPS is the best for CPU intensive stuff, which one is best for VPNing.

    @LAKid said: Serverbear already did benchmark, just reference it.

    Nope they didn't (http://serverbear.com/9801/edis), if they've I probably wouldn't have bothered to do it myself

  • @Chan said: which VPS is the best for CPU intensive stuff, which one is best for VPNing.

    I can tell you - no VPS is good for encoding movies 24/7 and VRS is not good at all for VPNing :)

    Thanked by 1marrco
  • @rds100 said: I can tell you - no VPS is good for encoding movies 24/7 and VRS is not good at all for VPNing :)

    Just making a point lol, this VRS VPS in particular doesn't even have TUN/TAP (I have KVMs for that)

  • Exactly, VRS doesn't have the features needed for VPNing.

  • @rds100 said: Exactly, VRS doesn't have the features needed for VPNing.

    I never said I was going to VPN with the VRS :), well I was just trying to say that benchmarks helps users to find out what the VPS is good and not good at. Sorry if that caused confusion

    Thanked by 1rds100
  • haha I bet 90% users get LEB just to benchmark every month :P

  • If you have a good node management, there is no problem with benchmarks. You can limit io, cpu and ram with xen or kvm. In our XEN and KVM vps, we don´t see any benchmark, only a high load or something. If a hoster offers guarantee ressources, they must be allowed benchmarks. If not, no guarantee ressources..

    fileMEDIA - Dedify: German Private Cloud @ https://www.dedify.com - CloudStack+XenServer+SSD

  • TazTaz Disabled

    @fileMEDIA said: If you have a good node management, there is no problem with benchmarks. You can limit io, cpu and ram with xen or kvm. In our XEN and KVM vps, we don´t see any benchmark, only a high load or something. If a hoster offers guarantee ressources, they must be allowed benchmarks. If not, no guarantee ressources..

    What are you smoking boi?

    Time is good and also bad. Life is short and that is sad. Dont worry be happy thats my style. No matter what happens i won't lose my smile!

  • Nothing...Good management..no problems with benchmarks..

    fileMEDIA - Dedify: German Private Cloud @ https://www.dedify.com - CloudStack+XenServer+SSD

  • TazTaz Disabled

    @fileMEDIA said: Nothing...Good management..no problems with benchmarks..

    10KVM on a same buyvm server running serverbear at the exact same time, Aldryic will bann the hell out of me.

    Time is good and also bad. Life is short and that is sad. Dont worry be happy thats my style. No matter what happens i won't lose my smile!

  • JarJar Member
    edited September 2012

    @fileMEDIA So do the benchmarks return low or does no one else on the node get to burst resources during that time? You can manage but you can't be running hardcore IO benchmarks and act like your other clients can do disk intensive operations at the same time without either feeling a bit of a loss in average performance.

  • ChanChan Member
    edited September 2012

    Quick Update: Edis just re-enabled my VRS and everything is fine again. I don't think that it's their fault after all as my VRS did do heavy IO for like 30 minutes.....

    @fileMEDIA: You're right in a way but Edis is selling a "fair-share" of resources for the VRSes, instead of "guaranteed" which they do with the KVMs. Which in a way is better for the customers as they can technically use all that's available from the server host as long as no one else is using it, but not so good when there are abusers

  • acarrascopeacarrascope Banned
    edited September 2012

    Is reasonable think in a review to @serverbear script - "several hours" - must be annoying for nodes admins. It is a great value to all us but sure I/O test are exhausting

    pd : Madrid 0 - 1 City -> draw 1 - 1

    Im out

  • @24khost said: Did everybody wake up and have somebody piss in there wheaties?

    Yes, @Randy

    When you find that perfect VPS, KEEP IT.

  • @jarland Limit the process with ionice, dm-ioband or something other..No problem here..All communication to the io layer are taking by a process (eg. xen: blkback.xxx.xvda), you can limit it with all working tools.

    Onapp included this function, too!

    I think it´s not a good business if you suspend a vps when it using some io ressources in hour or so.

    fileMEDIA - Dedify: German Private Cloud @ https://www.dedify.com - CloudStack+XenServer+SSD

  • Sorry to hear you got suspended, generally the script takes ~40-50 minute to run. If you've got more CPU cores it takes longer, from our testing if shouldn't place any unnecessary stress on other users on the node unless:

    The node performs poorly - the tests will run longer (poor IO speed/download speed will dramatically increase the length of those tests) Multiple people are running it on the same node at the same time (I've only really seen this happen with BuyVM/Ramnode).

    FIO is very disk intensive (and occasionally it hangs on some configurations), we're working on a way to exclude certain tests from the run if a certain thing gives you any trouble.

    If any hosts want to test how the script might impact others on the node shoot me a PM so we have some real world data rather than making assumptions.

    ServerBear - Easy UnixBench/dd/IOPS/FIO (NEW) & Network Benchmarks | Example Report | Compare Low End Boxes
    Gleam - Run kick-ass viral competitions & rewards to grow your userbase. Free until Sept.
    Thanked by 1acarrascope
  • @serverbear said: Multiple people are running it on the same node at the same time (I've only really seen this happen with BuyVM/Ramnode).

    Yeahhhh...

    RamNode: High Performance SSD and SSD-Cached VPS
    New York - Atlanta - Seattle - Netherlands - IPv6 - DDoS Protection - AS3842
  • NanoG6NanoG6 Member
    edited September 2012

    To be honest I don't really understand what serverbear FIO benchmark is, yet it is the longest part. @serverbear can you add an option to skip that one?

    --edit

    @serverbear said: we're working on a way to exclude certain tests from the run if a certain thing gives you any trouble.

  • serverbearserverbear Member
    edited September 2012

    @NanoG6 said: To be honest I don't really understand what serverbear FIO benchmark is, yet it is the longest part. @serverbear can you add an option to skip that one?

    At the moment it sets the number of processes based on the cores your CPU has, we're doing a bit of testing to determine whether we can get the same sort of results/comparison by just running 1 process (which will speed it up / reduce load).

    For example 1 core / process takes ~7mins, 4 cores / processes takes ~ 30mins on a Linode.

    ServerBear - Easy UnixBench/dd/IOPS/FIO (NEW) & Network Benchmarks | Example Report | Compare Low End Boxes
    Gleam - Run kick-ass viral competitions & rewards to grow your userbase. Free until Sept.
  • Well, for me, I would want to apologize for every host that ever benchmarked by me and causing high io or trouble :)

    My blog | Server Uptime | I'm not working for any providers in here, all my comments just my own opinion.image
  • Okay, we should have fixed any issues with the FIO test taking longer than normal. Not sure if you want to risk trying again Chan :)

    ServerBear - Easy UnixBench/dd/IOPS/FIO (NEW) & Network Benchmarks | Example Report | Compare Low End Boxes
    Gleam - Run kick-ass viral competitions & rewards to grow your userbase. Free until Sept.
  • and that, ladies and gentleman is the reason why i don't run serverbear benchmark on my vps

    @serverbear said: For example 1 core / process takes ~7mins, 4 cores / processes takes ~ 30mins on a Linode.

    7 mins that's more like it. I can't wait for this. =-)

    vpsdash.com - Tips and tricks in life, information and technology news to get things done

  • The problem is that Serverbear on Linux-VServer uses 100% on 24 (all available) cores and all available IO across the full RAID array - not a good idea to run on it.

    Opinions/Posts are to be assumed my own/personal and not company related unless obvious
    Currently unemployed | Available for consulting | http://as198412.net | https://william.si

    Thanked by 1Oliver
  • KuJoeKuJoe Member
    edited September 2012

    @fileMEDIA said: I think it´s not a good business if you suspend a vps when it using some io ressources in hour or so.

    So instead of all clients following the TOS, providers should make changes to few abusive VPSs to make them in compliance while they impact other users who are able to follow the rules? That doesn't seem like good business practices to me.

    -Joe @ SecureDragon - LEB's Powered by Wyvern in FL, CO, CA, IL, NJ, GA, TX, and AZ
    Test our network here: Drgn.biz
  • @William said: The problem is that Serverbear on Linux-VServer uses 100% on 24 (all available) cores and all available IO across the full RAID array - not a good idea to run on it.

    It won't do this now for the FIO tests, we've limited it to 1 process instead of 1 per core.

    ServerBear - Easy UnixBench/dd/IOPS/FIO (NEW) & Network Benchmarks | Example Report | Compare Low End Boxes
    Gleam - Run kick-ass viral competitions & rewards to grow your userbase. Free until Sept.
  • Hehe one of my edis VPS is down atm, maybe it is on your node ;)

    Quis custodiet ipsos custodes?
    https://raymii.org - https://cipherli.st
  • @rds100 said: Exactly, VRS doesn't have the features needed for VPNing.

    Actually, it has ssh... M

    top - 22:32:38 up 906 days, 2:58, 1 user, load average: 3.94, 5.13, 8.38

  • @serverbear said: It won't do this now for the FIO tests, we've limited it to 1 process instead of 1 per core.

    Would that be less accurate in any way? or do the old benchmark and the new single core limited one get the same results?

  • @AsadHaider said: Would that be less accurate in any way? or do the old benchmark and the new single core limited one get the same results?

    With my testing today 1 process vs multiple processes doesn't make much difference to the end avg result.

    ServerBear - Easy UnixBench/dd/IOPS/FIO (NEW) & Network Benchmarks | Example Report | Compare Low End Boxes
    Gleam - Run kick-ass viral competitions & rewards to grow your userbase. Free until Sept.
Sign In or Register to comment.