Geez another error [Archive]

Dean C

12-17-2002, 09:14 AM

Fatal error: Maximum execution time of 15 seconds exceeded in /www/vbulletin.org/htdocs/forum/search.php on line 416

This meant i couldn't do a search and help a fellow vbhacker find a hack they could not find !

I was devastated

- miSt

Chris M

12-17-2002, 11:31 AM

What were you searching for?:)

Satan

Dean C

12-17-2002, 12:12 PM

*post count* does not *decrease*

Chris M

12-17-2002, 01:21 PM

Hmmm...

I also got the error:confused::(

Try searching without the *'s;)

Satan

Dean C

12-17-2002, 01:59 PM

yea but without the * it produces like 10 pages of irrelevant results

Xenon

12-17-2002, 04:05 PM

i think the timelimit should be increased :)

N9ne

12-17-2002, 04:07 PM

Look in my profile, I have a hack for post counts not decreasing ;)

Dean C

12-17-2002, 06:32 PM

Wtf? lol

Admin

12-18-2002, 02:53 PM

Bug in vBulletin I believe.

Dean C

12-18-2002, 03:17 PM

I see...

Shall i report it or will you?

Chris M

12-20-2002, 08:37 AM

Somebody report it;)

Satan

Sebastian

12-24-2002, 05:45 AM

wow 15 is low.... default value is 30 seconds i believe. I had the same problem on my forums, when I increased it to 45 i no longer got that message O_o

uhm, my message got cut off.. where did the rest go? wow this forum is possessed. it has a mind of its own.

Logician

12-24-2002, 07:43 AM

It may not be a bug but just a query with a very heavy load. If you use wild cards in your search and use very commonly used keywords and especially use multi-keywords in search, it returns so many results from the db that it would take more than 30 seconds to return/process these results for search.php which will result in "Time out" errors.

If you have a large database you can encounter this problem even in "without wildcard" searches. Sometime ago David asked for a hack in request forum which will reduce the load in large db searching and I gave the code there. He had a large database and his searching was returning results in 14 seconds if 2 very commonly used keywords (and without wildcards!) were searched, thus killing server. After the hack is applied, we take it down to 2-3 seconds if I remember correctly. I couldn't find time to release the hack in Full Releases.

However I agree that vb should have a protection mechanism by default to prevent processing of so heavy search jobs as this can be easily exploited by malicous users. So from this point of view I agree that it's a bug. :)