logger, logmysql.server is not running

[food]

Hi

with a fresh installation of the network trial, 5.0.10.

INSTALL_PACKAGES="zimbra-core zimbra-logger zimbra-mta zimbra-snmp "

The machine, which is acting as zimbra mta, is receiving emails fine, and emails sent from the web interface are going out fine. The logger isn't running however

[zimbra@smtp bin]$ zmcontrol status
Host smtp.mydomain.com
        antispam                Running
        antivirus               Running
        logger                  Stopped
                logmysql.server is not running
        mta                     Running
        snmp                    Running
        stats                   Running

error in logger_mysql_error.log is:

081112 04:49:07  mysqld started
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
081112  4:49:07  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
081112  4:49:07  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 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 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
081112  4:49:07  InnoDB: Started; log sequence number 0 43655
081112  4:49:07 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
081112 04:49:07  mysqld ended

status from scripts:

[zimbra@smtp bin]$ zmloggerctl status
logmysql.server is not running

[zimbra@smtp bin]$ logmysql.server status
mysql is not running

Does this ring a bell with anyone?

Not really sure what this logger service offers. Perhaps I don't really need this feature anyway. Are people finding it useful?

I should also mention that this server is running centos. Not my choice. Once our testing is complete we'll be reinstalling with another os.

thanks

Sean

[uxbod]

MySQL Crash Recovery :: Wiki

[food]

Originally Posted by uxbod

MySQL Crash Recovery :: Wiki

thanks

I started with the process on the wiki page. The paths and filenames are a bit different, ie. my.logger.cnf. The db won't come up like that:

`mysql.server start` gives this in log

081113 01:05:13  mysqld started
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
081113  1:05:13  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
081113  1:05:13  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 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 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
081113  1:05:13  InnoDB: Started; log sequence number 0 43655
InnoDB: !!! innodb_force_recovery is set to 3 !!!
081113  1:05:13 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
081113 01:05:13  mysqld ended

BTW, not sure if I'm barking up the wrong tree, but when I edit mysql.server to echo ${mysql_directory}', at the start, right after zmsetvars, I get this:

[zimbra@smtp bin]$ mysql.server start
mysql_directory is: '/opt/zimbra/mysql'

which might not be good because:

[zimbra@smtp bin]$ ls /opt/zimbra/mysql
ls: /opt/zimbra/mysql: No such file or directory

thanks

Sean

[food]

Originally Posted by food

BTW, not sure if I'm barking up the wrong tree, but when I edit mysql.server to echo ${mysql_directory}', at the start, right after zmsetvars, I get this:

[zimbra@smtp bin]$ mysql.server start
mysql_directory is: '/opt/zimbra/mysql'

which might not be good because:

[zimbra@smtp bin]$ ls /opt/zimbra/mysql
ls: /opt/zimbra/mysql: No such file or directory

ok, I'm thinking that it was logmysql.server rather than mysql.server that I should have substituted for that wiki crash recovery. Anyhow, the daemon won't start from logmysql.server either. I think that I saw a post outlining a manual reinstall of the logger mysql; I may try that,

thanks

Sean

[phoenix]

You can re-initialise the logger with zmloggerinit - it will set it up again and clear the databases. You should have a look at the troubleshooting section of the wiki article on this page: Logger - Zimbra :: Wiki

[food]

Originally Posted by phoenix

You can re-initialise the logger with zmloggerinit - it will set it up again and clear the databases. You should have a look at the troubleshooting section of the wiki article on this page: Logger - Zimbra :: Wiki

thanks, I did try that:

[zimbra@smtp data]$ /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
/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!
* Changing mysql zimbra user password
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
**** PASSWORD CHANGE FAILED

I'll check out that wiki page

Sean

[food]

Hi,

I have the logger running now. What I did was a bit ugly, but looks as if it did the trick. In case anyone needs this info ..

the logger mysql wasn't installing completely, the bare bones were there but no mysql tables or logger tables

so it wasn't a case of a corrupt db, the install was erroring out with errors about (among other things) a file not found ( /opt/zimbra/mysql-standard-5.0.51a-pc-linux-gnu-i686-glibc23/bin/my_print_defaults )

the filename was one of a number of defaults in /opt/zimbra/logger/mysql/bin/mysql_install_db all of which refer to a location higher up the zimbra tree, the logger mysql is in /opt/zimbra/logger/mysql

I substituted all these default path references for the logger mysql path, and ran zmloggerinit like that

seems to have worked, the logger is running, mysql accepts the zimbra user password from zmlocalconfig, the logger database is there, so I'm hoping that the edit allowed the install to conclude successfully

[zimbra@smtp bin]$ zmcontrol status
Host smtp.mydomain.com
        antispam                Running
        antivirus               Running
        logger                  Running
        mta                     Running
        snmp                    Running
        stats                   Running

Sean

[rkscape]

Hi Sean, I'm experiencing the same problem with the logger mysql not installing properly.

Can you explain your solution in a little more detail? "I substituted all these default path references for the logger mysql path, and ran zmloggerinit like that"

Which file did you substitue the default paths?
What were the paths you used?

Thanks.

Rich

[phoenix]

Originally Posted by rkscape

Hi Sean, I'm experiencing the same problem with the logger mysql not installing properly.

Can you explain your solution in a little more detail? "I substituted all these default path references for the logger mysql path, and ran zmloggerinit like that"

Which file did you substitue the default paths?
What were the paths you used?

Thanks.

Rich

Details please. New install or upgrade? Which operating system and version of Zimbra?

Please update your forum profile with the output of:

zmcontrol -v

[rkscape]

We performed a new install on version 5.09 then upgraded to this version, before we actually configured the logger.
Release 5.0.13_GA_2791.RHEL4_64_20090206104831 RHEL4_64 NETWORK edition

Here is our OS information:
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 x86_64 x86_64 GNU/Linux

Thanks