[SOLVED] Another logger not working thread

[TheCowStir]

The problem. My FOSS 5.0.20 version of zimbra has not been able to show a status of services in the admin console since I migrated servers. I also don't get the admin e-mails with mail statistics. Both were working before my migration.

zimbra@zimbra:~$ zmcontrol -v
Release 5.0.20_GA_3127.UBUNTU8 UBUNTU8 FOSS edition

zimbra@zimbra:~$ zmloggerctl stop 
Stopping mysqld...done.
Stopping logswatch...done.
zimbra@zimbra:~$ ps ax | grep mysql
 3631 pts/0    S      0:00 /usr/bin/perl -w /opt/zimbra/libexec/zmstat-mysql
17601 pts/0    S+     0:00 grep mysql
zimbra@zimbra:~$ zmloggerctl start
Starting mysqld...done.
Starting logswatch...done.
zimbra@zimbra:~$ zmloggerctl status
logmysql.server is not running
zimbra@zimbra:~$ ps ax | grep mysql
 3631 pts/0    S      0:00 /usr/bin/perl -w /opt/zimbra/libexec/zmstat-mysql
17638 pts/0    S      0:00 /bin/sh /opt/zimbra/logger/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.logger.cnf --external-locking --log-error=/opt/zimbra/log/logger_mysql_error.log --ledir=/opt/zimbra/logger/mysql/libexec
17696 pts/0    Sl     0:00 /opt/zimbra/logger/mysql/libexec/mysqld --defaults-file=/opt/zimbra/conf/my.logger.cnf --basedir=/opt/zimbra/logger/mysql --datadir=/opt/zimbra/logger/db/data --pid-file=/opt/zimbra/logger/db/mysql.pid --skip-external-locking --port=7307 --socket=/opt/zimbra/logger/db/mysql.sock --external-locking
17965 pts/0    R+     0:00 grep mysql
zimbra@zimbra:~$ logmysql.server status
mysql is running with pid 17696

When I try to access the server status page in the admin console I get:

Server error encountered Message: system failure: getting database logger connection Error code: service.FAILURE Method: GetServiceStatusRequest Details:soap:Receiver

I have gone through the logger wiki and have not found any corruption.

today in working on the problem found a post describing how to delete the DB and re-initialize it, which I did, but did not help:
basically (from memory):
shut down logger service as zimbra user
rm -rf /opt/zimbra/logger/db/data/*
chown zimbra.zimbra /opt/zimbra/db/data
chmod 775 /opt/zimbra/db/data
cd /opt/zimbra/libexec/
./zmloggerinit
./zmfixperms --verbose --extended
start the logger as zimbra user (which stated it was already running).

no change.

I am running on Ubuntu 8.0.4 physical PE 2650 server. I migrated from a VM server running OpenSuse 10.1 as there was no supported upgrade path to 6.x in OpenSuse.

any ideas or addition resources/places to look for what is going on?

[LMStone]

SuSE? Using syslog-ng?

If so, this may help:
Problem ZCS 6.0.4 FOSS Installation on SLES 64 bit

All the best,
Mark

[TheCowStir]

I migrated away from Suse to Ubuntu, and Ubuntu is not using syslog-ng.

I also just tried resetting all mysql passwords (base and logger) via the directions on the wiki. No help...

I'm about ready to use the directions from the wiki to migrate from Open edition to Network Edition, but do it in-place to the Open Edition as the direct copy doesn't work for me...

[TheCowStir]

Looking a little deeper into problem and scripts present, I found that the logger instance of mysql didn't have the error log file, so I created that and set zimbra ownership.

I no longer get an error in the admin console for server status, but the page is stating that the package isn't installed.

with that I decided to re-run the 5.0.20 installer, and received the same error that I have always received on this box since I have migrated: UPGRADE FAILED right after starting logger mysql

Operations logged to /tmp/install.log.25746
Checking for existing installation...
    zimbra-ldap...FOUND zimbra-ldap-5.0.20_GA_3127.UBUNTU8
    zimbra-logger...FOUND zimbra-logger-5.0.20_GA_3127.UBUNTU8
    zimbra-mta...FOUND zimbra-mta-5.0.20_GA_3127.UBUNTU8
    zimbra-snmp...FOUND zimbra-snmp-5.0.20_GA_3127.UBUNTU8
    zimbra-store...FOUND zimbra-store-5.0.20_GA_3127.UBUNTU8
    zimbra-apache...FOUND zimbra-apache-5.0.20_GA_3127.UBUNTU8
    zimbra-spell...FOUND zimbra-spell-5.0.20_GA_3127.UBUNTU8
    zimbra-proxy...NOT FOUND
    zimbra-archiving...NOT FOUND
    zimbra-convertd...NOT FOUND
    zimbra-cluster...NOT FOUND
    zimbra-core...FOUND zimbra-core-5.0.20_GA_3127.UBUNTU8
ZCS upgrade from 5.0.20 to 5.0.20 will be performed.

Saving existing configuration file to /opt/zimbra/.saveconfig


PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
ZIMBRA, INC. ("ZIMBRA") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.

License Terms for the Zimbra Collaboration Suite:
  http://www.zimbra.com/license/zimbra_public_eula_2.1.html


Press Return to continue

Checking for prerequisites...
     FOUND: NPTL
     FOUND: sudo-1.6.9p10-1ubuntu3.5
     FOUND: libidn11-1.1-1
     FOUND: libpcre3-7.4-1ubuntu2.1
     FOUND: libgmp3c2-2:4.2.2+dfsg-1ubuntu2
     FOUND: libexpat1-2.0.1-0ubuntu1
     FOUND: libstdc++6-4.2.4-1ubuntu4
     FOUND: libstdc++5-1:3.3.6-15ubuntu6
     FOUND: libltdl3-1.5.26-1ubuntu1
Checking for suggested prerequisites...
    FOUND: perl-5.8.8
Prerequisite check complete.
Checking current number of databases...

Do you want to verify message store database integrity? [Y] 
Verifying integrity of message store databases.  This may take a while.
Starting mysqld...done.
mysqld is alive
No errors found

Do you want to verify logger database integrity? [Y] 
Verifying integrity of logger database.  This may take a while.
Starting mysqld...done.
mysqld is alive
No Logger DB errors found.

Checking for installable packages

Found zimbra-core
Found zimbra-ldap
Found zimbra-logger
Found zimbra-mta
Found zimbra-snmp
Found zimbra-store
Found zimbra-apache
Found zimbra-spell
Found zimbra-proxy


The Zimbra Collaboration Suite appears already to be installed.
It can be upgraded with no effect on existing accounts,
or the current installation can be completely removed prior
to installation for a clean install.

Do you wish to upgrade? [Y] 

Select the packages to install
    Upgrading zimbra-core
    Upgrading zimbra-ldap
    Upgrading zimbra-logger
    Upgrading zimbra-mta
    Upgrading zimbra-snmp
    Upgrading zimbra-store
    Upgrading zimbra-apache
    Upgrading zimbra-spell

Install zimbra-proxy [N] 
Checking required space for zimbra-core
checking space for zimbra-store

Installing:
    zimbra-core
    zimbra-ldap
    zimbra-logger
    zimbra-mta
    zimbra-snmp
    zimbra-store
    zimbra-apache
    zimbra-spell

The system will be modified.  Continue? [N] y

Shutting down zimbra mail

Backing up the ldap database...done.

Removing existing packages

   zimbra-ldap...done
   zimbra-logger...done
   zimbra-mta...done
   zimbra-snmp...done
   zimbra-store...done
   zimbra-spell...done
   zimbra-apache...done
   zimbra-core...done

Removing deployed webapp directories
Installing packages

    zimbra-core......zimbra-core_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-ldap......zimbra-ldap_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-logger......zimbra-logger_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-mta......zimbra-mta_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-snmp......zimbra-snmp_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-store......zimbra-store_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-apache......zimbra-apache_5.0.20_GA_3127.UBUNTU8_i386.deb...done
    zimbra-spell......zimbra-spell_5.0.20_GA_3127.UBUNTU8_i386.deb...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=zimbra.stir.org
   LDAPHOST=zimbra.stir.org
   LDAPPORT=389
   SNMPTRAPHOST=zimbra.stir.org
   SMTPSOURCE=admin@stir.org
   SMTPDEST=admin@stir.org
   SNMPNOTIFY=yes
   SMTPNOTIFY=yes
   LDAPROOTPW=---
   LDAPZIMBRAPW=---
   LDAPPOSTPW=---
   LDAPREPPW=---
   LDAPAMAVISPW=---
   LDAPNGINXPW=---
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.01152010-145542.log
Starting ldap...done.
Setting defaults...done.
Upgrading from  to 5.0.20_GA_3127
Stopping zimbra services
Verifying /opt/zimbra/conf/my.cnf
Starting mysql
Starting logger mysql
I can't upgrade version 

UPGRADE FAILED - exiting

Any ideas?

[TheCowStir]

I finally found my problem with the failed upgrades.

I noticed that during an upgrade (even between versions) the old version number wasn't displayed, so I hard coded my old version number into the zmsetup.pl file to let the upgrade script continue. Once that happened the upgrade continued until it complained about:

Setting defaults from ldap...done.
dualvar is only available with the XS version of Scalar::Util at /opt/zimbra/zimbramon/lib/IO/Socket/SSL.pm line 38
BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/IO/Socket/SSL.pm line 38.
Compilation failed in require at /opt/zimbra/zimbramon/lib/Net/LDAP.pm line 998.

With that information I found This post [SOLVED] Still no fix ... " is only avaliable with the XS version at" issue stating that there were probably library mismatches due to the migration from OpenSuse to Ubuntu. I installed a fresh system in vmware and copied the new /opt/zimbra/zimbramon/lib directory to my production server and re-ran the setup.

That fixed my problem. The upgrade completed... Now to upgrade to 6.0.4 and install my new GoDaddy certificate manually(2048 bit fun, fun).

Hope this helps someone else at some point.

[DeJuan N. Onley]

Originally Posted by TheCowStir

I noticed that during an upgrade (even between versions) the old version number wasn't displayed, so I hard coded my old version number into the zmsetup.pl file to let the upgrade script continue.

Noob question: where did you set this at?

Looking at /opt/zimbra/libexec/zmsetup.pl, did you change the following line:

our $curVersion = "";

If so, would something like this work:

our $curVersion = "5.0.18_GA_3011.UBUNTU8";

Obviously I am having the same problem and am looking for newbie guidance here.

[DeJuan N. Onley]

Originally Posted by TheCowStir

I noticed that during an upgrade (even between versions) the old version number wasn't displayed, so I hard coded my old version number into the zmsetup.pl file to let the upgrade script continue.

Can you give details on what you changed in zmsetup.pl? I have searched the forums and found no info on where to "hard code" the version number in here. I tried changing $curVersion but it still is showing a blank old version number when upgrading. Sorry for the noob question...