Ubuntu VServer logger not working

[cshepherd]

Hey all,

I've had Zimbra up and running on various Debian and Ubuntu VServers, sometimes with logger working, sometimes not.

I've searched a fair bit in the forums and I can't seem to dig up much with relevance.

I now have the Ubuntu 4.0.2 Beta installed in an Ubuntu Dapper VServer.

zmcontrol status returns;
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running

On the web based server status window I'm getting
Server status data is not available. To see the server status, logger service must be installed.

I'm not seeing the list of services and their status in /var/log/zimbra.log so I guess this is where it's failing. /var/log/zimbra.log is far from empty though.

I've also found zimbra.csv files with all sorts of stats and the logger database exists.

What else can I look for?

Also, it seems to be linked; my graphs also aren't working.

[bobby]

is this for single node or multi-node installation? what's in /tmp/logprocess.out? what happens if you run zmstatuslog and zmdisklog manually (they're in ~/libexec/)?

[cshepherd]

Single node installation.

/tmp/logprocess.out;
Can't locate DBI.pm in @INC (@INC contains: /opt/zimbra/zimbramon/lib /opt/zimbra/zimbramon/lib/zimbrapm/SOAP /opt/zimbra/zimbramon/lib/zimbrapm /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /opt/zimbra/libexec/zmlogprocess line 33.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmlogprocess line 33.

~/libexec/zmstatuslog
Nothing goes to stdout

~/libexec/zmdisklog
Nothing goes to stdout

[jrh]

I have the same problem with the new 4.0.2 Ubuntu beta running on a vserver. Everything seems to be working great except server status and the logger. I had the same problem with an ubuntu vserver and the older debian installs too.

[pacsteel]

Same problem here "Server status data is not available. To see the server status, logger service must be installed."

This is on a fresh Ubuntu server 6.06.1 i386 install (Not vserver), and a fresh zimbra 4.0.2_GA_362_UBUNTU6

My /tmp/logprocess.out also starts with :

Can't locate DBI.pm in @INC (@INC contains: /opt/zimbra/zimbramon/lib /opt/zimbra/zimbramon/lib/zimbrapm/SOAP /opt/zimbra/zimbramon/lib/zimbrapm /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /opt/zimbra/libexec/zmlogprocess line 33.

doing a /# find -depth -name DBI.pm
shows that it is located in :

./opt/zimbra/zimbramon/lib/i386-linux-thread-multi/DBI.pm
./opt/zimbra/zimbramon/lib/i386-linux-thread-multi/Bundle/DBI.pm

So, I guess the question is A) Where in the install process does is Zimbra supposed to be either 1)adding that path to @INC or 2)copying DBI.pm into a path where it can be found? and B) what should we do to get it there now?

[pacsteel]

I added the following as line 31 to /opt/zimbra/libexec/zmlogprocess and restarted Zimbra

use lib "/opt/zimbra/zimbramon/lib/i386-linux-thread-multi";

[cshepherd]

If I add that line and restart my zmlogswatchstl and swatch is no longer running and I can now see this in ~/log/zimbra.log which I'm pretty sure wasn't in there before.

I removed the added line and the error is now gone.

2006-10-07 16:29:49,266 WARN  [Timer-0] [] DbStats - An error occurred while getting current database stats
com.zimbra.cs.service.ServiceException: system failure: getting database connection
        at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:174)
        at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:295)
        at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:168)
        at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:195)
        at com.zimbra.cs.db.DbStats.getStatus(DbStats.java:87)
        at com.zimbra.cs.db.DbStats.getStatData(DbStats.java:58)
        at com.zimbra.cs.stats.RealtimeStats.getData(RealtimeStats.java:73)
        at com.zimbra.cs.stats.ZimbraPerf$ZimbraStatsDumper.run(ZimbraPerf.java:539)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: java.sql.SQLException: Server connection failure during transaction. Due to underlying exception: 'java.net.SocketException: java.net.ConnectException: Connection refused'.

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused

STACKTRACE:

java.net.SocketException: java.net.ConnectException: Connection refused
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
        at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284)
        at com.mysql.jdbc.Connection.createNewIO(Connection.java:2680)
        at com.mysql.jdbc.Connection.(Connection.java:1485)
        at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
        at java.sql.DriverManager.getConnection(DriverManager.java:525)
        at java.sql.DriverManager.getConnection(DriverManager.java:140)
        at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:97)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:300)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
        at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:171)
        at java.sql.DriverManager.getConnection(DriverManager.java:525)
        at java.sql.DriverManager.getConnection(DriverManager.java:193)
        at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:286)
        at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:168)
        at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:195)
        at com.zimbra.cs.db.DbStats.getStatus(DbStats.java:87)
        at com.zimbra.cs.db.DbStats.getStatData(DbStats.java:58)
        at com.zimbra.cs.stats.RealtimeStats.getData(RealtimeStats.java:73)
        at com.zimbra.cs.stats.ZimbraPerf$ZimbraStatsDumper.run(ZimbraPerf.java:539)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)


** END NESTED EXCEPTION **

[pacsteel]

Originally Posted by cshepherd

... I can now see this in ~/log/zimbra.log which I'm pretty sure wasn't in there before.

I removed the added line and the error is now gone.

I guess that makes sense. Once you fix the "Can't locate DBI.pm" error, you can then move on to the next error (and the next one, and so on...)

Does adding the line make your Can't locate DBI.pm" error go away? Assuming your DBI.pm is located in ./opt/zimbra/zimbramon/lib/i386-linux-thread-multi/ then it should, but your system may not be a carbon copy of mine--you might have done the LAMP install for example.

My guess is removing the line makes your new error go away because if your system can't locate DBI.pm, it never gets far enough to write that next error to the zimbra.log.

[cshepherd]

Fair enough, that makes sense.

So... Anyone able to help with my new error

[mjfleck2000]

I am also running Ubuntu Dapper with 4.0.3 foss

I have not had server statistics give accurate information. At frist, I did not have ANY graph output. I fiddled with running the zimbra crontab commands on the command line and finally did get some graphs. However, they do not update.

/tmp/logprocess.out does show the DBI.pm error as does /tmp/gengraphs.out

I added use lib "/opt/zimbra/zimbramon/lib/i386-linux-thread-multi"; to the file /opt/zimbra/libexec/zmlogprocess as suggested above and restarted using zmlogswatchctl.

There was a different error in /tmp/logprocess.out. Unable to write to /var/log/zimbra.log. The permissions on /var/log/zimbra.log were 644 for root.adm. Hmmm. It seems to me that this file is supposed to be owned by the user zimbra. I chown zimbra and restarted zmlogswatchctl. No errors in /tmp/logswatch.out or /tmp/logprocess.out. In fact, logprocess.out now shows a lot of data that was processed.

I will watch the server statistics to see if they do indeed update, but this seems hopeful.

Mike