Mysql Access

[stb74]

At the moment joomla can't access its databases.

I have checked other sites and they are the same.

[paul_r]

Saw that - some MySQL error as the html sites were ok. Rebooted the server and it's fine again.

[paul_r]

There was another problem with the server for a short time last night. Seems there was a Perl script running on one of the sites (can't tell which one) that got tied in a knot and locked up the server. A restart seems to have cleared it ok but if you see any other problems let me know, in case we have a faulty script in a site somewhere causing a problem.

[Castle Utd Sec]

My site can't access php stuff on its Forum.

phpBB: Critical Error

Could not connect to the database

http://www.castleunitedfc.com/_mgxroot/page_10813.html

www.castleunitedfc.com (http://www.castleunitedfc.com)

Incase its related to all this.

[stb74]

Database access is not working

[paul_r]

MySQL fell over this morning. Back up again just after 09:00.

They're having a look at log files to see if they can see what caused it, as this happened on Saturday too.

[paul_r]

These problems are all related and we now know what's caused them, but we could do with some help from one of you.

In basic terms (cos some of it's over my head) ...

One of the sites (can't identify which one) has a Perl script running on it. This script appears to have some iffy code that isn't closing a loop somewhere. So it's going exponential and filling the memory. Once that happens the server chokes and either locks up (as it did on the second event on Saturday) or coughs out MySQL in a bid to free up some memory (what happened on Saturday first time, then again this morning).

We can deal with this for now by doing an automatic reboot of the server every morning at 08:00 to flush it out but obviously the proper solution is to find the crappy Perl script.

'What's a Perl script?' I hear you ask. I doubt any of you are knowingly running or writing Perl scripts so this is very likely to be in one of the free applications that can be installed using Installatron. Some of those free applications are probably quite out of date now, and not necessarily updated or supported by their author. We think maybe some of you habve installed one of these, or maybe some other free application you found on the web, and this is causing the problem.

So ... as this problem first came up last Saturday, then again today, I'm guessing we're looking for a new application that was installed sometime last week. If we can identify possible suspects I can have someone try to fix the loop in the script, or we'll have to disable it.

Anyone been working on their site in the last couple of weeks and installed something new? It's not a problem and no need for embarassment as it's not that anyone has done anything wrong, but we could do with sorting this.

Thanks