[Maia-users] web pages hang on maia, forced to reboot server. ..

[Kurt Buff]

Robert LeBlanc wrote:
> Kurt Buff wrote:
> 
> >> [mysqlhotcopy]
> >> interactive-timeout
> > 
> > Sorry to reply to myself. Blindness on my part. The entry
> > interactive-timeout doesn't have a parameter in any of the 
> my-*.cnf example
> > files, nor in mine. The question remains, then, will it 
> hurt to increase
> > innodb_lock_wait_timeout?
> 
> First, try commenting out the "interactive-timeout" line to let MySQL
> use its default value for that setting.  Also check the command-line
> arguments you're using to start MySQL, since some of those 
> may override
> the settings in your my.cnf file.

Have done.

> If all else fails, consider adding a couple of timeout values 
> explicitly
> to the [mysqld] section of your my.cnf file:
> 
>  interactive_timeout = 86400
>  wait_timeout = 86400
> 
> The default for both of these values is 28800 seconds (8 hours), but
> increasing this to 86400 (24 hours) might give you more insurance
> against slow periods.  Remember to restart mysqld after 
> changes to your
> my.cnf file.

I'll wait for a while to see if commenting out interactive-timeout cures it,
but this seems a bit unlikely. Why I say this is because we receive mail for
3 offices, one in the US, one in the UK and one in AU, and we receive
between 300 and 500 emails each day, from midnight to each day.

> As for innodb_lock_wait_timeout, that's not likely to be the 
> problem in
> this case.  That's a setting that's more likely to come into play when
> the server is /busy/, whereas I suspect your disconnections are
> occurring when the server is /idle/.

Ah. 

Good enough. I've put in the mod, we'll wait to see if it helps.

Thanks

Kurt