Sorry I didn't reply sooner, I was busy with the Marmite.
Anyways, yes, there have been problems coming and going recently. I often click and see the dreaded Internal Server Error message.
So here is where we are at, brought to you by understandable geek-stuff and Marmite.
When you click something in the forum, the software on the web server runs a 'query' on the database.
Basically the forum software has a little conversation with the database as follows: "Hi Mr Database sir, can you please tell me all posts from the table you have called 'posts', but only the ones that belong to the 'Marmite' topic and while you are at it tell me all the names from the table you have called 'members' and correlate them to the posts, oh and one more thing, can I have a Marmite sarnie". The database responds with the info you asked for and then the forum software displays all the Marmitey goodness when I click on the Marmite thread.
Now, sometimes the forum software asks the database a really really complicated question (I haven't worked out what the problematical question is yet, something about a list of topics). Instead of a quick reply from the database, it just sits there thinking about it. This should always be quick, but for some reason it's slow sometimes.
Normally, the database can still listen for new queries while one is taking a long time to run, but in the instances where we have the problem, it's just saying "no, hang on, i'm working on this really complicated question someone asked about Marmite" and then all the new queries have to wait (Locked tables, or blocking, is the technical term)
When this happens and the database has about 30 blocked queries, the forum software gives up and displays the Internal Server Error. Once the database has worked out that long query (The answer was Marmite & Beans on Toast) then all the blocked queries can continue and all is back to normal.
Recently, when I saw the error, I looked on the database and just told the database to stop thinking about Marmite (Actually, I just killed that long-running query, but Marmite is always fun) and then the forum would come back immediately. It turned out, however that doing this seemed to damage the database and it went into self-repair mode which can take up to 3 hours...
So currently, I let these long-running-Marmite-questions run for the 10-20 mins they take
The work we did previously to change the format of the tables was meant to stop this, but it still needs tweaking it seems. We will work it out, but for now, we will be getting these errors
Tom...