SSL error right after install, can't get into Admin UI

[robotrock]

Got a funny SSL error right after a seemingly smooth install.

When trying to connect to the Admin UI via web browser, I get the error

"SSL_error_rx_record_too_long"

Any ideas where to start looking? Thanks in advance!

[phoenix]

Did you try https://yourserver:7071?

[robotrock]

Whoops I was on the wrong port...however...

https://mail.testdomain.com:7071?

Just sits there saying "connected to mail.testdomain.com"

Did a port scan, and it looks ok...


Open TCP Port: 22 ssh
Open TCP Port: 25 smtp
Open TCP Port: 80 http
Open TCP Port: 110 pop3
Open TCP Port: 111 sunrpc
Open TCP Port: 143 imap
Open TCP Port: 389 ldap
Open TCP Port: 465 urd
Open TCP Port: 896
Open TCP Port: 993 imaps
Open TCP Port: 995 pop3s
Open TCP Port: 3310 dyna-access
Open TCP Port: 7025 vmsvc-2
Open TCP Port: 7071
Open TCP Port: 7072
Open TCP Port: 7110
Open TCP Port: 7143
Open TCP Port: 7780
Open TCP Port: 7993
Open TCP Port: 7995
Open TCP Port: 11211

[robotrock]

Upon further investigation it looks like MySQL isn't working properly...

Trying to get the mysql status yields:

Can't connect to local MySQL server through socket '/opt/zimbra/db/mysql.sock

Even after starting mysql, and getting a "starting mysqld...done" message

[robotrock]

From the mysql_error log:

081207 15:46:44 mysqld started
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
081207 15:46:45 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...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
081207 15:46:45 InnoDB: Starting an apply batch of log records to the database.
..
InnoDB: Progress in percents: 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 7
9 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
081207 15:46:46 InnoDB: Started; log sequence number 0 43655
081207 15:46:46 [ERROR] Fatal error: Can't open and lock privilege tables: Table
'mysql.host' doesn't exist
081207 15:46:46 mysqld ended

[frankman]

Originally Posted by robotrock

From the mysql_error log:

081207 15:46:46 [ERROR] Fatal error: Can't open and lock privilege tables: Table
 'mysql.host' doesn't exist
081207 15:46:46  mysqld ended

Seems other people are also getting this. I got the same error on a fresh install of the Open Source edition 5.0.13 in a CentOS 5.2 VMware guest.

Here's what I did to fix it:

Summary: Switch to the "zimbra" user, stop Zimbra, initialize zimbra to fix mysql, start up Zimbra so mysql is running as well as others, kill the logger and mysql, deleted the logger's db directory, initialize the logger and fix the passwords.

Summary details:

su - zimbra
zmcontrol stop
/opt/zimbra/libexec/zmmyinit
zmcontrol startup
ps -auxw | grep my.logger | grep -v grep | awk '{print $2}' | xargs kill
rm -rf logger/db
libexec/zmloggerinit 
zmcontrol status

Even though logger still failed, I then ran through these instructions. And finally, ran "zmcontrol stop", "zmcontrol startup" and "zmcontrol status" and everything ran fine from there.

The cause may have been that the host computer (XP SP3) would totally crash (I mean power off) during the Zimbra install on the guest OS (CentOS 5.2) on VMware Server 1.0.8 (free ). The Zimbra VM image I'm building is for testing and possibly developing zimlets (without better docs, this is really hard ). When I powered it all back on, I'd just "rm -rf /opt/zimbra" and run the "./install.sh --platform-override" script over again. Funny how it finds a previous install of Zimbra after I'd deleted it. I thought everything was installed in /opt/zimbra... Where is it finding this info?

Anyhow, it's all running well now .

P.S. I compiled the above answer from here, here and here.