Bug #45913 mysqld restarts signal 11 connecting host forward and reverse dns records differ
Submitted: 2 Jul 2009 13:42 Modified: 20 Aug 2009 8:36
Reporter: vbooh vbooh Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:4.1.22; 5.0.83 OS:FreeBSD (6.3)
Assigned to: CPU Architecture:Any
Tags: hosts.allow signal 11 forward revers dns records

[2 Jul 2009 13:42] vbooh vbooh
System: FreeBSD 6.3-RELEASE
MySQLd versions: 4.1.22; 5.0.83

MySQLd restarts with signal 11 with this message in log:
090630 11:51:01 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1286144 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

090630 11:51:01  mysqld restarted
090630 11:51:01 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
090630 11:51:01 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090630 11:51:01  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090630 11:51:02  InnoDB: Started; log sequence number 0 3525634607
090630 11:51:02 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.0.83'  socket: '/tmp/mysql.sock'  port: 3306  FreeBSD port: mysql-server-5.0.83

In /var/log/messages:
Jul  2 17:25:30 hostname mysqld[33751]: warning: /etc/hosts.allow, line 18: can't verify hostname: getaddrinfo(REVERSE_DNS_RECORD, AF_INET) failed
Jul  2 17:25:30 hostname mysqld[33762]: refused connect from IP_ADDRESS

In /etc/hosts.allow:
# hosts.allow access control file for "tcp wrapped" applications.
# $FreeBSD: src/etc/hosts.allow,v 2007/01/20 02:19:57 csjp Exp $
# NOTE: The hosts.deny file is deprecated.
#       Place both 'allow' and 'deny' rules in the hosts.allow file.
#	See hosts_options(5) for the format of this file.
#	hosts_access(5) no longer fully applies.
# from working, so remove it when you need protection).
# The rules here work on a "First match wins" basis.

# Protect against simple DNS spoofing attacks by checking that the
# forward and reverse records for the remote host match. If a mismatch
# occurs, access is denied, and any positive ident response within
# 20 seconds is logged. No protection is afforded against DNS poisoning,
# IP spoofing or more complicated attacks. Hosts with no reverse DNS
# pass this rule.
ALL : PARANOID : RFC931 20 : deny

# Allow anything from localhost.  Note that an IP address (not a host
# name) *MUST* be specified for rpcbind(8).
ALL : localhost : allow

MySQL is started in standalone mode.

How to repeat:
Try to connect to mysqld via network from host, that have different forward and reverse dns records, and in hosts.allow must be rule "ALL : PARANOID : RFC931 20 : deny" and this rule must work for connecting host.
[20 Jul 2009 8:36] Susanne Ebrecht
Many thanks for writing a bug report. I think this once was fixed in MySQL 5.1.

Please try MySQL 5.1 and let us know if this still exist.
[20 Aug 2009 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".