Dynaverse.net
Taldrenites => Dynaverse II Experiences => Topic started by: Dizzy on January 23, 2005, 03:47:21 pm
-
Server reset at 2271.18x
Same map as we had this morning.
Using the provided SGO4 uninstaller, UNINSTALL the OLD SGO4 from your HD then after D/Ling the new one, run it.
http://fire.prohosting.com/astinky/SGO4/SGO4.exe
Mirror 1
http://members.lycos.co.uk/astinky/SGO4/
Or Mirror 2
http://69.115.120.11:9000/images/SGO4.exe
Now, Bonk and I have busted our asses to come up with nothing but a bandaid fix, however we did find the problem and it'd take a week to 2 weeks to fix. It is almost entirely a shiplist issue dealing with class types and FY/LYA dates. Our bandaid should be good enough to work as well or better than past servers have, but this experience has put me and Bonk on the path towards a complete solution.
So if this doesnt work, what we did today, then I'm sorry, but SG4 will be delayed for two weeks till all these problems are fixed. I'm surprised, tho, that the past servers were able to run at all considering all the errors that have been carried over since we started modding the stock list.
I surmise this donor list for SG4 will be close to the template used for future 'donor' servers. There have been a LOT of lessons learned. I hope we can document this for future campaigns to benefit from.
Ok, well, thats about it! Cross your fingers!
-
Ok, it had several 'burps' where it's knocked peeps off since the reset.
Good news is the DB hasnt gotten any bigger which means no critical errors are happening.... So the burps may be that part of that 'takes 2 weeks to fix' part I detailed above.
Oh well, its as good as its likely gonna get. ;)
HF while it lasts...
-
Again will changing the start date to 73 not fix the problem?
(as opposed to waiting 2 weeks or so?)
-
WONT MATTER, oops caps
-
So what exactly is the problem? You forgot to mention that part. By the way, the incidence of server crashes remains unchanged, irrespective of server load.
-
So what exactly is the problem? You forgot to mention that part. By the way, the incidence of server crashes remains unchanged, irrespective of server load.
It is a shiplist YFA issue that remains unresolved. We may attempt another fix (taking the time necessary), decision depending on the group...
-
I'm surprised, tho, that the past servers were able to run at all considering all the errors that have been carried over since we started modding the stock list.
This may answer a question I've had for several years. I think most of our more recent servers (mine included!) have been a lot less stable than our older servers from years ago. I've noticed this for a long time. Remember servers like Articfire, where hundreds of people would play for weeks on a friggin huge map, and there was no DB cleaner at all? Yet these days we need to clean the DB at least once a day to get decent results.
In the back of my mind the last two years, I've remembered the connection issues I had with OP when it first came out and wondered if OP was simply less stable than EAW. But Dave always said this wasn't true, and that it should be more stable than EAW. Maybe you guys have found the real reason.
What is the FYA issue? Is it just that certain ships classes aren't available in certain years, leading to errors when AI is trying to be created? I've run into that one when trying to create servers with limited shiplists. Or have you found something more insidious?
-S'Cipio
-
Yes we have. Right now we are working on a fix. And it is very specific. All future servers may run like articfires w/o the need for daily DB cleaners. Wouldnt that be something? I'll keep u posted.
-
SG4 has been up and running for Edit: 6 1/2 hrs now w/o a crash. ;)
-
8 1/2 hours now, no crashes.
-
8 1/2 hours now, no crashes.
And then I signed on... WAHAHAHA!
-
No, it still has not crashed today (under low load however).