Error on logging on

A

Anon_F

Joined
Jan 14, 2006
Messages
12,268
Reaction score
283
Ian, got this when trying to log on @ 09:47

Fatal error: Maximum execution time of 60 seconds exceeded in C:\Inetpub\vhosts\pcreview.co.uk\httpdocs\Index.php on line 23
 
feckit said:
Ian, got this when trying to log on @ 09:47

Fatal error: Maximum execution time of 60 seconds exceeded in C:\Inetpub\vhosts\pcreview.co.uk\httpdocs\Index.php on line 23
Click to expand...

I've had it too, although not today.
icon11.gif
 
Not had that error today, but it took ages and ages for the PCR home page to load at 10:14 :)
 
Thanks Feckit, I'll look into that now (along with the one Chris posted last week).

I'm doing a bulk delete of spam posts - so I'm guessing it is that slowing the site down. I might need to do it early in the morning instead :thumb:
 
Yep, it was the spam removal that was doing this - I'll restart it tonight before I go to bed :thumb:
 
I'm running the query again now, so the main page will take some time to load (but the rest of the pages should be ok, maybe a little slower).

Sorry about this, but it has to be done to purge all of the old spam posts :)
 
I just knew you were doing something ... :lol:


OK, carry on, I now know for sure ... it ain't me. ;)


:p
 
Ian Cunningham said:
so the main page will take some time to load (but the rest of the pages should be ok, maybe a little slower).
Click to expand...

Exactly what's happening.

Thanks for all your hard work,Ian. :wave:
 
Ian, just got the following message below at about 17:53.

Fatal error: Maximum execution time of 60 seconds exceeded in C:\Inetpub\vhosts\pcreview.co.uk\httpdocs\Index.php on line 75
 
Thanks, I got that here too - a query locked up the database, so I'm seeing what it is now :thumb:
 
Ian, another problem logging on at 09:22 this morning.

Fatal error: Maximum execution time of 60 seconds exceeded in C:\Inetpub\vhosts\pcreview.co.uk\httpdocs\Index.php on line 30
 
Thanks :thumb:

I thought I'd fixed the error but I'll have to get back to the drawing board :wall:
 
I've found 2 possible ways to fix the rogue query :

1) Find and change the bit of code that is doing this

2) Downgrade from MySQL 5 to MySQL 4. This option will work, however it could take a whole day of downtime to do so it's a last resort.

I'll see if I can get option 1 working first :D ;)
 
Hmmm... I don't want to jinx it by saying it's fixed - but... it could be!

I've found the part of the script that was creating massive queries, and it is a feature which is never used anyway - so I've disabled it. Fingers crossed that it does the trick :thumb:
 
Back
Top