Zimbra

jholder · #11 (**permalink**) 10-30-2007, 08:26 PM

Hi Max-
I'm actually in the middle of a lot of work. I'm going to refer to you to mike who can help you more.

Please keep in mind that if you require priority support, then the Network Edition is really what you want.

Max Ma · #12 (**permalink**) 10-30-2007, 09:08 PM

Hi Jholder,

we will consider the network version as we are testing some push mail issue as you know in Hong Kong most of the business are on mobile now.
as for this case, I will be very happy to have Mike to help out asap.

Dear Mike,
Should you need any further information, please let me know.

many thanks,

max

mmorse · #13 (**permalink**) 10-30-2007, 09:10 PM

Check your PM's I was actually waiting for you to sign into an IM client.

mmorse · #14 (**permalink**) 10-31-2007, 12:05 AM

Current status:
Live box: .7 OlderMail + the MostRecentMail + well, it's live so anything new that comes in. I don't know if he ever got his statistic reports working properly on that live box. (It's 1AM my time & lunch time there and it seems he's run off without answering me; plus I don't have a login to that live one.)

Hold box: .7 NewerMail Logger hits some nice database connection errors occasionally on this box but everything else is up fine.

Quote:

at com.mysql.jdbc.Connection.createNewIO(Connection.j ava:2707)
at com.mysql.jdbc.Connection.<init>(Connection.java:1 531)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:266)
at java.sql.DriverManager.getConnection(DriverManager .java:582)
at java.sql.DriverManager.getConnection(DriverManager .java:207)
at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool .java:368)

I'll reset the db/pass/zmloggerinit when he comes back (as I perfer not to working on it with him not there or answering my IM's)

However, that's about 27-29 days of mail difference between the live and the hold

It's gonna be a long manual process...for him to grab the mail, cals, etc...and there might even be accounts on the hold that aren't on the live if he's made new one's in the past 30days...so just a little fun!
(A perfect case for you all to make more frequent backups!)
update: I see 151 on 'hold' and he says 141 on 'live' so yup need to create those on live.

On further investigation it was found that he was backing up by just cp -r /opt/zimbra instead of something that keeps permissions like rsync/tar.

Plus on one of the 'restores' he tried it was to a 64bit machine and he wasn't aware of the wiki docs on that.

He's also planning on purchasing NE, especially for the backups, makes 2 out of this thread alone

though he's still deciding between the std/pro and may hold off on MobileSync initially.

When people's accounts are up to par on the live box, he's going to backup the live, and try the upgrade to .9 again.

While he could do the opposite (take the 'hold' copy make it production, and then grab the older mail that's in the 'live') which might be easier on the calendaring/notebooks, I think he doesn't want to mess with what's up and running & works.

mmorse · #15 (**permalink**) 10-31-2007, 12:14 AM

yup, for logger I got:

Quote:

/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 1007 (HY000) at line 26: Can't create database 'zimbra_logger'; database exists
ERROR 1146 (42S02) at line 2: Table 'zimbra_logger.config' doesn't exist
* 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
* Changing mysql zimbra user password
ERROR 1133 (42000) at line 1: Can't find any matching row in the user table
**** PASSWORD CHANGE FAILED

A manual pass reset did nothing helpful, so once again I just tried:

Quote:

$./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

So normailly if you get the "can't connect localhost" error alone, it might be a missing localhost adapter or something.
However, we got an oh so nice error log that tells us things like:

Quote:

071031 5:13:28 InnoDB: Started; log sequence number 0 43655
071031 5:13:28 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
071031 05:13:28 mysqld ended
---
071031 06:11:36 mysqld started
071031 6:11:36 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...
071031 6:11:36 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 36808.
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
071031 6:11:36 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
071031 6:11:37 InnoDB: Started; log sequence number 0 43655
071031 6:11:37 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: ready for connections.
Version: '5.0.45-log' socket: '/opt/zimbra/logger/db/mysql.sock' port: 7307 Source distribution
---
A mysqld process already exists at Wed Oct 31 06:12:47 HKT 2007

and even while zmcontrol status reports everythign running, logmysql zimbra_logger returns:

Quote:

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

So I guess it's time for a password reset/clear of db/data

mmorse · #16 (**permalink**) 10-31-2007, 12:45 AM

Max, as you're away right now, what I did was:
-killed anything I saw after ps aux | grep logger/mysql
-emptied /opt/zimbra/logger/db/data
-reset permissions/ownership on that folder
-then in /opt/zimbra/libexec/ I ran

Quote:

$./zmloggerinit
* Creating required directories
* Creating database in /opt/zimbra/logger/db/data
* Starting logger_mysql server
* Loading schema /opt/zimbra/db/loggerdb.sql
* 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
* Changing mysql zimbra user password
* Changed zimbra mysql user password

mmorse · #17 (**permalink**) 10-31-2007, 01:20 AM

So on the 'hold' box:
For a bit (a day or two) you'll just have 'data not yet available' in the server statistics section until everything fires.

Then you we're showing the stats (different from the logger) as stopped in admin console gui:

This is Bug 17977 - Server Status in admin console shows incorrect info. (Which has been addressed in .8FOSS & .9NE)

But you're on .7 so to work around that I simply edited your crontab -e and changed:
#*/2 * * * * /opt/zimbra/libexec/zmstatuslog > */2 * * * * source ~/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog
and viola!:

So that takes care of your 'hold' box for the time being.

As you can see from that pic, my time is 2AM & the server time is 6PM.

(Though if you time zone is actually Hong Kong; on my world clock I do show your currently at 3PM there - so do fix that 3 hour difference sometime if needed.)

I'd quickly check the 'live' for you, but you never provided a login - so it's time that I say: good night & see you in the morning!