Please Scroll Down to See Forums Below
napsgear
genezapharmateuticals
domestic-supply
puritysourcelabs
UGL OZ
UGFREAK
napsgeargenezapharmateuticals domestic-supplypuritysourcelabsUGL OZUGFREAK

This thread mixup bug thing ...

sk*

New member
This shit really needs to be fixed. It is far from just annoying and the problem wouldn't take more than 5-10mins to fix.

Can we make this a sticky until it gets fixed?

-sk
 
It doesn't only happen with the first post in the thread either.

Seems to be related to people having different times?
 
I'm sure it would of already been fixed if it only took 5-10 minutes. I'm sure the board's code is being read daily to see the problem.
 
WizKid25 said:
I'm sure it would of already been fixed if it only took 5-10 minutes. I'm sure the board's code is being read daily to see the problem.

Right, lol.

Bro, this isn't something serious. I imagine it happened cause they tried to add something to the board, all they have to do is go back and upload the old php files an worry about the upgrade later.

This is so easy that is absurd, all the vbulletin files are available and all they have to do is a small comparason to see what's wrong. I am thinking that maybe george doesn't realize that this problem exists?

From what I can tell, you are right zander. I think it has to do with the different time zones too.

-sk
 
It is caused by our using multiple web servers instead of one. Post some example URL's and we will take a look -- we are working on a major upgrade and may do everything all at once.
 
George Spellwin said:
It is caused by our using multiple web servers instead of one. Post some example URL's and we will take a look -- we are working on a major upgrade and may do everything all at once.

So the times aren't syncronized on both servers?

-sk
 
It has to do I believe with the post id number. One server might not know the correct post id number if the other server wrote to the database at the exact same moment with another person's post. Then the order would get off for a short time.
 
George Spellwin said:
It has to do I believe with the post id number. One server might not know the correct post id number if the other server wrote to the database at the exact same moment with another person's post. Then the order would get off for a short time.

Ahh ic, makes sence. How do you guys distinguish which server each post is sent to? I am guessing regional?

Maybe instead you can send each thread to the same server or you can just add a different field that will send the miliseconds along with the post# which will make it easier for distinguish which post comes when. A new field would increase the database size so I would vote for the former ...

-sk
 
sk* said:


Ahh ic, makes sence. How do you guys distinguish which server each post is sent to? I am guessing regional?

Maybe instead you can send each thread to the same server or you can just add a different field that will send the miliseconds along with the post# which will make it easier for distinguish which post comes when. A new field would increase the database size so I would vote for the former ...

-sk

Or if that doesnt work you could just do a cold reboot. How come nobody thought of that?
 
Top Bottom