Re: MYSQL Issues.

[Nico Meijer <lists_(_at_)_familiemeijer_(_dot_)_org>]

Hi Otto,

> This has come up a lot of times already.

Got bitten myself, not too long ago... ;-)

> Starting mysqld_safe with the 
> option --open-files=1000 (and making sure it is started by rc.local, 
> so  the process gets the daemon login class with a higher nofiles 
> limit) fixes  the problem.

Wouldn't this cause trouble when started from the command line? Say 
`sudo mysqld_safe &`?

Personally, I went this route:

/etc/my.cnf:
[mysqld]
set-variable = max_allowed_packet=64M
set-variable = max_connections=1000
[mysqld-safe]
open-files = 2048

The specific fix for this issue is indeed the open-files limit, as you 
state. The other settings are just my own preferences.

Addition to /etc/login.conf:
mysql:\
        :datasize=infinity:\
        :maxproc=infinity:\
        :openfiles-cur=2048:\
        :openfiles-max=8192:\
        :stacksize-cur=16M:\
        :localcipher=blowfish,8:\
        :tc=default:

Note: the "datasize=infinity" will be lowered soon, but first I'd have 
to get decent stability results. Since I applied this 'fix' just two 
weeks ago (with a reboot![1]), I'd hate to speak of total stability just 
yet. ;-) The mysqld process sits steadily at 96Mb, which makes me happy. 
Previously, mysqld hung at 68M. This meant I couldn't make a full 
database backup.

[1] There seems to be some 'debate' whether or not the reboot is needed 
after modifying login.conf. I couldn't find any reference to it in 
login.conf(5) - perhaps need to reread - but my problems were fixed once 
I rebooted. Note the "my" and "I".

> There's no need to go back to an older version of MySQL.

Very true.

Thanks... Nico