Logger stopped after upgrade to 5.0.7

[captainmish]

Hello
I upgraded 5.0.6 NE to 5.0.7 NE on ubuntu 604 last night, there were some problems, I had to re-run the install.
After the second run, things started working, but the logger will still not start:

zmcontrol status
antispam Running
antivirus Running
ldap Running
logger Stopped
logmysql.server is not running
mailbox Running
mta Running
snmp Running
spell Running
stats Running

But when I try to start it:
logmysql.server start
mysqld_safe already running with pid 4977

after stopping logmysq.server and then starting with logmysql.server start
it looks promising, giving:
Starting mysqld daemon with databases from /opt/zimbra/logger/db/data

logmysql.server status
mysql is running with pid 14307

zmloggerctl status
logmysql.server is not running

In desperation I have tried a full server reboot in case old processes were hanging on, this also did not improve things.

Can anyone shed some light and point me in the right direction?

[captainmish]

I have removed all the logger dbs and done the zmloggerinit process. This did not return any errors, but:

zmcontrol status:
antispam Running
antivirus Running
ldap Running
logger Stopped
zmlogswatchctl is not running
mailbox Running
mta Running
snmp Running
spell Running
stats Running

zimbra@mail:~$ zmloggerctl start
mysqld_safe already running with pid 17202

[captainmish]

A bit of progress:

Issuing zmloggerctl reload seems to have been what it wanted. zmcontrol status now shows that all services are running, but...

Logging in to the web gui, on the server status section gives:

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

[phoenix]

Check to see if there are any errors in the database, fix them if there are any.

[captainmish]

Thanks Phoenix

zmloggerctl stop (if this is not done, "1 client is using or hasn't closed the table" errors are given on next step, this seems normal to me)

/opt/zimbra/mysql/bin/myisamchk -s /opt/zimbra/logger/db/data/zimbra_logger/*.MYI
(returns nothing - "no repair needed" messages suppressed)

So it seems the logger tables are all ok. I can see that there is data in them as well (`select * from raw_logs limit 1` returns a very recent log entry)

Tried on a different client machine to access the admin gui and same error is returned.

find /opt/zimbra/logger/ -name *.err returns nothing, so there doesnt seem to be an error file as mentioned in a few posts.