Mailbox and logger not starting - SLES9 M3 Beta436

[echristi]

logger_mysql_bind_address = localhost
logger_mysql_data_directory = ${zimbra_home}/logger/db/data
logger_mysql_directory = ${zimbra_home}/logger/mysql
logger_mysql_mycnf = ${zimbra_home}/conf/my.logger.cnf
logger_mysql_pidfile = ${zimbra_home}/logger/db/mysql.pid
logger_mysql_port = 7307
logger_mysql_socket = ${zimbra_home}/logger/db/mysql.sock
mysql_bind_address = localhost
mysql_data_directory = ${zimbra_db_directory}/data
mysql_directory = ${zimbra_home}/mysql
mysql_innodb_log_buffer_size = 8388608
mysql_innodb_log_file_size = 104857600
mysql_logger_root_password = *
mysql_memory_percent = 40
mysql_mycnf = ${zimbra_home}/conf/my.cnf
mysql_pidfile = ${zimbra_db_directory}/mysql.pid
mysql_port = 7306
mysql_read_buffer_size = 1048576
mysql_root_password = *
mysql_socket = ${zimbra_db_directory}/mysql.sock
mysql_sort_buffer_size = 1048576
mysql_table_cache = 500
zimbra_logger_mysql_password = *
zimbra_mysql_connector_maxActive = 10
zimbra_mysql_password = *
zimbra_mysql_user = zimbra

To access the database, I did the following
su - zimbra
mysql
show databases

I could see the mysql, test, and zimbra databases. (and also select things out of the tables contained within)

[marcmac]

That's strange, that you can connect to sql from the command line, but tomcat can't find it.

What do you get from:
su - zimbra
mysqladmin status

Also
host localhost

What's in your /etc/hosts file?

Are you running a firewall?

Does
telnet localhost 7306
connect?

[echristi]

Originally Posted by marcmac

That's strange, that you can connect to sql from the command line, but tomcat can't find it.

What do you get from:
su - zimbra
mysqladmin status

>Uptime: 8536 Threads: 1 Questions: 250 Slow queries: 5 Opens: 33 Flush tables: 1 Open tables: 22 Queries per second avg: 0.029


Also
host localhost

>localhost.mtghouse.com has address 127.0.0.1

What's in your /etc/hosts file?

>127.0.0.1 localhost
>
># special IPv6 addresses
>::1 localhost ipv6-localhost ipv6-loopback
>
>fe00::0 ipv6-localnet
>
>ff00::0 ipv6-mcastprefix
>ff02::1 ipv6-allnodes
>ff02::2 ipv6-allrouters
>ff02::3 ipv6-allhosts
>192.168.1.150 zimbra.mtghouse.com zimbra


Are you running a firewall?

>no

Does
telnet localhost 7306
connect?

>telnet: connect to address 127.0.0.1: Connection refused
>Trying ::1...
>telnet: connect to address ::1: Connection refused

[echristi]

sorry, my responses are inline next to the ">" character

[marcmac]

Originally Posted by echristi

>telnet: connect to address 127.0.0.1: Connection refused
>Trying ::1...
>telnet: connect to address ::1: Connection refused

That's the problem right there. THe mysql command is going through the local socket, but tomcat is trying to hit mysqld on the network port.

That's from
telnet localhost 7306
right? (Not telnet 127.0.0.1 7306)

Does
telnet 127.0.0.1 7306
connect?

What do you get from (as root):
iptables -t nat -L
iptables -L

[echristi]

zimbra:/usr/bin # telnet localhost 7306
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying ::1...
telnet: connect to address ::1: Connection refused
zimbra:/usr/bin # telnet 127.0.0.1 7306
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
zimbra:/usr/bin # iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
zimbra:/usr/bin # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

[marcmac]

Just to verify - you said mysql is running, right?

Can you post the contents of /opt/zimbra/conf/my.cnf?

[echristi]

I got it working.

It was due to making the change for
#skip-networking

When I removed this and re-initialized the db and ran zmmyinit, it worked! (my logger isn't starting still though)

[JohnPeacock]

Just to follow up on this thread with a potential solution. It appears that mysql's resolveip is fragile (to the point of returning an answer 1 time out of 5) and it is not easy to get the --force option in the right place for mysql_install_db. The correct fix for the Zimbra project (IMHO) is to use Unix Domain Sockets exclusively, but that needs to be corrected in Tomcat as well (my earlier suggestion to remove the networking support from my.cnf does not work).

I wound up as one of the earlier posters suggested and commented out the call to zmmyinit and hardcoded the appropriate IP address in my.cnf, then changed mysql/scripts/mysql_install_db to assume --force was passed in. It's incredibly hacky, but I don't think there is another way around it. I have no idea why this only affects SLES 9 (possibly having to do with the dual CPU's).

John

[yusufu]

I ran "telnet 127.0.0.1 7306" and this is what I got:
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
Too many connectionsConnection closed by foreign host.