Oh no! Not now!

Bugs
3

Right in the middle of NaNoWriMo, the server got the hiccups.

First, the blogs stopped responding. Then the main site went down. I did what any stressed dev might do and restarted the server.

Bad mistake!

The MySQL server refused to come back up. Just totally refused.

After some time I found an error log file that had gotten a bit big. I removed it but the server still reported a file space problem.

What?

dev in painOkay, stay calm.

I will not panic, I will not panic…

PANIC!!!!

It turns out that sometimes you also need to restart services that were using the file so they give the space back. I’m sure there is a good reason for that but… Right now I am no fan of that feature. Actually, that’snot true. I know exactly why things work like that and it is a really good design. It comes up so infrequently that I had forgotten about it.

Anyway panic over I restarted the database and everything was fine, right?

No of course not.

One of the blogs – my blog – had a corrupted table and so was still acting like it was down.

I tried not to headbutt my nice new desk and ran the table repair. MySQL has this “magical” ability to fix itself if you “ask really nicely”.

Panic over…

Note to self, get with migrating your older stuff that makes big log files to something a bit less aggressive.

The image used for this post was first used by one of our bloggers. It seemed apt.

Not sure what your hosting platform is, but don’t the log files get recycled? (not sure what the technical term is). Normally log files would be gzipped after a period of time, or when they reach a certain size, only a limited number would be kept.

You are right Danny. Log Rotate would have eventually taken care of the problem. Not logging a lot of nonsense was just more efficient. It was pretty much just an edge case mistake on my part.

3 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

train crash
Bugs
All fixed now

There was a problem but we are all fixed now. I’m going to duck away again and hope nobody saw that downtime.  If you did, then please rest assured that our hosts have taken care of the issue and there should not be a repeat of the problem. Pictured: All …

train crash
Bugs
2
Sites outage – confession of a silly dev

Hands up here, the outage of all sites was my fault. If you are interested, this post will look at what went wrong and how it was fixed. How the outage happened Author Buzz is set up on a secure dedicated server. The domains are registered with a trustworthy registrar …

train crash
Bugs
2
Tiny MCE and BBPress bug

I guess I spoke too soon. The update seems to have had a very strange side effect – BBPress’ WYSIWYG editor has stopped working. I noticed a bug report from one of our members this evening. They were reporting that the forums were being squiffy. I was going to reply …

%d bloggers like this:
Skip to toolbar