AAARGH! Bikejournal.com down!!

[mary9761]

I just got home from watching the grandsons and logged on here then tried to head over to bikejournal.com. Evidently there's some sort of server issue!!:eek::eek: Anyone know how long it's been down?

[jobob]

In really big red letter on the logon page:

We are working on the server due to a service issue. We'll have the site back up as soon as possible. I'm sorry for the inconvenience. Thanks for your patience. -Slantz

[mary9761]

hi jobob, yeah, I'd seen that I was just wondering if anyone knew how long it had already been down today?

[Fredwina]

at least since noon PST Ok, I broke it:rolleyes:

[tulip]

It goes down from time-to-time; it's a big job to keep it going. Slantz works hard to keep it going.

[BleeckerSt_Girl]

at least since noon PST Ok, I broke it:rolleyes:

Yeah, I believe that too!
Just like how on the news the other day that National Debt $ clock ran out of digits
because our nation's debt has become so gigantic.....Fredwina must have broken BikeJournal when they ran out of digits to record her mileage!! :eek:

[Geonz]

My theory is that Howard got a red cross by his name and the server couldn't stand it. I was going to ride all night to catch up to him (he got 180 miles ahead of me as of this weekend waht with Saturday's 108 miles to Wyoming)...

Still down today... snork... what if all the mileage got lost?

[arielmoon]

I keep checking every few hours. I hope it is back up soon! :D

[OakLeaf]

I'm going to forget to log my miles from yesterday, I just know it. :p

[lph]

arrh, I'm getting all twitchy here. Want to log my miles for yesterday... want to log my miles for today...*twitch*

[SouthernBelle]

It's up, but read only now while they check things out etc.

[Velobambina]

Still down!

[mary9761]

It says that it's read only, but I've not even been able to get the forum open to read. I hope it's back up soon.

[lph]

*meep*

:(

[Fredwina]

from the banner on the webpage, it looks like Slantz had a hacker attack and corrupt the database. I imagine the extra downtime is to repair the database and make the site more hacker-proof.

[Geonz]

Let's see... I had 34.5 miles on Monday, 23 on Tuesday, and 16 yesterday. Now there's a wreckered.

I was just reading that the esteemed candidates in teh campaign had people hacking into their files, too...

[Geonz]

Just the regular commute at 16.3 miles yesterday o on the Trek because I did the inside ride at the bike shop.

[SouthernBelle]

Just the regular commute at 16.3 miles yesterday o on the Trek because I did the inside ride at the bike shop.

Ah. So you're one who doesn't count their inside miles!

[mary9761]

As most of you know by now, we had an automated attack on our database, Monday, Nov. 3rd. Nothing personal as far as I understand - but that doesn't make it any less vicious. As a result, many records were overwritten with a malicious URL (website address). This resulted in the following unfortunate cascade of events:

1) The site was down: We had to take the database offline for 4.5 days while we attempted to fix the damage.

2) Some data was lost: In the course of attempting repairs, I found a backup task had stopped a few weeks ago after a security update, and some backup files were accidentally deleted as well. This resulted in the inabililty to easily restore the database to its proper state. The ultimate result of this, after much heroic rescue effort, is that some of the text data truncated by the attack is not recoverable. Thankfully it did not infect journal data directly, but, most notably and regretfully, blog entries from the past two months are decimated. Other areas affected, which need to be updated by their respective contributors, are recent changes or additions (past 2 months) to the following items: bike descriptions; bike club, route, organized ride, and bike shop information; and personal effort levels and bike chain maintenance descriptions. Note that none of the records are missing, but the text is truncated to 30 characters or less in most of these cases. Thanks for your help in restoring the data.

3) The site must be re-designed to prevent this attack in the future. As a result, I'm reviewing all pages and updating them as needed. Until they pass inspection, the pages will not be accessible. I will focus on getting ride entry back up as soon as possible, hopefully by the end of this weekend. The status bar above will track overall progress in restoring the site.

4) We aren't out of the woods yet: Note that we haven't been able to verify everything is working as it should, so there may be other issues that we haven't uncovered yet. Overall, it looks like we are on the recovery path now, but there may be some rocky trails ahead of us the next few days.

I apologize greatly for the downtime and loss of data. It's been a tough week for everyone who enjoys the site, myself included. I will extend all active premier memberships by a week because of the problems. On the positive side, the site will improve as a result, and our nightly backups will be monitored so that this can't happen in the future. Lots of thanks go to dallasbikr who spent many hours during a busy work week to get the database restored. And big thanks to SouthernYankee who is helping to review the site updates needed to prevent this going forward. Thank you all for the supportive emails and for your extended patience during this time.
- slantz


:(:(:(:(:(

[Geonz]

Yea... and basically that's the only page that's up. Doesn't say anything about the discussions.

[mary9761]

There are some pretty popular long running threads. I hope they're all intact. :eek::(

[mary9761]

I was able to log my 11/5 ride into my journal this morning. Not much else working yet but at least it appears the journal function is back up. I don't envy Slantz reworking the entire site because of some jerk.. :(:mad:

[Geonz]

Welp, it's one of those "automated bot attacks," I think. I suspect if you know how to do it you could earn a living - not legally, of course!...

Yea, I came back to this thread to find my miles & record them. And I wonder if some of the moderators don't secretly hope the "forum" takes its sweet time reviving ;) It might have been tough during the election and post-election fervors...

Oh, my... I"m a mere fourteen miles behind Howard and I did 6.7 already today. If I sneak out at lunch and do 9 miles I could get ahead of him ... until he logs his miles, of course ;)

[Grog]

I get a password error all the time. Is it just me?

[kelownagirl]

I can log in now, Grog. I thought I might try to export my data while it's still intact but that part isn't working.

[Geonz]

It says there are password issues - to wit:
"Note: If you have having trouble accessing your journal, log out and back in. I corrected a bug on the login page - you now need to follow correct capitalization of your username and password to login. I'll get the password recovery page up later today in case you don't remember."

[7rider]

I get a password error all the time. Is it just me?

Nope. Me, too.
I could log in yesterday, but couldn't see my journal or blog (I didn't try to hit the forum).
Today, I can't log in.

[Geonz]

The "everybody's stats page" is back up!!! I can see Howard's 102 miles ahead of me... my motivation is back!

(I' m utterly embarrassed at how that's not entirely facetious...)

[mary9761]

SITE STATUS
Areas fixed, in order of most recent: manage clubs club home journal upload/download configure journal options and columns site preview and signup stats tables journal view/calendar/add/edit/delete individual profiles site login and home page

[mary9761]

There are still some pages down and Slantz is working on them, but the forums are BACK! :cool::D:D