• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!

We're back (downtime 9/20/11)

Jump to latest Follow Reply
Sort by date Sort by votes
Saw31;1995999; said:
Hasn't happened since.

The thread would never "record" that I went in and viewed it. It would continually take me back to the same post as if that was where I had left off the last time I visited the thread. I can point you to the exact post where it "froze" if that helps...
Click to expand...

Mine froze on Coqui's last post. I unsubscribed from the thread and have since re-subscribed; therefore, I don't know what may have fixed it or not.
 
Upvote 0
Saw31;1995999; said:
Hasn't happened since.

The thread would never "record" that I went in and viewed it. It would continually take me back to the same post as if that was where I had left off the last time I visited the thread. I can point you to the exact post where it "froze" if that helps...
Click to expand...

Nope, shouldn't be necessary. Thanks for the offer though. One of the two tables that ended up completely corrupted and broken today (which is to say worse than the others that had crashed) was the one that handles/records when a thread is read by a given user. My best (and entirely uninformed/rank amateur) guess is that there was overhead and/or some sort of tomfoolery with that table before todays server event.

Either way, if you see that sort of behavior again (where something doesn't register a thread visit within, say, an hour or so) please do let us know.

Thanks for the info (muffler and Saw)!
 
Upvote 0
Saw31;1995999; said:
Hasn't happened since.

The thread would never "record" that I went in and viewed it. It would continually take me back to the same post as if that was where I had left off the last time I visited the thread. I can point you to the exact post where it "froze" if that helps...
Click to expand...


It appears those posts no longer exist. Interesting.

The "2011 TSUN shenanigans" thread says the last post was posted 9/13/11 by Coqui (on the college football board index page 3), but when you go into the thread, the last post appearing is from Tlangs on 9/3/11. So the post where I was "hung up" doesn't exist anymore in the thread...
 
Upvote 0
muffler dragon;1996002; said:
Mine froze on Coqui's last post. I unsubscribed from the thread and have since re-subscribed; therefore, I don't know what may have fixed it or not.
Click to expand...


Pretty sure that was where I was too. I would know for sure if I could read it, but apparently it is gone.
 
Upvote 0
Saw31;1996008; said:
Pretty sure that was where I was too. I would know for sure if I could read it, but apparently it is gone.
Click to expand...

Can't speak to what happened to the post, but it definitely sounds like there was a problem with it. Like the post we 'lost' today when I repaired the tables, it may simply have been corrupted or had simply been deleted/moved/merged/split by an admin or mod.

The important thing is that it's not happening now, and I hope and expect we'll be fine going forward.

Sorry about the headache with it. Wish I were better at/with this stuff. No I don't. Wish we had someone who was better at it taking care of that end of things. :)

--edit--
I just posted in that thread and then deleted the post, the 'last post' timestamp now correctly reflects the 3rd.
 
Upvote 0
Clarity;1995954; said:
Gasoline and matches. vBulletin has built in repair tools, but those failed spectacularly. Today it took going into mySQL and identifying the crashed and corrupted tables there and running repair processes there. It appears only one post was lost as part of this process (as noted above). The corruption was the result of the server issue, and hopefully the server issue was a one-and-done, rather than something that will occur again. If it does reoccur, we'll figure it out.
Click to expand...
How did you identify the crashed/corrupted tables and how did you run the repair processes there?
 
Upvote 0
JCOSU86;1996013; said:
How did you identify the crashed/corrupted tables and how did you run the repair processes there?
Click to expand...

By error messages/logs and what vB's (failed) maintenance/overhead/repair tool was telling me. By logging into mySQL itself and running individual repair commands on each table beyond the repair ability of vB itself.
 
Upvote 0
Clarity;1996003; said:
My best (and entirely uninformed/rank amateur) guess is that there was overhead and/or some sort of tomfoolery with that table before todays server event.
Click to expand...

Tomfoolery in the shenanigans thread? That's malarkey!!11!11!!1

work.7319924.1.sticker,375x360.tomfoolery-v1.png
 
Upvote 0
Yeah, not a big deal Clarity. The only reason I mentioned it (had forgotten about it) was because muffler had the same thing. Figured it may have been a symptom of something after hearing about the crash...
 
Upvote 0
Saw31;1996038; said:
Yeah, not a big deal Clarity. The only reason I mentioned it (had forgotten about it) was because muffler had the same thing. Figured it may have been a symptom of something after hearing about the crash...
Click to expand...

Oh hey, I appreciate the reports. Wish I could speak in absolutes about what caused it, but I feel pretty good about it not happening again after cleaning up the specific table that might have triggered it. If I sound frazzled, it's only because major outages/problems like today really do kick my butt. I was out at a doc appointment when I found out through FB that we were down, and next I knew my gmail inbox had 3k+ error messages in it, lol. Anyway, all fixed now, and if it happens again we'll be prepared. Hopefully it was just a one time event.

Don't hesitate to report any oddities like that in the future, and thanks for the help.
 
Upvote 0
ochre;1996056; said:
probably that btn applet that's messing with browser history... :)
Click to expand...
That couldn't do anything to our database, but it will be nice when we can switch back to Admonkey's smaller cage. That ad is a big help for current finances, though, so I'm really glad we have it.
 
Upvote 0
Deety;1996058; said:
That couldn't do anything to our database, but it will be nice when we can switch back to Admonkey's smaller cage. That ad is a big help for current finances, though, so I'm really glad we have it.
Click to expand...
I just figured, with the way it is affect client behavior, it could be flooding the last viewed table
 
Upvote 0
You must log in or register to reply here.
Back
Top