ForceField (OP)
aka Vitaliy
Sr. Member
Offline
Activity: 386
Merit: 250
|
|
June 28, 2012, 01:58:35 PM Last edit: June 28, 2012, 08:54:37 PM by Vitaliy |
|
When trying to access bitcointalk.org today, the following error message was displayed on a blank white page:
"Table './bitcoin/smf_sessions' is marked as crashed and should be repaired"
|
PC Hardware & Electronics For BTC Traded w/: Kansattica | jduck1987 | shakaru | newdude | nitetrader | midievil | blo8i | mb300sd | juggalodarkclow | Garr255 | Tril | Ringmasta | SysRun | CrazyBlane | sokay | BCB | str4wm4n | PinkBatman | Bitobsessed | matauc12 | antimattercrusader | BryanK
|
|
|
|
|
|
|
|
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Grouver (BtcBalance)
|
|
June 28, 2012, 02:00:07 PM Last edit: June 28, 2012, 02:10:29 PM by Grouver (BtcBalance) |
|
Got an "Got error 134 from storage engine" message. So I assume the database crashed or was full?
|
|
|
|
davout
Legendary
Offline
Activity: 1372
Merit: 1007
1davout
|
|
June 28, 2012, 02:09:49 PM |
|
Usually happens to MySQL when the partition it sits on is full.
|
|
|
|
John (John K.)
Global Troll-buster and
Legendary
Offline
Activity: 1288
Merit: 1225
Away on an extended break
|
|
June 28, 2012, 02:14:48 PM |
|
Who brought it back online? theymos is off IIRC.
|
|
|
|
Maged
Legendary
Offline
Activity: 1204
Merit: 1015
|
|
June 28, 2012, 02:55:46 PM |
|
Who brought it back online? theymos is off IIRC.
Most likely it was Mark (MagicalTux). Also, based on when the posts stopped, we either reverted to a DB backup, or this was the result of the backup. I don't have a tracker watching when the forum is down (since I can't do anything anyway), so I don't know which it was.
|
|
|
|
Stephen Gornick
Legendary
Offline
Activity: 2506
Merit: 1010
|
|
June 28, 2012, 04:53:16 PM |
|
With current traffic exceeding two million page views per week, this forum is getting quite a workout!
|
|
|
|
ForceField (OP)
aka Vitaliy
Sr. Member
Offline
Activity: 386
Merit: 250
|
|
June 29, 2012, 02:55:53 AM |
|
Site was down again at 10:54PM EST. New error message:
"Connection Problems Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later."
|
PC Hardware & Electronics For BTC Traded w/: Kansattica | jduck1987 | shakaru | newdude | nitetrader | midievil | blo8i | mb300sd | juggalodarkclow | Garr255 | Tril | Ringmasta | SysRun | CrazyBlane | sokay | BCB | str4wm4n | PinkBatman | Bitobsessed | matauc12 | antimattercrusader | BryanK
|
|
|
John (John K.)
Global Troll-buster and
Legendary
Offline
Activity: 1288
Merit: 1225
Away on an extended break
|
|
June 29, 2012, 02:57:40 AM |
|
I got another one: Database Error: Query execution was interrupted File: /var/www/bitcoin/smf/Sources/BoardIndex.php Line: 84Database Error: MySQL server has gone away File: /var/www/bitcoin/smf/Sources/Load.php Line: 2040
|
|
|
|
pirateat40
Avast Ye!
Sr. Member
Offline
Activity: 378
Merit: 250
"Yes I am a pirate, 200 years too late."
|
|
June 29, 2012, 03:06:17 AM |
|
From what I've gathered, Maged slipped on a stale hot pocket (pepperoni) and spilled his Malava Novocaine drink all over the back of the server. It just needed to dry out a bit before the system came back up.
Warning! Smoke signals are often mistranslated.
|
|
|
|
theymos
Administrator
Legendary
Offline
Activity: 5180
Merit: 12878
|
|
June 29, 2012, 04:01:13 AM |
|
I have a guess about what caused all of the problems today. While writing watchlist.php today, I ran an SQL query that seemed to really confuse MySQL. It was something like this: select t.ID_TOPIC as ID_TOPIC, t.ID_BOARD as ID_BOARD, t.ID_LAST_MSG, m.subject AS subject from smf_watchlist w LEFT JOIN smf_topics t ON (t.ID_TOPIC = t.ID_TOPIC) LEFT JOIN smf_messages m ON (m.ID_MSG = t.ID_FIRST_MSG) where w.ID_MEMBER = 35; I believe it was the ON (t.ID_TOPIC = t.ID_TOPIC) part that caused problems. (This isn't actually what I wanted to do -- I meant to compare ID_TOPIC in two different tables.) I think this query caused the database to lock up completely and refuse all connections, even after I stopped loading the page which ran this query. Maybe it also created huge temporary files which caused the other problems -- I didn't notice.
|
1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
|
|
|
apetersson
|
|
June 29, 2012, 08:00:18 AM |
|
[01:27] yellowhat theymos: are you sure its not a self-dos due to new addons (maybe badly written) addons? [01:29] yellowhat is the source available? I could review the sql maybe [01:30] yellowhat maybe its doing something dumb as querying without index or anything
/pats myself on back for remote debugging ninja-senses
|
|
|
|
|