This happe

[mmorse]

This happen when you attempt to view statistics in the admin console?

Could you post the links you've followed?
Also see: Logger - Zimbra :: Wiki

Have you tried zmloggerinit yet?

This is a brand new setup so you have nothing to loose by doing so - it should create a new database and generate the necessary passwords

[marklindley]

Hi mmorse
I have tried a lot of threads ... here is the error.
1. Resetting LDAP & MySQL Passwords - Zimbra :: Wiki

2.Logger - Zimbra :: Wiki


zimbra@mailserver:/root$ /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 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

* 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: 'Access denied for user 'root'@'localhost' (using password: NO)'

* Changing mysql zimbra user password

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

**** PASSWORD CHANGE FAILED

zimbra@mailserver:/root$


Really lost on this, been working on it nearly 2 days now. I don't want to reinstall from fresh because I have add all of my domains and user accounts
Thanks Mark

[mmorse]

wow I see you now have 3 threads on this - I'll consolidate them up in a bit
ya, logger is a frustration to many, so don't give up - you can still run zimbra without logger (though you won't have any daily reports, server message statistics, and can't zmmsgtrace properly)
This is not to be confused with the stats service - which might get renamed perfmon (Bug 20549 - rename stats service)
(before doing this I assume you have no users connected, because well, your killing any running zimbra processes)
sudo zimbra

zmcontrol stop

switch back to another user

(use sudo as needed - I don't know if your root or not)

ps auxww | grep zimbra

ps auxww | grep mysql

(kill any remaining processes on either of those)

rm -rf /opt/zimbra/logger/db (maybe only db/data/ ?)

zmloggerinit

[marklindley]

root@mailserver:/opt/zimbra/logger# locate zmloggerinit

/opt/zimbra/libexec/zmloggerinit

/opt/zimbra/log/zmloggerinit.log

root@mailserver:/opt/zimbra/logger# /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

[jholder]

Do you have localhost adapter, and an localhost entry in your hosts file?

[marklindley]

jholder,
Not 100% sure what you mean but this is what I have in the hosts file
127.0.0.1 localhost.localdomain localhost

212.79.238.154 mailserver.itismail.co.uk mailserver


Zimba is work correctly it's just the logger that is not playing ball.


Thanks Mark

[jholder]

Hi Mark-

This is honestly a shot in the dark, but we restrict access to the mysqldb to localhost for security. If there isn't a localhost adapter, then that can cause your issue. I've seen this in particular on Virtual Machines like Xen.
What does ifconfig show?

[marklindley]

root@mailserver:/opt/zimbra/db# ifconfig

eth0 Link encap:Ethernet HWaddr 00:16:3E:49:33:7E

inet addr:212.79.238.154 Bcast:212.79.238.191 Mask:255.255.255.192

inet6 addr: fe80::216:3eff:fe49:337e/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:552778 errors:0 dropped:0 overruns:0 frame:0

TX packets:152405 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:351386430 (335.1 MiB) TX bytes:20281124 (19.3 MiB)
lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:98881 errors:0 dropped:0 overruns:0 frame:0

TX packets:98881 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:31424814 (29.9 MiB) TX bytes:31424814 (29.9 MiB)

[jholder]

Is there a:

/opt/zimbra/logger/db/(hostanme).err file? If so, can you post that?

[marklindley]

Hi,
It was loacted in /opt/zimbra/logger/db/data
root@mailserver:/opt/zimbra/logger/db/data# cat mailserver.err

071017 18:04:57 mysqld started

InnoDB: The first specified data file ./ibdata1 did not exist:

InnoDB: a new database to be created!

071017 18:04:57 InnoDB: Setting file ./ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

071017 18:04:58 InnoDB: Log file ./ib_logfile0 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile0 size to 5 MB

InnoDB: Database physically writes the file full: wait...

071017 18:04:58 InnoDB: Log file ./ib_logfile1 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile1 size to 5 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

071017 18:04:58 InnoDB: Started; log sequence number 0 0

071017 18:04:58 [ERROR] Can't start server : Bind on unix socket: Permission denied

071017 18:04:58 [ERROR] Do you already have another mysqld server running on socket: /opt/zimbra/logger/db/mysql.sock ?

071017 18:04:58 [ERROR] Aborting
071017 18:04:58 InnoDB: Starting shutdown...

071017 18:05:00 InnoDB: Shutdown completed; log sequence number 0 43655

071017 18:05:00 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete
071017 18:05:00 mysqld ended
071017 18:06:27 mysqld started

071017 18:06:27 InnoDB: Started; log sequence number 0 43655

071017 18:06:27 [ERROR] Can't start server : Bind on unix socket: Permission denied

071017 18:06:27 [ERROR] Do you already have another mysqld server running on socket: /opt/zimbra/logger/db/mysql.sock ?

071017 18:06:27 [ERROR] Aborting
071017 18:06:27 InnoDB: Starting shutdown...

071017 18:06:30 InnoDB: Shutdown completed; log sequence number 0 43655

071017 18:06:30 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete
071017 18:06:30 mysqld ended


Looks like a perms problem
Mark