hey guys, how do solve a problem that has to do with max_question resource?

dunno, maybe someone might tell you if you provide more details as to what exactly your problem is or what exactly it is you want to know :S be specific and give as much info as possible..

I have a SQL database max_questions resource problem also. So, I will try to give as much info as possible.

My site regularly goes down and leads to a blank page. I first noticed this when I was making a lot of changes to the site and uploading lots of database tables. Apparently, my web host limits the number of database queries over some unknown time frame to 50000. Sometimes the site will go down for just a few minutes, and other times for up to one hour when this limit has been reached. The error max_questions error shows up when the site is down and I log into phpMyAdmin. The databases that normally show up, do not, and an SQL error message shows up indicating that the max_questions limit of 50K has been reached. The webhost told me that this will always reset within an hour.

This first showed up as only a problem when I was doing extensive upgrading of modules or database tables and running a lot of queries. But now the problem shows up repeatedly and on a daily basis even when no extensive database changes or site development is happening. My site has recently been receiving more user and robot activity, but it is still very low traffic on average, receiving a max of 3000 unique visits a day. Hits on on the order of 100K per day. Still, I feel either the limit of 50K queries is low, or for some reason XOOPS is running a lot of database activity upon page loading that may not be necessary.

Thoughts?

I was helping a friend with the same problem (max_questions limit hit). He's using phpnuke, not XOOPS.

I added some code to log all the database queries, along with the IP address and user agent.

It turned out that the bulk of the hits were from Google's bot: HTTP_USER_AGENT = Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html).

Quote:

Yeah. I found out the same problem with my site. I receive more google hits than any other visitors. So I disabled many modules in the robot.txt file in the root directory and now my site seems work a lot better.

yes. i too have a lot of google hits. I also found in other threads here that it helps to optimize the use of module and block caching. my site did not have any caching on blocks or modules. So, I configured those appropriately and am going to see if this helps.

I received the following message from my web host in regard to this proglem:

Quote:

Can anyone help me understand what is meant by the script not closing the connection after a request is made and the connection this has to exceeding the limit? I'm a bit unclear on that. Also, does this make sense for XOOPS?

Anyone? Does the above quote mean that XOOPS leaves the database connections open so that they eventually add up to 50K and crash the system? Is this true? Is this configurable? And, if so, how? It's very irritating to have the site crash on such a regular basis. I'd love to blame my webhost completely, but something tells me there's more to this story. . .

Unless you have persistent connections enabled, the connection gets closed automatically.

A "question" is a query. So that error means you're getting 50000 database queries within the specified time period.

The only way I know to troubleshoot it is to add some code to log all the queries, along with some identifying information (e.g., timestamp, IP address, user agent). Then you would be able to tell whether some particular visitor, such as a robot, is causing the problem, or whether it's just that your site is very busy due to normal traffic.

The problem might be lessened by enabling caching for, or not using, various blocks or modules.

Here's a hack you can use to log the afrementioned information.

You'll need to change $logdir to specify the path to a writable directory for the log files. This directory should be protected from viewing from a web browser.

A new log file is created each hour. The log files may take up a lot of disk space, so watch out for that.

class/database/mysqldatabase.php (function XoopsMySQLDatabase::queryF)

thanks! i'll give it a shot.