max_allowed_packet and wait_timeout on shared servers

[AdrianB]

I started to get a lot of "MySQL server has gone away" on a Drupal installation on my shared server.

It seems to boil down to the settings for max_allowed_packet and wait_timeout in MySQL (I think - since I can't change the settings I can't test it).

These are the settings on my shared server:
max_allowed_packet is 1M
wait_timeout is 20 seconds

These are very low numbers. Since I'm on shared I can't change then (afaik). Would it be possible for JaguarPC to change these values to something more reasonable?

[Connie]

I ;think you need to open a ticket in the client area. https://secure.jaguarpc.com/clients/

[AdrianB]

I just wanted to know if it was something that could be considered at all. If the answer is "No, we don't adjust those settings." then I wouldn't need to bother support about it.

I also wanted a discussion about what numbers are reasonable.

[Vin DSL]

These are very low numbers. Since I'm on shared I can't change then (afaik). Would it be possible for JaguarPC to change these values to something more reasonable?

I just wanted to know if it was something that could be considered at all. If the answer is "No, we don't adjust those settings." then I wouldn't need to bother support about it.

Hrm... well...

You've been here almost as long as me - it just took you a little longer to crash the sql server.

I've had this problem in the past, and Tech Support has increased my quota (when necessary). Ultimately, I've had to eventually upgrade to a more appropriate hosting package... but they were perfectly willing to work with me on silly sh!t like this.

It's no big deal, really, on THEIR end... but it will require the authorisation of a Senior Tech, sooo...

I would contact Masood (if he's still around)... Rizwan.Z ... or one of the other muckety-mucks, and explain the situation!

They tend to be very flexible here, if you have a reasonable request...

JagPC bends over backwards for their clients, but you undoubtedly know that by now!

[AdrianB]

Hrm... well...

You've been here almost as long as me - it just took you a little longer to crash the sql server.

Actually this was just a test installation with no load at all, but some cron actions from Drupal seems to hit the ceiling. Drupal could probably be better optimized, but from what I've read these numbers seems unusually low even for shared hosting.

They tend to be very flexible here, if you have a reasonable request...

JagPC bends over backwards for their clients, but you undoubtedly know that by now!

Yeah, especially if you can get past the first tier of support and reach those, like Masood, that you can actually communicate with.

[JPC-Jawad]

I started to get a lot of "MySQL server has gone away" on a Drupal installation on my shared server.

It seems to boil down to the settings for max_allowed_packet and wait_timeout in MySQL (I think - since I can't change the settings I can't test it).

These are the settings on my shared server:
max_allowed_packet is 1M
wait_timeout is 20 seconds

These are very low numbers. Since I'm on shared I can't change then (afaik). Would it be possible for JaguarPC to change these values to something more reasonable?

Please open a support ticket so that we can assist you regarding this.

[JPC-Sreejith]

Your ticket has already been updated.Please check last reply below.

============
If you would like we can move your account to one of the newer servers which do not give any issue with Midnight commander.
============

[AdrianB]

Your ticket has already been updated.Please check last reply below.

Was that answer addressed to me? I haven't even opened a ticket about it

[JPC-Awais]

AdrianB, The last reply from Tech Sreejith was for user Layenue09.

[Gwaihir]

I don't know about your site, but mine is still on MySQL 4.1 series here. In MySQL <5, you can make this setting yourself from the PHP code. I found a tidbit about it on Drupal's own site.