Hi,

I've got an odd setup that I need to diagnose. The customer won't
allow us to upgrade very far with the OS or MySQL.

Its currently on a BSD/OS 4.0.1 system, and 4.2 is the highest we
could possibly be allowed to go.

We have upgraded to mysql-3.23.58 (Customer won't let us go to
4 or 5), with the following patches from the RedHat distro:

mysql-3.23.58-config.patch mysql-3.23.58-setpermission.patch
mysql-3.23.58-dropdb.patch mysql-3.23.58-symlink.patch
mysql-3.23.58-hotcopy.patch mysql-3.23.58-typo.patch
mysql-3.23.58-security.patch


The configure is just "./configure --with-libwrap". (We do have to
go in to client/Makefile, mysys/Makefile and sql/Makefile to take the
-fno-exceptions out otherwise it won't compile)

With the recent reports of an issue with MySQL we've been getting
alot of probes against the server. Its currently set to only allow connections
from a monitoring machine, and locally. It appears that after a while the
server starts to get QUITE slow... Requests take over a minute, even using
the local socket. Until we do a "flush-hosts", it runs quite slow.

Has anyone heard/seen/experienced this? On some other customer
servers, we just had to put "mysqld: ALL" into /etc/hosts.allow to
prevent the database from becoming unusable.

Thanks, Tuc/TTSG Internet Services, Inc.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql [at] m.gmane.org

Hello.



On some systems tcpwrapper works with MySQL not that well as expected. For

example see:

http://bugs.mysql.com/bug.php?id=5652



And some bugs aren't fixed in old 3.23.xx versions. In my opinion, your problem

is related to DNS. You may disable DNS lookups by starting mysqld with the

--skip-name-resolve option. However, in this case, you can only use IP numbers

in the MySQL grant tables. See:

http://dev.mysql.com/doc/mysql/en/dns.html





Tuc <tuc [at] ttsg.com> wrote:

> Hi,

>

> I've got an odd setup that I need to diagnose. The customer won't

> allow us to upgrade very far with the OS or MySQL.

>

> Its currently on a BSD/OS 4.0.1 system, and 4.2 is the highest we

> could possibly be allowed to go.

>

> We have upgraded to mysql-3.23.58 (Customer won't let us go to

> 4 or 5), with the following patches from the RedHat distro:

>

> mysql-3.23.58-config.patch mysql-3.23.58-setpermission.patch

> mysql-3.23.58-dropdb.patch mysql-3.23.58-symlink.patch

> mysql-3.23.58-hotcopy.patch mysql-3.23.58-typo.patch

> mysql-3.23.58-security.patch

>

>

> The configure is just "./configure --with-libwrap". (We do have to

> go in to client/Makefile, mysys/Makefile and sql/Makefile to take the

> -fno-exceptions out otherwise it won't compile)

>

> With the recent reports of an issue with MySQL we've been getting

> alot of probes against the server. Its currently set to only allow connections

> from a monitoring machine, and locally. It appears that after a while the

> server starts to get QUITE slow... Requests take over a minute, even using

> the local socket. Until we do a "flush-hosts", it runs quite slow.

>

> Has anyone heard/seen/experienced this? On some other customer

> servers, we just had to put "mysqld: ALL" into /etc/hosts.allow to

> prevent the database from becoming unusable.

>

> Thanks, Tuc/TTSG Internet Services, Inc.

>



--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko [at] ensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql [at] m.gmane.org