every so often the server fails to correctly display some data.
Specifically when people send updates, rarely the new character field doesn't get handled and shows zero... then the next update shows both the new characters for that update and the missing update display.
I'm expecting that realms with accent marks have the data.. but the display routines need tweaking to present the data... this has been a long term problem that just wasn't noticed and handled.
Metalbeast is looking at the code routines, it appears there is a race condition where rarely the allowed times expire before the process finished.
He is doing a re-write of these routines.. He thought he might have a solution by the end of the week, but after further thought and discussion... the update to fix the display may take a little longer.. it is better to be right then to be fast.
Known issue
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Sunday 4/28 appears to have suffered a glitch in the processing of upload data.
From what I can see the realm/factions that had complete census run reports did correctly update the counters for server submissions.
However some uploads didn't get character data processed into the database.
Metalbeast has been notified.. more info if I find anything out or/and when I get any updates from Metalbeast.
From what I can see the realm/factions that had complete census run reports did correctly update the counters for server submissions.
However some uploads didn't get character data processed into the database.
Metalbeast has been notified.. more info if I find anything out or/and when I get any updates from Metalbeast.
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Metalbeast is debating with himself if he should invoke a restart of the MySQL database engine.. in case there is some cache issues...
I ran a few more EU census runs and submitted my update ... and it processed cleanly.. with vary large numbers.. indicating that all the data that should have processed in the previous two 0 0 Y runs had cleanly processed.
So again we see a situation where if your data doesn't update.. then keep it in your data file until you get an update processed..
or in other words .. if you routinely prune your data.. make sure the data upload processed cleanly before you do your next prune.
I ran a few more EU census runs and submitted my update ... and it processed cleanly.. with vary large numbers.. indicating that all the data that should have processed in the previous two 0 0 Y runs had cleanly processed.
So again we see a situation where if your data doesn't update.. then keep it in your data file until you get an update processed..
or in other words .. if you routinely prune your data.. make sure the data upload processed cleanly before you do your next prune.

I know it's a known issue, but just to add the submissions numbers are getting worse for me, today was a nice example:
May 12, 14 10:34:51 1352 1009 Y
May 12, 14 07:07:45 194 194 Y
Those are the exact same file, I re-uploaded it after the first go looked way too low on both sides. How did it manage to then find more new than updated?! Maybe I'm just unlucky but my submissions this month have nearly all looked wrong, so I hope you or Metalbeast can get to the bottom of it soon
May 12, 14 10:34:51 1352 1009 Y
May 12, 14 07:07:45 194 194 Y
Those are the exact same file, I re-uploaded it after the first go looked way too low on both sides. How did it manage to then find more new than updated?! Maybe I'm just unlucky but my submissions this month have nearly all looked wrong, so I hope you or Metalbeast can get to the bottom of it soon

- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Metalbeast believes it is part of the system safety code that is in place to prevent run away bad file processes.
The code is pretty standard coding practices but needs to be evaluated and tweaked for our usage patterns.
I'm seeing the same issues as I use my alternate WoW client to squash those EU 0 0 realms.
I run about 50 realm/faction combos and then at end of day upload.
Sometimes I get 0 0 Y
and after a 2nd submission with no changes to the file I might see >5000 >10000 Y
The question is what is happening on the site that causes the processing to timeout.. or whatever is happening.
Due to the fact that I know IRL Business etc. issues are limiting Metalbeast time to work the problem I offered (hesitantly) to help on website side of things.
It has been awhile since I've worked this side of IT and I'll need to spend time chipping off the rust before I can really provide help.
But at least I have the time to put eyes on the issue and maybe I can point out the area of concern and the fixes.
I'm leaving the actually implementation of any fixes to Metalbeast and his staff.
We wouldn't want to have our own version of the Heart Bleed bug.. because something I suggested might lead to bigger problems.
The code is pretty standard coding practices but needs to be evaluated and tweaked for our usage patterns.
I'm seeing the same issues as I use my alternate WoW client to squash those EU 0 0 realms.
I run about 50 realm/faction combos and then at end of day upload.
Sometimes I get 0 0 Y
and after a 2nd submission with no changes to the file I might see >5000 >10000 Y
The question is what is happening on the site that causes the processing to timeout.. or whatever is happening.
Due to the fact that I know IRL Business etc. issues are limiting Metalbeast time to work the problem I offered (hesitantly) to help on website side of things.
It has been awhile since I've worked this side of IT and I'll need to spend time chipping off the rust before I can really provide help.
But at least I have the time to put eyes on the issue and maybe I can point out the area of concern and the fixes.
I'm leaving the actually implementation of any fixes to Metalbeast and his staff.
We wouldn't want to have our own version of the Heart Bleed bug.. because something I suggested might lead to bigger problems.

Hmm, that's interesting, I was starting to wonder if EU might be a common theme, since myself and ER are based here and you and Padanfain both drop in. Going down the top new ones list for this month almost confirmed it, 4 others EU-based with messed up results, one with no claimed characters, but this guy bucks the trend, as his characters are in the US: http://www.warcraftrealms.com/usersheet ... 040304&c=u - still, I guess it's possible he may be another one with an alt account!
Very glad you can help out, without intending any disrespect to Metalbeast, you're present and active so much more that I have faith in you getting to the problem and its solution much sooner
Very glad you can help out, without intending any disrespect to Metalbeast, you're present and active so much more that I have faith in you getting to the problem and its solution much sooner
