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

[Kurt Buff]

Kurt Buff wrote:
> Robert LeBlanc wrote:
> > Kurt Buff wrote:
> > 
> > > Note the first line - I'm betting that instance 77929 is 
> > PID of the job that
> > > launched at 20:00 and hung while trying to find MySQL, 
> > though I can't be
> > > sure because it's not logged in the email. In agreement 
> > with what was noted
> > > previously, MySQL was still running when I rebooted the machine.
> > 
> > Another thought occurred to me.  It's possible that in your 
> > my.cnf file
> > you've got MySQL configured to use a short interactive_timeout value
> > rather than the default, such that it drops the connection if 
> > you go for
> > more than X seconds without receiving a mail item.  If these 
> > "MySQL has
> > gone away" errors are consistently happening in the early 
> > morning hours
> > when traffic levels are lowest, that could account for it.  
> > Take a look
> > at any timeout-related settings in your my.cnf file, and try just
> > commenting those out--let the defaults take a crack at it 
> and see how
> > that works.
> > 
> > - --
> > Robert LeBlanc <rjl at renaissoft.com>
> > Renaissoft, Inc.
> > Maia Mailguard <http://www.maiamailguard.com/>
> 
> An interesting thought. Below is the my.cnf, and the timeout specified
> matched the my-[small|medium|large|huge].cnf examples, though not
> my-huge.cnf, which is 120. Think increasing it to that might 
> be useful?
> 
> [client]
> port            = 3306
> socket          = /tmp/mysql.sock
> [mysqld]
> port            = 3306
> socket          = /tmp/mysql.sock
> skip-locking
> key_buffer = 16M
> max_allowed_packet = 10M
> table_cache = 64
> sort_buffer_size = 512K
> net_buffer_length = 8K
> read_buffer_size = 256K
> read_rnd_buffer_size = 512K
> myisam_sort_buffer_size = 8M
> skip-networking
> log-bin=mysql-bin
> server-id = 1
> innodb_data_home_dir = /var/db/mysql/
> innodb_data_file_path = ibdata1:10M:autoextend
> innodb_log_group_home_dir = /var/db/mysql/
> innodb_log_arch_dir = /var/db/mysql/
> innodb_buffer_pool_size = 128M
> innodb_additional_mem_pool_size = 2M
> innodb_log_file_size = 32M
> innodb_log_buffer_size = 8M
> innodb_flush_log_at_trx_commit = 1
> innodb_lock_wait_timeout = 50
> [mysqldump]
> quick
> max_allowed_packet = 16M
> [mysql]
> no-auto-rehash
> [isamchk]
> key_buffer = 20M
> sort_buffer_size = 20M
> read_buffer = 2M
> write_buffer = 2M
> [myisamchk]
> key_buffer = 20M
> sort_buffer_size = 20M
> read_buffer = 2M
> write_buffer = 2M
> [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?

Kurt