Topic: Dreams becoming reality for the D2: GW4 MySQL test

[drb]

Hoi Folks,

It is here...
it is now...
and it is just for You, and YOU, and YOU, and YOU!
Oh, and me too. hehe

Things around here have changed; for the better, no strike that, for the best. For I speak of the Holy Grail of dyna servers, the MySQL supported dynaverse server! Due to the work of many highly trained, devoted, and down right great folks, the GW4 MySQL test will help us to make D2 bells and whistles never witnessed in this quadrant of the galaxy before!

What we need from YOU is get out there on the GW4 Test Server. As I mentioned, this is a special set up, that will let us do much for overall game play, but it will not mean a thing if folks do not use Bonk's really easy to use installer (it will not install over itself, and reverts your game back to the way it was before the install with just a couple of clicks, so if you are set
up with another mod you won't be put out at all) and login.

Take care...to get on that test server, everybody!

Please!

drb

[Bonk]

Get on there folks! I'm logging the works, (except at the ODBC connector - as running a debug ODBC driver could interfere with the MSSQL installation on the server - but I'm logging the kit output, the kit's SQL logging, and SQL's own logging to compare to the kit's).

We need numbers! I feel optimistic, if not sure, that we can nail down the problem(s) this time.

Come try and take on my Thol NCA, I'll blast y'all! 

P.S. the installer is here

[FPF-DieHard]

PS.   if we don't crash it tonight there will be another stress test tommorow at noon 

[Lepton]

Is GW4 running on an SQL server?  Ouch, bad idea.  Stress test?  Great.  Experimenting?  Great.  Major server?  Doubtful.

[Bonk]

Is GW4 running on an SQL server?  Ouch, bad idea.  Stress test?  Great.  Experimenting?  Great.  Major server?  Doubtful.

Stress test.

The problem, you see, is nobody will show up for a stress test. The only way to get a crowd is to try it on a major server. There will be a second stress test tomorrow if not enough show up tonight. If neither stress test crashes then DieHard may decide to run it on SQL.

So, to make your point in the best way possible, please login! 

The main point of this exercise is data collection, I have that server logging its little heart out. (I agree its not too likely to run perfectly, but we really need to find out just what might be causing problems)

[KAT J'inn]

Lets see:


1) I have the flu.

2)  A female friend told me that she wants me to buy her a house.  YES A FRIKKIN HOUSE!!! Like I have that kind money!  Like I would even if I did!!!   GRRRRRRRR  Like I could EVER explain THAT to Shop Rex!!!
 
3)  I have the flu.

4) Shop Rex wants me to help with Thanksgiving Dinner for her whole family.  It's a Chinese family . . . as it's at least 200 people. All of them mad at me.

5) I have the flu

6)  Shop Rex found out the Frikkin Kohl's opens at 6:00 AM on Black Friday and she wants to get in line . .  . get this  . . . early.

7) I have the flu.

8 )  My legal assistant decided that since I was not in the office today that she might as well leave her _(&$(*&(*$)&)$* brain at home and now I have a few angrier that normal clients.   Some of which have been charged with various violent crimes

9)  <COUGH>

10)  I asked one of the secretaries to bring me some OJ.  She said she would.  I then asked if she had a "Nurse Naughty" outfit.  Now she's mad at me too.   I blame the cold medicine I'm taking for my sudden lapse of judgment there.



So  . . .  Let me at that server.  I'll give it stress.

[drb]

Hoi J'inn

Good for you! Nevermind the weather, its always perfect. hehe

And if you log on as Alliance I will have to be really creative to come up with a new way to BLACKMAIL you.

BTW thanks for the retraction about the light beer. A little malpractice suit is nothing, but if word got out that I drank light beer; well there goes a very lucrative business as Dr. B.

Take care

drb

[Green]

Back late from dinner.  No test server up so I assume it is complete.  How did it go?

[drb]

Hoi Green,

It is up. If you do not see it try a refresh. I have had to refresh twice at one point.

Take care

drb

[KBFLordKrueg]

It would be wonderful if we can get the SQL work correcty.
I assume this means we'll have a WebMap now too?

[Lepton]

I guess my problem with using a major server as a stress test is what happened with RDSL (was that the one??).  After crashing like nuts, it had to go to a flatfile after a number of days, I believe.  I'm just hoping that you all have the flatfile ready to go if the SQL craps out.  If it works, great.  If not, there are going to be alot of frustrated people.   Let's hope for a bit of luck.

[FPF-DieHard]

I guess my problem with using a major server as a stress test is what happened with RDSL (was that the one??).  After crashing like nuts, it had to go to a flatfile after a number of days, I believe.  I'm just hoping that you all have the flatfile ready to go if the SQL craps out.  If it works, great.  If not, there are going to be alot of frustrated people.   Let's hope for a bit of luck.

Oh it was a joke, I'm not going to go live with it in SQL.   We just want to log enough activity for debugging purposes.

Noon kickoff will be Flatfile.   Hopefully we'll have SQL stable enough for "AOTK2: The Wrath of J'inn"

[Green]

Crashed at 1230am EST with 8 players on.  We were "hung-up" and unable to move.

[FireSoul]

Crashed at 1230am EST with 8 players on.  We were "hung-up" and unable to move.

That's not necessarily a bad thing. Logging being turned on, this may have caught something.

[Strafer]

MElf and Lkrueg or WSears (forget) witness shipyard go black, FSoul and KOTHGreen end a long battle and I move slowly to the same hex...

[likkerpig]

End of mission, lost connection.
Not on server list, refreshed twice.
Showed up, 9 people on.
Counted down while trying to connect to server.
Refreshed, no server. Refreshed again, server with 9 people on.
Counted down...
Will reboot my sys and give it one more try.


No joy, same results.

[drb]

Hoi Folks,

Posted by: likkerpig 

End of mission, lost connection.
Not on server list, refreshed twice.
Showed up, 9 people on.
Counted down while trying to connect to server.
Refreshed, no server. Refreshed again, server with 9 people on.
Counted down...
Will reboot my sys and give it one more try.


No joy, same results.

Same here. Strange, the server was set to restart itself. Well, it should show up in the log.
 
Take care

drb

[Bonk]

I guess my problem with using a major server as a stress test is what happened with RDSL (was that the one??).  After crashing like nuts, it had to go to a flatfile after a number of days, I believe.  I'm just hoping that you all have the flatfile ready to go if the SQL craps out.  If it works, great.  If not, there are going to be alot of frustrated people.   Let's hope for a bit of luck.

There was a single 20 minute SQL test for RDSL thats it, then RDSL was on the flatfile and its issues were gf settings (hourly burps). The kit's problems go waaaaayyyyyy beyond just how it handles SQL. The kit does not report gf errors in a useful way, the settings that are in error can only be determined by trial and error - lots of fun - give it a try sometime!

[Bonk]

Crashed at 1230am EST with 8 players on.  We were "hung-up" and unable to move.

That's not necessarily a bad thing. Logging being turned on, this may have caught something.

That sounds like the logfile bogging the server down. That is the main problem with this strategy, the logging itself can cause instability. THe server seems to choke when the logfile reaches 1 MB consistently (have observed this on a number of trials).

[Bonk]

Logs cleared, server rebooted to collect more MySQL data till we start on the flatfile later today!

[RazalYllib]

It is my opinion that sql should work.  The last true stress test was several dozen people, and IIRC they were all in the same hex and someone selected a mission.  Until that point in time, the server was doing OK, bit of a stutter, but ok.  The stutter was do to the logging.  I strongly urge the powers that be, to use the sql server kit when GW4 is live.  There may be absolutely wrong with it.  The problem experienced in the past may not be present during the course of normal play.  I would use the sql kit, and not tell the player base...ala single blind experiment.  If it crashes after a couple hours then restart with flatfile, but I do not think it will crash.

[RazalYllib]

Just curious, was enough data gathered to make worthwhile????

[FPF-DieHard]

I guess my problem with using a major server as a stress test is what happened with RDSL (was that the one??).  After crashing like nuts, it had to go to a flatfile after a number of days, I believe.  I'm just hoping that you all have the flatfile ready to go if the SQL craps out.  If it works, great.  If not, there are going to be alot of frustrated people.   Let's hope for a bit of luck.

There was a single 20 minute SQL test for RDSL thats it, then RDSL was on the flatfile and its issues were gf settings (hourly burps). The kit's problems go waaaaayyyyyy beyond just how it handles SQL. The kit does not report gf errors in a useful way, the settings that are in error can only be determined by trial and error - lots of fun - give it a try sometime!

I'll bet you a week's pay the issue on SQL was donor ships in the Server-side shiplist.   I removed all the donor ships from the server list for GW and things seem to be relatively stable.   GW3 was more stable, but there are other variables to account for that.

[Bonk]

Just curious, was enough data gathered to make worthwhile????

Yes we gathered enough data to make some conclusions about the serverkit (whether under load or not and whether on SQL or not). It turned out not to be a stress test at all but nevertheless was very revealing. Thanks to all those that helped!

[RazalYllib]

Reveal what was revealed

[Bonk]

Reveal what was revealed

The majority of SQL tests that have failed have had nothing to do with SQL and everything to do with undetermined gf errors and shiplist misconfigurations.

[RazalYllib]

Well that must be progress eh?