Forum Suggestions & User Assistance - posting order wrong

It would appear BikeForums went down for a while, but is now back up. However, its system time appears to be screwy. I just posted here (http://www.bikeforums.net/showthread.php?t=225842) (as did someone after me) and the posts are being inserted in the wrong positions because they are being assigned the wrong posting time.

Update: This appears to have been fixed.

not quite, i too noticed this today in a P&R thread.

It isn't resolved for older posts. But it's fixed in the sense that new posts (as of just before my second post in this thread) now show the correct time.

Now if you reply with quote then your reply goes directly under the original post rather then just being added to the end of the page in a time sequenced order. It makes sense in so far as a conversational reading style but I am used to going to the last page of a thread just to continue the conversation in stead of searching around looking for who said what. Also when you hit the post button and post my message you no longer go to the thread with all the pposts in order rather just a page with my post only on it and that new little thread title IFRAME at top.

Now if you reply with quote then your reply goes directly under the original post rather then just being added to the end of the page in a time sequenced order. It makes sense in so far as a conversational reading style but I am used to going to the last page of a thread just to continue the conversation in stead of searching around looking for who said what. Also when you hit the post button and post my message you no longer go to the thread with all the pposts in order rather just a page with my post only on it and that new little thread title IFRAME at top.

At the top right of each thread is a drop down menu named 'Display Modes', click that and select 'Linear Mode'. Did that fix the problem? It sounds like you selected one of the other options be accident.

^^ Duh yup I sure must have. So has those options been here all along and I just never saw them? I probably don't know 90% of what is capable on this site besides 'post quick reply'. Thanks and have a lovely day...

This is happening again.

This is happening again.

+1

it's not 10:41.... it's 3:44

Still doing it to me (posted at 4:00 PM)

Still doing it to me (posted at 4:00 PM)

+1.

Also, not getting any email notifications when thread to which I'm subscribed are updated.

it's not 10:41.... it's 3:44

this is a test....hmmm, now it seems OK.

I'm lost...where are we again? (posted at 7:24pm est)

Yeah...all out of order right now (7:25p EST)

The system is acting like the date on the server is incorrect, or set to the wrong timezone.

If you can get to a terminal window, type the "date" command. You have to be root to change it to the correct date.

It is exactly 5 hours early. That's why posts are showing up in the wrong order. Anything that was posted at the correct time before the crash is going to be posted at the correct time. Anything posted now is going to get a date stamp 5 hours earlier, which could be BEFORE the posts posted before the crash.

That explains how a reply to one of my posts is showing up earlier than my original post to which it is replying (which I made shortly before the crash).

Nope...still screwed up. I just replied to post #22 in this thread (http://www.bikeforums.net/showthread.php?p=3165894&posted=1#post3165894), and my post appeared as post #19.

Test

It hasn't been fixed, and the post times are ALL wrong.

Hello,

This has now been resolved, we had 2 seperate issues.

1) Our datacenters resolvers are down which caused the time server not to sync correctly(hence the 5 hours out of date). I have added the new resolvers and have rsynced to time.nist.gov.

2) The database was not calculating the unqiue ids correctly due to the incorrect row numbers. This has been corrected also.

The posts made during this time will remain in place, but all new posts will be working correctly.

-Scott

Hello,

This has now been resolved, we had 2 seperate issues.

1) Our datacenters resolvers are down which caused the time server not to sync correctly(hence the 5 hours out of date). I have added the new resolvers and have rsynced to time.nist.gov.

2) The database was not calculating the unqiue ids correctly due to the incorrect row numbers. This has been corrected also.

The posts made during this time will remain in place, but all new posts will be working correctly.

-Scott
Not that it matters, but I don't see how these are two separate issues.

The "unique ids" in the database referenced in #2 are usually a function of the current time. It is the wrong time on the server which caused the database to calculate the "unique ids" incorrectly. It's all the same problem.

By the way, if you can identify the unique id of the first message that was posted after the system was restarted with the time incorrect, and the unique id of the last message that was posted before the time problem was corrected, then you should be able to fix all the posts that were posted incorrectly by adding 5 hours (18000 seconds) to each of the time stamp unique ids for the messages with unique ids that fall within the range delimited by the first and last messages you identified.

Not that it matters, but I don't see how these are two separate issues.

The "unique ids" in the database referenced in #2 are usually a function of the current time. It is the wrong time on the server which caused the database to calculate the "unique ids" incorrectly. It's all the same problem.

By the way, if you can identify the unique id of the first message that was posted after the system was restarted with the time incorrect, and the unique id of the last message that was posted before the time problem was corrected, then you should be able to fix all the posts that were posted incorrectly by adding 5 hours (18000 seconds) to each of the time stamp unique ids for the messages with unique ids that fall within the range delimited by the first and last messages you identified.

The posting order was because of the dates, however inserting of unique ids has nothing to do with the date since they are calculated by the database going on the last insert. However when the database "corrupts" the row count was incorrect which was causing duplicate id errors. The table has to be repaired to have the correct row count otherwise it will just continue with invalid ids which in turn would cause even more errors when trying to view threads with the same id (since technically it's only designed for 1 match when selecting an id, not 2)

-Scott