mysql.sock ....5.0.16 issue?

**physikal** · 05-11-2009, 04:12 PM

Long story short, I was working fine with a 5.0.14 install and then I had some LVM issues so I had to start over. Last time, after I learned the install process and server setup steps, the install went flawlessly. Now when rebuilding and using 5.0.16 I'm getting this:

Pasted from install log:

Code:

Mon May 11 15:55:06 2009 Initializing store sql database...
Mon May 11 15:55:06 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmmyinit
* Creating required directories
* Generating mysql config /opt/zimbra/conf/my.cnf
* Creating database in /opt/zimbra/db/data
* Starting mysql server
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...retrying
* Failed to connect to mysql...giving up!
Mon May 11 15:57:19 2009 done.
Mon May 11 15:57:19 2009 Setting zimbraSmtpHostname for mail.mydomain.com...
Mon May 11 15:57:19 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov -l ms mail.mydomain.com zimbraSmtpHostname mail.mydomain.com
Mon May 11 15:57:22 2009 done.
Mon May 11 15:57:22 2009 checking isEnabled zimbra-logger
Mon May 11 15:57:22 2009 zimbra-logger is enabled
Mon May 11 15:57:22 2009 Initializing logger sql database...
Mon May 11 15:57:22 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmloggerinit
* Creating required directories
* Creating database in /opt/zimbra/logger/db/data
* Starting logger_mysql server
* Loading schema /opt/zimbra/db/loggerdb.sql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
* Setting random password for mysql root user in zimbra local config
* Setting random password for mysql zimbra user in zimbra local config
* Changing mysql root user password
^G/opt/zimbra/logger/mysql/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/opt/zimbra/logger/db/mysql.sock' exists!

I also get this, but I think its related to the same issue:

Code:

Mon May 11 16:01:15 2009 Initializing Documents...
Mon May 11 16:01:15 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled TRUE
ERROR: zclient.IO_ERROR (invoke localhost, server: localhost) (cause: java.net.UnknownHostException localhost)
Mon May 11 16:01:17 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mcf zimbraNotebookAccount wiki@mydomain.com
ERROR: zclient.IO_ERROR (invoke localhost, server: localhost) (cause: java.net.UnknownHostException localhost)
Mon May 11 16:01:19 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov in wiki@mydomain.com
ERROR: zclient.IO_ERROR (invoke localhost, server: localhost) (cause: java.net.UnknownHostException localhost)
Mon May 11 16:01:21 2009 *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled FALSE
ERROR: zclient.IO_ERROR (invoke localhost, server: localhost) (cause: java.net.UnknownHostException localhost)
Mon May 11 16:01:22 2009 failed to initialize documents...see logfile for details.
Mon May 11 16:01:22 2009 Restarting mailboxd...

Posting more information since I see devs/mods asking for this info on similar posts:

Code:

[root@mail tmp]# host `hostname`
mail.mydomain.com has address 192.168.0.43
mail.mydomain.com mail is handled by 10 192.168.0.43.mydomain.com.

Code:

[root@mail tmp]# dig mydomain.com mx

; <<>> DiG 9.3.4-P1 <<>> mydomain.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40901
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.com.                 IN      MX

;; AUTHORITY SECTION:
mydomain.com.          38400   IN      SOA     mail.mydomain.com. admin.mydomain.com. 1242079966 10800 3600 604800 38400

;; Query time: 1 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Mon May 11 16:31:38 2009
;; MSG SIZE  rcvd: 78

Code:

[root@mail tmp]# dig mydomain.com any

; <<>> DiG 9.3.4-P1 <<>> mydomain.com any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64334
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com.                 IN      ANY

;; ANSWER SECTION:
mydomain.com.          38400   IN      SOA     mail.mydomain.com. admin.mydomain.com. 1242079966 10800 3600 604800 38400
mydomain.com.          38400   IN      NS      mail.mydomain.com.
mydomain.com.          38400   IN      A       192.168.0.43

;; ADDITIONAL SECTION:
mail.mydomain.com.     38400   IN      A       192.168.0.43

;; Query time: 1 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Mon May 11 16:32:37 2009
;; MSG SIZE  rcvd: 124

Any ideas? Never had this issue last time. Any info would be great, thanks!

I also get the initilizing docs

**phoenix** · 05-11-2009, 11:30 PM

According to your output you have no MX record pointing to the server. What exactly are you trying to do here, a new install or upgrade?

**physikal** · 05-12-2009, 08:02 AM

New install.

But if I do this look at the response:

Code:

[root@mail ~]# host -t mx mail.mydomain.com
mail.mydomain.com mail is handled by 10 192.168.0.43.mydomain.com

Check this out though, this is durring install:

Code:

DNS ERROR - No A record for mail.mydomain.com.

        Interface: 192.168.0.43
        Interface: 127.0.0.1


DNS ERROR - none of the MX records for mail.mydomain.com
resolve to this host
Change domain name? [Yes]
Create Domain: [mail.mydomain.com] mydomain.com
        Warning: no 'A' record found for 192.168.0.43.mydomain.com

        Interface: 192.168.0.43
        Interface: 127.0.0.1
        Warning: no 'A' record found for 192.168.0.43.mydomain.com
        Warning: no 'A' record found for 192.168.0.43.mydomain.com


DNS ERROR - none of the MX records for mydomain.com
resolve to this host
It is suggested that the MX record resolve to this host
Re-Enter domain name? [Yes]

However check out:

Code:

[root@mail ~]# host -t a mydomain.com
mydomain.com has address 192.168.0.43

One thing I am concerned with, is why is it doing it in a reverse type address. i.e. 192.168.0.43.mydomain.com? I don't recall it doing that before.

**phoenix** · 05-12-2009, 08:59 AM

Have you followed the Split DNS set-up instructions? Please post the output of the following (run on your Zimbra server):

Code:

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`

Just to make sure we start from the same point.

**physikal** · 05-12-2009, 11:11 AM

Code:

[root@mail ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.0.43    mail.mydomain.com mail
127.0.0.1       localhost.localdomain   localhost
#localhost.localdomain localhost
#::1            localhost6.localdomain6 localhost6

Code:

[root@mail ~]# cat /etc/resolv.conf
search mail.mydomain.com
nameserver 192.168.0.43
nameserver 192.168.0.150

Code:

[root@mail ~]# dig mydomain.com mx

; <<>> DiG 9.3.4-P1 <<>> mydomain.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38537
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; QUESTION SECTION:
;mydomain.com.                 IN      MX

;; ANSWER SECTION:
mydomain.com.          38400   IN      MX      0 192.168.0.43.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com.          38400   IN      NS      mail.mydomain.com.

;; ADDITIONAL SECTION:
192.168.0.43.mydomain.com. 38400 IN    A       192.168.0.43
mail.mydomain.com.     38400   IN      A       192.168.0.43

;; Query time: 2 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Tue May 12 11:06:00 2009
;; MSG SIZE  rcvd: 111

Code:

[root@mail ~]# dig mydomain.com any

; <<>> DiG 9.3.4-P1 <<>> mydomain.com any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11406
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;mydomain.com.                 IN      ANY

;; ANSWER SECTION:
mydomain.com.          38400   IN      SOA     mail.mydomain.com. admin.mydomain.com. 1242079969 10800 3600 604800 38400
mydomain.com.          38400   IN      NS      mail.mydomain.com.
mydomain.com.          38400   IN      A       192.168.0.43
mydomain.com.          38400   IN      MX      0 192.168.0.43.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com.     38400   IN      A       192.168.0.43
192.168.0.43.mydomain.com. 38400 IN    A       192.168.0.43

;; Query time: 2 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Tue May 12 11:06:24 2009
;; MSG SIZE  rcvd: 169

Code:

[root@mail ~]# host `hostname`
mydomain.com has address 192.168.0.43
mydomain.com mail is handled by 10 192.168.0.43.mail.mydomain.com.

Just so you know it is functioning now. But I am concerned with why its coming back with xxx.xxx.xxx.xxx.mydomain.com. now. I don't remember it being like that before.

Also yes the SplitDNS was setup correctly and nslookup returns the local address. (As it asks for in the end of the SplitDNS guide)

**phoenix** · 05-12-2009, 11:20 AM

You effectively have no MX record for your ZImbra server, this line:

Code:

mydomain.com.          38400   IN      MX      0 192.168.0.43.mydomain.com.

should look like this:

Code:

mydomain.com.          38400   IN      MX      10 mail.mydomain.com.

Fix that and restart Zimbra and see what happens.

**physikal** · 05-12-2009, 01:48 PM

Could this possibly be caused by only having the SplitDNS server with an A and an MX record pointing at the local server? I have no set the WAN DNS server/hosting server to point to this server yet because this server has not gone live yet. I hope that makes sense.

Thank you again for all your help Phoenix, you're all over these boards! A machine I tell ya!

**physikal** · 05-12-2009, 02:08 PM

Code:

$ttl 38400
mydomain.com.	IN	SOA	mail.mydomain.com. admin.mydomain.com. (
			1242079969
			10800
			3600
			604800
			38400 )
mydomain.com.	IN	NS	mail.mydomain.com.
mydomain.com.	IN	A	192.168.0.43
mail.mydomain.com.	IN	A	192.168.0.43
mail.mydomain.com.	IN	MX	10 192.168.0.43
mydomain.com.	IN	MX	0 192.168.0.43
192.168.0.43.mydomain.com.	IN	A	192.168.0.43

This is my SplitDNS config file, how does that not have an MX record though? I hate DNS heh.

**physikal** · 05-12-2009, 03:04 PM

So now my dig looks like this:

Code:

[root@mail ~]# dig mydomain.com mx

; <<>> DiG 9.3.4-P1 <<>> mydomain.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34478
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com.                 IN      MX

;; ANSWER SECTION:
mydomain.com.          38400   IN      MX      10 mail.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com.          38400   IN      NS      192.168.0.43.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com.     38400   IN      A       192.168.0.43

;; Query time: 2 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Tue May 12 14:58:12 2009
;; MSG SIZE  rcvd: 95

But my SplitDNS looks like:

Code:

$ttl 38400
@	IN	SOA	mail.mydomain.com. admin.mydomain.com. (
			1242079978
			10800
			3600
			604800
			38400 )
	IN	NS	192.168.0.43
	IN	A	192.168.0.43
	IN	MX	10 mail

mail.mydomain.com.	IN	A	192.168.0.43

When SplitDNS guide says to have:

Code:

;
;       Addresses and other host information.
;
@       IN      SOA     server.example.com. hostmaster.server.example.com. (
                               10118      ; Serial
                               43200      ; Refresh
                               3600       ; Retry
                               3600000    ; Expire
                               2592000 )  ; Minimum
;       Define the nameservers and the mail servers
               IN      NS      
               IN      A       
               IN      MX      10 server.example.com.

My main concern is, the guide says to have for an MX, server.example.com...so mine should be mail.mydomain.com. Where its just the hostname, mail. For some reason it chooses to trail with mydomain.com on its own.

For example, when my DNS looked like :

Code:

$ttl 38400
@	IN	SOA	mail.mydomain.com. admin.mydomain.com. (
			1242079978
			10800
			3600
			604800
			38400 )
	IN	NS	192.168.0.43
	IN	A	192.168.0.43
	IN	MX	10 mail.mydomain.com

mail.mydomain.com.	IN	A	192.168.0.43

If my DNS was setup like that ^^^ then my dig mydomain.com looked like:

Code:

[root@mail ~]# dig mydomain.com mx

; <<>> DiG 9.3.4-P1 <<>> mydomain.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49908
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.com.                 IN      MX

;; ANSWER SECTION:
mydomain.com.          38400   IN      MX      10 mail.mydomain.com.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com.          38400   IN      NS      192.168.0.43.mydomain.com.

;; Query time: 2 msec
;; SERVER: 192.168.0.43#53(192.168.0.43)
;; WHEN: Tue May 12 14:57:13 2009
;; MSG SIZE  rcvd: 93

So basically, for some reason its trailing everything w/ mydomain.com. Is that right?

-Phys

Thanks again.

**phoenix** · 05-12-2009, 11:01 PM

For the moment, the fact you have no external DNS records doesn't matter. That only means you can't receive mail from outside your LAN, not a problem as zimbra isn't installed yet.

It is also correct to just have the server name in your DNS records instead of the FQDN, the domain name part will get added automatically as you've seen. I prefer to specify the full FQDN instead of just the server name.

The problem you've got with the following example:

Code:

$ttl 38400
@	IN	SOA	mail.mydomain.com. admin.mydomain.com. (
			1242079978
			10800
			3600
			604800
			38400 )
	IN	NS	192.168.0.43
	IN	A	192.168.0.43
	IN	MX	10 mail.mydomain.com

mail.mydomain.com.	IN	A	192.168.0.43

is the fact you've not got a period "." following the FQDN mail.mydomain.com and in that config you'll get the domain name added - that's why the example above gave you this:

Code:

mydomain.com.          38400   IN      MX      10 mail.mydomain.com.mydomain.com.

Post your DNS configuration files so I can check them for you and make sure everything's OK.

Zimbra

Thread: mysql.sock ....5.0.16 issue?

LinkBack

Thread Tools

Search Thread

Display

mysql.sock ....5.0.16 issue?

Thread Information

Users Browsing this Thread

Similar Threads

ZCS 5.0.16 Released

Zimbra desktop and AVG Free 8.0 Issue

dns issue with suse 10.2 and issue with bind

Intermittent issue (issue# 5852) ?

Posting Permissions