exceeded max_questions resource ?

[DonnaNJ]

has exceeded the 'max_questions' resource (current value: 50000)

 

select configuration_key as cfgKey, configuration_value as cfgValue from configuration

 

 

What the heck is this ? Our store has been running for months - and this passed week maybe we haven't kept up with processing orders die to holiday (we put up a notice)..

 

What does this mean and how can we fix it ?

 

Donna

[Guest]

There are a few threads on this, as well as an article in the knowledgebase, but the skinny is this:

 

Shared hosting requires that the web hosting company keep their users from taking up too many resources at the expense of other users. One way to do this is to limit the number of mysql queries that can be in progress at any given time. This error message means that you've exceeded your allocation for the next several minutes. When you see this in Admin, your customers will see it too on the catalog side.

 

Talk to your host about it.

 

-jared

[lickity40]

There are a few threads on this, as well as an article in the knowledgebase, but the skinny is this:

 

Shared hosting requires that the web hosting company keep their users from taking up too many resources at the expense of other users. One way to do this is to limit the number of mysql queries that can be in progress at any given time. This error message means that you've exceeded your allocation for the next several minutes. When you see this in Admin, your customers will see it too on the catalog side.

 

Talk to your host about it.

 

-jared

 

Jared...nice answer but not a solution really. In my case, the ISP, (iPowerweb), says to talk to osCommerce about it. Funny thing is, this is a product that my ISP has available as a power app. To me, 50,000 requests in an hour doesn't really sound like an unreasonable limitation. I've checked my logs though and there isn't that much activity to generate this many requests. Is it not possible that the indexing in the SQL database is not normalized effeciently or some other issue with the coding?

 

Rick Forsythe

[boxtel]

Jared...nice answer but not a solution really. In my case, the ISP, (iPowerweb), says to talk to osCommerce about it. Funny thing is, this is a product that my ISP has available as a power app. To me, 50,000 requests in an hour doesn't really sound like an unreasonable limitation. I've checked my logs though and there isn't that much activity to generate this many requests. Is it not possible that the indexing in the SQL database is not normalized effeciently or some other issue with the coding?

 

Rick Forsythe

 

well, it has nothing to do with indexing but yes, limiting your database access would ofcourse help.

 

So category counts and things like that will do the necessary damage -> optimize

[ozcsys]

Jared...nice answer but not a solution really. In my case, the ISP, (iPowerweb), says to talk to osCommerce about it. Funny thing is, this is a product that my ISP has available as a power app. To me, 50,000 requests in an hour doesn't really sound like an unreasonable limitation. I've checked my logs though and there isn't that much activity to generate this many requests. Is it not possible that the indexing in the SQL database is not normalized effeciently or some other issue with the coding?

 

Rick Forsythe

 

 

It may or may not be just your store that is the problem. I know on at least some of the godaddy hosting that they set server limits for database requests and once that is reached than all sites on that particular server are down until the limits are reset.

 

If it is just your site than you may want to checkout a couple of the contributions that can decrease your database requests and lower the overhead.

[lickity40]

well, it has nothing to do with indexing but yes, limiting your database access would ofcourse help.

 

So category counts and things like that will do the necessary damage -> optimize

 

Forgive my shade of green here, but I understand that 'limiting access' would be a solution. That's pretty obvious by the error message. Not having an online store is a solution too. What I'm trying to get at here is how can I limit the accesses from within the program.

 

From the number of orders placed and the logs showing number of visitors and what they are doing, there is no way in hell that they are making 50,000, (the sql limit), requests to the db in one hour.

 

So....either the server is somehow not resetting the connections and the requests are allowed to accumulate to the 50,000 limit, (which the ISP denies being the problem), or, (and according to them), the coding of this program is written in such a way that the connections aren't resetting.

 

Puzzled.

[lickity40]

It may or may not be just your store that is the problem. I know on at least some of the godaddy hosting that they set server limits for database requests and once that is reached than all sites on that particular server are down until the limits are reset.

 

If it is just your site than you may want to checkout a couple of the contributions that can decrease your database requests and lower the overhead.

 

I'll give you a dollar if you give me a hint as to what these contributions are. :rolleyes:

[Guest]

Rick:

 

1) Make sure that your configure.php files have persistent connections set to off. This way, each time the php script finishes executing, the connection will be terminated (supposed to, anyway).

2) page cache contribution. page optimization thread. turn off category counts in the osC config.

 

-jared