Mailbox and logger not starting - SLES9 M3 Beta436

[chaas]

Originally Posted by DanielP

SE-linux is not enabled.

I had a problem on my smp-server, too. Try to boot for installation with 'failsafe', this worked for me on sles9 + sp2. After installation, zimbra run with the default kernel.

hth

cu chris

[DanielP]

Hi,

Well, i dont belive that it was a kernel issue(the previous beta wen just fine). Anyway, i ended up doing some serious cleaning using grep -r , locate, lsof|grep zimbra etc and made really sure all updates where on, rebooted, installed and everything worked as a charm. The machine seems to be happily running M3_381 right now. Something must have been left from the previous installation, or the machine got problem since i switched IP prior to removing the old installation, and installing the new one.

Thanks for the tip tough.

/Daniel

[prosenbl]

I'm experiencing this exact same problem. mysqld is not running, and running zmmyinit fails complaining that it cannot find mysql.sock.

Also, starting mysqld.server as zimbra gives:

Starting mysqld daemon with databases from /opt/zimbra/db/data
STOPPING server from pid file /opt/zimbra/db/mysql.pid
060118 10:36:11 mysqld ended

[prosenbl]

hm perhaps this is another dns issue

zimbra@mailtemp:~/log> more zmmyinit.log
Neither host 'mailtemp' nor 'localhost' could be looked up with
/opt/zimbra/mysql/bin/resolveip
Please configure the 'hostname' command to return a correct hostname.
If you want to solve this at a later stage, restart this script with
the --force option
Starting mysqld daemon with databases from /opt/zimbra/db/data
STOPPING server from pid file /opt/zimbra/db/mysql.pid
060118 10:27:51 mysqld ended

Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
060118 10:28:10 mysqld ended

[marcmac]

what do you get from
host `hostname` (backticks, not quotes)
What's in /etc/hosts?
what do you get from
host localhost

[prosenbl]

Thanks for the quick repsonse... here's the info you asked for

zimbra@mailtemp:~/libexec> host `hostname`
mailtemp.my-domain.com has address 192.168.1.73

zimbra@mailtemp:~/libexec> host localhost
localhost has address 127.0.0.1

zimbra@mailtemp:~/libexec> more /etc/hosts
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#

127.0.0.1 localhost.localdomain localhost
63.138.xxx.xxx office.my-domain.com office


# 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
127.0.0.2 mailtemp.my-domain.com mailtemp

Also, since the zmmyinit.log seems to blame mysql's resolveip:

zimbra@mailtemp:~/libexec> /opt/zimbra/mysql/bin/resolveip `hostname`
IP address of mailtemp is 127.0.0.2


zimbra@mailtemp:~/libexec> /opt/zimbra/mysql/bin/resolveip localhost
IP address of localhost is 127.0.0.1

[marcmac]

Try adding the 192 entry for mailtemp to your /etc/hosts file:
192.168.1.73 mailtemp.my-domain.com mailtemp

[prosenbl]

No luck... with a new entry in the hosts file in addition to the 127.0.0.2 and with replacing the 127.0.0.2 entry...

even though:

zimbra@mailtemp:~/log> /opt/zimbra/mysql/bin/resolveip `hostname`
IP address of mailtemp is 192.168.1.73

[anand]

In the past when mysql would abruptly terminate I have found the reason for the badness stated in /opt/zimbra/log/mysqld.log.

What does your mysqld.log contain?

[prosenbl]

Unfortunately all I am seeing in /opt/zimbra/log/mysqld.log is:

zimbra@mailtemp:~/log> more mysqld.log
060118 14:32:44 mysqld started
060118 14:32:44 mysqld ended

060118 14:34:29 mysqld started
060118 14:34:29 mysqld ended