FQuest Alert: MYSQL02

[Terra]

Due to some malformed queries to the MYSQL02 server, I have had to forcibly kill off the MySQL engine...

Right now, I am running 'isamchk' on all databases to ensure integrity...

I will return MYSQL02 server back to full operation as quickly as possible...

The site owner that caused the problem will have their access terminated to avoid any further difficulties...

--
Terra
sysAdmin
FutureQuest

[Terra]

Service has been restored...

No errors were found in any of the ISAM tables...

--
Terra
sysAdmin
FutureQuest

[Hitek333]

Hmmm... "access terminated" - that sounds rather drastic!

Presumably (???) what happened was accidental rather than malicious. Do you take this into account when deciding what action to take? Was that a "temporary withdrawal of DB access", or a "permanent withdrawal of all access to everything"?!

... A few days ago I visited a computer-illiterate friend to setup a new computer for her children. It was raining *heavily* at the time, and I hurriedly parked in a space which another car had just left. I didn't even consider that it might not be legal.

I came back later to find that it I had a parking ticket - it was a space for disabled people! Alas, I'd inadvertently committed a heinous crime... made substantially worse by a dirty look and a "serves you right" from a passer by!!!

So, I was doing something good for someone, but find I'm irrevocably guilty of a crime - by deed if not by intent :-(

Not that this has anything to do with my question of course!

[Terra]

Yes, the question of malicious intent was taken into account...

However, the resources must be shared by all and when one account can take down the resources for many others - then yes, we must reserve the right to terminate access to that resource...

When something goes wrong, then we are bombarded by complaints - both publicly and privately...[nbsp][nbsp]They want us to ensure that this rogue user does not debilitate their web sites functionality as it was not *their* problem that caused the issue...[nbsp][nbsp]They pay for a service, and they expect us to fulfill their sites needs - they will expect nothing less and will vocalize in various ways as such...

We do what we can to ensure the integrity of all functionality offered, for everyone...[nbsp][nbsp]Many times, developers will throw queries at a database (for testing or benchmarking purposes) that can render it's appearance to seem non-functional - but in fact this one domain has got a database locked with 50 requests stacked behind it waiting for it to be unlocked...

To turn the tables - your site is listed 'Most Important Resource on the Web', and everyone is heading to your domain...[nbsp][nbsp]Someone at acme.com feels like today is a good day to see how much our MySQL engines can withstand abuse, or how many requests they can process in a second...[nbsp][nbsp]They have just taken down the same resource that you depend on (as well as many others)...

There will be a day the tables will turn...

--
Terra
sysAdmin
FutureQuest

[Hitek333]

Hi Terra,

Thanks for the explanation. I do (did previously) understand everything you've explained. You have no choice - you have to do what you need to to keep the servers running properly and I fully support that.

Alas, I'm not sure my question was clear enough - I'll try again:

In this (and similar cases), and assuming no malicious intent on the part of the site owner, do you:

1. Disable the site (or the part of it causing the problem)?
2. Cancel the users account completely?

By the way, I think that anyone running benchmarks of the sort you described on a shared server is very thoughtless / selfish...

[Terra]

Under the assumption of no malicious intent, then I will most likely:
a) scavenge the errant processes...
or
b) close the domain and item #a above

You are asking for strict policy, and in this avenue, all overload situations are different and handled as such...

From there, a 'TOS Violation' will be issue and is usually pretty well documented with actual process lists, memory consumption, etc...[nbsp][nbsp]Just depends on what I can snag, and ensuring that I don't aggravate the situation further...

If there is no response to this 'TOS Violation' email, and item #a was followed, then the account will be completely deactivated...

The response contents would contain your acknowledgment of the problem, and your plans on fixing the problem...[nbsp][nbsp]I may also ask for detailed information on what you are trying to accomplish or the programs purpose...[nbsp][nbsp]There is no guarantee that I will allow the program to run on our servers again...

Overall, for those that know me and have been nailed with a TOS Violation, that I am extremely fair and handle each incident with an open mind...

To cut the chase, if your domain overloads the server (or possibly takes it down), then I will be in contact with you...[nbsp][nbsp]Due to the dynamics of the situation, everything is fair game as I try to pin down the problem and ensure it does not occur once again...

In conclusion, if you respect our servers and practice safe computing then you have nothing to worry about...[nbsp][nbsp]If you plan on doing heavy developing, then please test your programs on your development machine at home/office before loading them into full blown production FutureQuest server(s)...

Fair enough?

--
Terra
--In my tour of duty, I've seen a lot - I'm not shocked by disregard anymore--
FutureQuest

[Hitek333]

Yes, very fair, and thank you for clarifying this for me. I'm happy with what you say.

All I really wanted to know was whether an inadvertant misdemeanor would result in an immediate and irrevocable account cancellation (which could be very unfair), or a considered response, not excluding the above, but based on the particular circumstances (which would be entirely fair).

My impression of FutureQuest is that it would most likely be the latter, but from the original posting, it did sound rather like the former.

Er, just one thing I want to make *very* clear: I get the impression from what you've written that you might think that I'm worried that I'll do something that will bring your servers down myself...!

I'd like to emphasise that that's absolutely not the case. I'm *not* asking because I think it might happen to me (any more than any of your other responsible users). I just like to know these things. In effect, you've now told me that FutureQuest will try to be fair and reasonable, even in dire circumstances - that's very important to me.

Thank you once again for your explanation :-)