User Pass
Home Sign Up Contact Log In
Page:
 
n:iceman:16
offline
Link
 
Originally posted by Larry Roadgrader
Originally posted by Iceman16

Cliffs on past 15 pages plz


Bort updated the changelog in partial response to the problem. It may or may not solve the problem. Others continue to pile into the thread without reading first 50+ pages and in doing so look rather silly.


 
Signalsgt
offline
Link
 
Originally posted by CapnEnnui
142nd, actually.

But it's OK because I F'ed up the link in your quote too.


I was going off memory, only remembered the name of the song
 
Bogleg
offline
Link
 
Originally posted by Signalsgt
Originally posted by

Originally posted by RandomBeast
any explanation about why the same WR has his packet dropped/corrupted every sim? If it were an error in the database itself, sure, but if it is a transmission thing...?


Originally posted by Deathblade

Pretty much...we aren't entirely sure if it will even change anything, but it might, so it wouldn't be fair to not add a changelog note.


I still don't buy corrupted packets, TCP traffic simply does not work that way.

Mr. Packet leaves Borts machine with a header, he shows up at the server and the header presents a SYN. The server sends a SYN-ACK handshake back to Borts machine and Mr. Packet along with his friends deliver the data in sequential order. Once all packets have left Bort's machine it sends a FIN. The Server makes sure that all packets have arrived in order and un-corrupted and responds FIN-ACK and shuts down the connection.

Now if Mr. Packet is out of sequence or the data doesn't match the header then the packet is resent, to include a dropped packet.

http://en.wikipedia.org/wiki/File:Tcp_state_diagram_fixed.svg =>Follow the arrows folks.





I have skimmed the last XX pages, and I have more than my share of Perl + MySQL (InnoDB, MyISAM, whatever) troubleshooting under my belt. Bort said somewhere back there that the table in question is so super-huge that a consistency check on it would take an unacceptable amount of time. And he said that MySQL is just saying "goodbye" mid-response.

And it always affects the same players.

I don't see how there's any way this can be anything but a corrupted table. If it were a networking problem, TCP would retransmit, and you should see a delay, but not any change in your query response. If TCP didn't correct the problem, you'd still not see the consistently wrong results -- it'd affect a more random set of players. If it were a bad RAM situation, you'd very likely see more random results (and probably software crashing here or there, too). Disk errors would be equivalent of either corrupt database/table or bad RAM in end-user experience, I'd think.

But, if it's a corrupt table, I don't see how a web server querying the same DB would not see the same symptoms. But stranger things have happened, I'm sure.

There are a few options to fixing broken tables, or at least finding out what's wrong.

The easiest way (to me) is to setup a slave MySQL server, run a mysqldump on the master with the master data intact, import that into the slave, and setup slave replication so that it'll catch up. That'll get a copy of the data as mysqldump sees it, but not the same on-disk image. Unfortunately, that mysqldump can take a damn long time, too. With a lot of careful work, it can be done one table at a time.

Or you can just bite the downtime and run the db check and get it fixed. And hope that's the problem.
 
ThaOutlaw
offline
Link
 
Cliff Notes

There is no X-factor per Bort.

There may be a bug somewhere per Bort.

Things are being looked in to per Bort.







Cliff Notes for Conspiracy Theorist

X-factor has been proven

GLB clean-up crew has taken over to "Bort" the x-factor

Bort is a computer program



Spot on?
 
Deathblade
offline
Link
 
Originally posted by Bogleg
I have skimmed the last XX pages, and I have more than my share of Perl + MySQL (InnoDB, MyISAM, whatever) troubleshooting under my belt. Bort said somewhere back there that the table in question is so super-huge that a consistency check on it would take an unacceptable amount of time. And he said that MySQL is just saying "goodbye" mid-response.

And it always affects the same players.

I don't see how there's any way this can be anything but a corrupted table. If it were a networking problem, TCP would retransmit, and you should see a delay, but not any change in your query response. If TCP didn't correct the problem, you'd still not see the consistently wrong results -- it'd affect a more random set of players. If it were a bad RAM situation, you'd very likely see more random results (and probably software crashing here or there, too). Disk errors would be equivalent of either corrupt database/table or bad RAM in end-user experience, I'd think.

But, if it's a corrupt table, I don't see how a web server querying the same DB would not see the same symptoms. But stranger things have happened, I'm sure.

There are a few options to fixing broken tables, or at least finding out what's wrong.

The easiest way (to me) is to setup a slave MySQL server, run a mysqldump on the master with the master data intact, import that into the slave, and setup slave replication so that it'll catch up. That'll get a copy of the data as mysqldump sees it, but not the same on-disk image. Unfortunately, that mysqldump can take a damn long time, too. With a lot of careful work, it can be done one table at a time.

Or you can just bite the downtime and run the db check and get it fixed. And hope that's the problem.


Now THIS guy sounds legit.
 
lizrdgizrd
offline
Link
 
Originally posted by Dmac2008
Can I please get some Cliff notes?

I think I have an X-factor player but, this season I think I may have broken him.


Synopsis: serious evidence of potential x-factor presented. Discussion ensued. Bort pleads the 5th on current or future x-factors via Jed who relays this info from mod forum. Shit hits fan. Bort makes small change to sim to remove potential height/weight data transmission errors. Shit hits fan. Nobody really sure if this was x-factor and if it has been borted or not.

We now return you to your regularly scheduled forum, now in progress.
 
Signalsgt
offline
Link
 
Originally posted by Bogleg
I have skimmed the last XX pages, and I have more than my share of Perl + MySQL (InnoDB, MyISAM, whatever) troubleshooting under my belt. Bort said somewhere back there that the table in question is so super-huge that a consistency check on it would take an unacceptable amount of time. And he said that MySQL is just saying "goodbye" mid-response.

And it always affects the same players.

I don't see how there's any way this can be anything but a corrupted table. If it were a networking problem, TCP would retransmit, and you should see a delay, but not any change in your query response. If TCP didn't correct the problem, you'd still not see the consistently wrong results -- it'd affect a more random set of players. If it were a bad RAM situation, you'd very likely see more random results (and probably software crashing here or there, too). Disk errors would be equivalent of either corrupt database/table or bad RAM in end-user experience, I'd think.

But, if it's a corrupt table, I don't see how a web server querying the same DB would not see the same symptoms. But stranger things have happened, I'm sure.

There are a few options to fixing broken tables, or at least finding out what's wrong.

The easiest way (to me) is to setup a slave MySQL server, run a mysqldump on the master with the master data intact, import that into the slave, and setup slave replication so that it'll catch up. That'll get a copy of the data as mysqldump sees it, but not the same on-disk image. Unfortunately, that mysqldump can take a damn long time, too. With a lot of careful work, it can be done one table at a time.

Or you can just bite the downtime and run the db check and get it fixed. And hope that's the problem.


Wonder Twin Powers...Activate

...what he said on the DB stuff.
 
Dmac2008
offline
Link
 
Originally posted by lizrdgizrd
Originally posted by Dmac2008

Can I please get some Cliff notes?

I think I have an X-factor player but, this season I think I may have broken him.


Synopsis: serious evidence of potential x-factor presented. Discussion ensued. Bort pleads the 5th on current or future x-factors via Jed who relays this info from mod forum. Shit hits fan. Bort makes small change to sim to remove potential height/weight data transmission errors. Shit hits fan. Nobody really sure if this was x-factor and if it has been borted or not.

We now return you to your regularly scheduled forum, now in progress.


TYVM
 
Michael Vick
offline
Link
 
Originally posted by ThaOutlaw
Cliff Notes

There is no X-factor per Bort.

There may be a bug somewhere per Bort.

Things are being looked in to per Bort.







Cliff Notes for Conspiracy Theorist

X-factor has been proven

GLB clean-up crew has taken over to "Bort" the x-factor

Bort is a computer program



Spot on?


I'm not reading all of this so I hope so
 
Link
 
Originally posted by Bogleg
I have skimmed the last XX pages, and I have more than my share of Perl + MySQL (InnoDB, MyISAM, whatever) troubleshooting under my belt. Bort said somewhere back there that the table in question is so super-huge that a consistency check on it would take an unacceptable amount of time. And he said that MySQL is just saying "goodbye" mid-response.

And it always affects the same players.

I don't see how there's any way this can be anything but a corrupted table. If it were a networking problem, TCP would retransmit, and you should see a delay, but not any change in your query response. If TCP didn't correct the problem, you'd still not see the consistently wrong results -- it'd affect a more random set of players. If it were a bad RAM situation, you'd very likely see more random results (and probably software crashing here or there, too). Disk errors would be equivalent of either corrupt database/table or bad RAM in end-user experience, I'd think.

But, if it's a corrupt table, I don't see how a web server querying the same DB would not see the same symptoms. But stranger things have happened, I'm sure.

There are a few options to fixing broken tables, or at least finding out what's wrong.

The easiest way (to me) is to setup a slave MySQL server, run a mysqldump on the master with the master data intact, import that into the slave, and setup slave replication so that it'll catch up. That'll get a copy of the data as mysqldump sees it, but not the same on-disk image. Unfortunately, that mysqldump can take a damn long time, too. With a lot of careful work, it can be done one table at a time.

Or you can just bite the downtime and run the db check and get it fixed. And hope that's the problem.


 
Kevin Smith
offline
Link
 
Originally posted by Bogleg


setup a slave MySQL server, run a mysqldump on the master with the master data intact, import that into the slave, and setup slave replication so that it'll catch up. That'll get a copy of the data as mysqldump sees it, but not the same on-disk image. Unfortunately, that mysqldump can take a damn long time, too. With a lot of careful work, it can be done one table at a time.




Doing that to Tautīs wife tonite.
 
lizrdgizrd
offline
Link
 
Originally posted by Dmac2008
TYVM


YW
 
Kegergator
offline
Link
 
Originally posted by Kevin Smith

Doing that to Tautīs wife tonite.



loooooooooool
 
Dacolts
offline
Link
 
Originally posted by Bort
When the sim reads the data, it does a sanity check and makes sure it is not out of line of expected values.


If this can't be a verified fix, couldn't each position get a common height/weight so the X-factor is eliminated?
 
Jack Del Rio
offline
Link
 
or could we eliminate height/weight's effect on the sim altogether? :|
 
Page:
 


You are not logged in. Please log in if you want to post a reply.