mysql is down when remote telnet to 3306.

Hello, all.

When I direct telnet to mysql port to 3306 like this,

How-To-Repeat: telnet remote.mysql.server 3306
the remote.mysql.server is configured to permit remote connection.

Surely, only local connection allowed mysql would be like this
(this has no problem)

Trying 192.168.3.4...
Connected to 192.168.3.4.
Escape character is '^]'.
EHost '192.168.1.2' is not allowed to connect to this MySQL
serverConnection closed by foreign host.


But remote connection allowed mysql service is restarted or down.

[root@www bin]# ./mysql.server start
[root@www bin]# Starting mysqld daemon with databases from
/usr/local/mysql/var
and telnet to mysql port at this server the messages are below.

[root@www bin]# /usr/local/mysql/bin/safe_mysqld: line 273: 11340
Segmentation fault $NOHUP_NICENESS $ledir/$MYSQLD $defaults
--basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION
--pid-file=$pid_file --skip-locking >>$err_log 2>&1

Number of processes running now: 1
mysqld process hanging, pid 11343 - killed
021104 17:56:10 mysqld restarted

But when I execute mysql daemon with mysql user, the mysql daemon is down,
but when I execute mysql daemon with root, the mysql daemon is restarted
like above.

Is this a mysql related bug or not?
my mysql version is ./mysql Ver 11.18 Distrib 3.23.52, for pc-linux-gnu
(i686)

some other latest mysql version has same problem.


Thanks in advance.



____________________________________________________________ _____
MSN Messenger¸¦ ÅëÇØ ¿Â¶óÀÎ»ó¿¡ Àִ ģ±¸¿Í ´ëÈ­¸¦ ³ª´©¼¼¿ä.
http://messenger.msn.co.kr


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12906@lists.mysql.com
To unsubscribe, e-mail

Re: mysql is down when remote telnet to 3306.

Hello,
On Thu, 2002-11-07 at 03:05, SB CH wrote:
>
>
> Hello, all.
>
> When I direct telnet to mysql port to 3306 like this,
>
> How-To-Repeat: telnet remote.mysql.server 3306
> the remote.mysql.server is configured to permit remote connection.
>
> Surely, only local connection allowed mysql would be like this
> (this has no problem)
>
> Trying 192.168.3.4...
> Connected to 192.168.3.4.
> Escape character is '^]'.
> EHost '192.168.1.2' is not allowed to connect to this MySQL
> serverConnection closed by foreign host.
>
>
> But remote connection allowed mysql service is restarted or down.
>

Looks like known problem with RedHat 8.0 glibc. Is it your case?
If so temporary workaround is to run nscd for a while ...
at least we have reports that problem dissapears after that.

If you are not with RH8.0 please let us know and provide more information
about your system.


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12908@lists.mysql.com
To unsubscribe, e-mail

Re: mysql is down when remote telnet to 3306.

On Thu, 2002-11-07 at 03:05, SB CH wrote:
> Hello, all.
>
> When I direct telnet to mysql port to 3306 like this,
>
> How-To-Repeat: telnet remote.mysql.server 3306
> the remote.mysql.server is configured to permit remote connection.
>
> Surely, only local connection allowed mysql would be like this
> (this has no problem)
>
> Trying 192.168.3.4...
> Connected to 192.168.3.4.
> Escape character is '^]'.
> EHost '192.168.1.2' is not allowed to connect to this MySQL
> serverConnection closed by foreign host.
>
>
> But remote connection allowed mysql service is restarted or down.
>

We ran across this as well and finally solved it in such a way that
leads us to believe that the problem is that the MySQL code assumes that
the IP trying to connect can always be resolved. We think this because
the action was repeatable until we included an entry for the remote IP
in /etc/hosts. Once this was done, the mysql service no longer
restarted.

Something of note, when we ran safe_mysqld from the command line, rather
than as a service, a SEGFAULT message would show up when trying to
connect. (We haven't tested this again since adding the hostname to the
/etc/hosts table, so I can't say if it still SEGFAULTs).




------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12911@lists.mysql.com
To unsubscribe, e-mail

Re: mysql is down when remote telnet to 3306.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On November 7, 2002 18:51, Richard Duran wrote:
> We ran across this as well and finally solved it in such a way that
> leads us to believe that the problem is that the MySQL code assumes tha=
t
> the IP trying to connect can always be resolved. We think this because
> the action was repeatable until we included an entry for the remote IP
> in /etc/hosts. Once this was done, the mysql service no longer
> restarted.
>
> Something of note, when we ran safe_mysqld from the command line, rathe=
r
> than as a service, a SEGFAULT message would show up when trying to
> connect. (We haven't tested this again since adding the hostname to the
> /etc/hosts table, so I can't say if it still SEGFAULTs).

I remember reading somewhere you can prevent MySQL from trying to resolve=
the=20
client IP by adding the "skip-name-resolve" directive to the [mysqld] sec=
tion=20
of /etc/my.cnf

Alexander Keremidarski mentionned earlier that this was likely due to a=20
problem with RH8.0 glibc. Note that this is not 8.0-specific and that RH=20
released updated glibc packages yesterday:

https://rhn.redhat.com/errata/RHSA-2002-197.html

Hope this helps,

- - Matt
- --=20
+----------------------------------------------------------- -+
| Mathieu Mourez mailto:matt@securebuxx.com |
| SecureBuxx workphone:800.337.0675 |
| Senior System Administrator cellphone:514.996.9626 |
| PGP: C150 2E23 64F4 7396 EF24 19E9 7855 50ED 2691 6BFB |

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE9y0LreFVQ7SaRa/sRAg79AJ43GCDhMoIoEuyK2cMT/Jvdw2uXhACf cRzt
Sc4L06UDpGD4XMnnGhcfE3Q=3D
=3D7gJs
-----END PGP SIGNATURE-----


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12913@lists.mysql.com
To unsubscribe, e-mail

Re: mysql is down when remote telnet to 3306.

On Thu, 2002-11-07 at 22:51, Mathieu Mourez wrote:
> I remember reading somewhere you can prevent MySQL from trying to resolve the
> client IP by adding the "skip-name-resolve" directive to the [mysqld] section
> of /etc/my.cnf
>
> Alexander Keremidarski mentionned earlier that this was likely due to a
> problem with RH8.0 glibc. Note that this is not 8.0-specific and that RH
> released updated glibc packages yesterday:
>
> https://rhn.redhat.com/errata/RHSA-2002-197.html
>
> Hope this helps,
>
> - - Matt

I recall running across "skip-name-resolve" on the man page and suspected that
it might help with the problem (Thanks for confirming it for me). I probably
would have ended up going with that anyway (if not for the glibc patch,
thanks again), but I thought I'd mention it anyway, feeling that there
was a bug that needed to be fixed.

Regards,
-richard


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12920@lists.mysql.com
To unsubscribe, e-mail