Zimbra work but all services are marked as down

[Samp]

Hi,

Strange behavior Zimbra works but all services are marked as down in admin wizard !?

Server stats send an error panel with:

Mail : system failure: Unable to read logger stats Code d'erreur : service.FAILURE Method: GetLoggerStatsRequest Détails :soap:Receiver

I have this problem after install the french dictionary in aspell...

I use Release 6.0.4_GA_2038.DEBIAN5 DEBIAN5 FOSS edition.

Thanks for your help.

Sam.

[ArcaneMagus]

What exactly did you change when installing the french dictionary? Can you try reversing those steps to see if logger data starts showing properly again?

[tyarmas]

Not sure if it's a red herring, but the thing that seemed to resolve my errors, which were similar, was adding memory to the Zimbra server.

I am running Zimbra on FC11 in a vmware virtual machine and did not realize that I had only allowed the virtual machine to have 1GB of RAM. I bumped the amount of RAM to 3GB and my stats problem went away and the server status is all working correctly in the admin tool.

The release notes for 6.0.4 say 2GB of RAM is required and 4GB is recommended.

Good luck.

-tom

[Samp]

Originally Posted by ArcaneMagus

What exactly did you change when installing the french dictionary? Can you try reversing those steps to see if logger data starts showing properly again?

Changed owner in all /opt/zimbra/aspell in zimbra:zimbra instead of root:root to permit install aspell files in ./aspell/lib/aspell_0.60/ with the "make install" as zimbra user.

I re-install Zimbra Release 6.0.4_GA_2038.DEBIAN5 DEBIAN5 FOSS edition, and this solve the problem, the french spell checker work too...

Thanks for your help.

Sam.

[Samp]

Originally Posted by tyarmas

Not sure if it's a red herring, but the thing that seemed to resolve my errors, which were similar, was adding memory to the Zimbra server.

I am running Zimbra on FC11 in a vmware virtual machine and did not realize that I had only allowed the virtual machine to have 1GB of RAM. I bumped the amount of RAM to 3GB and my stats problem went away and the server status is all working correctly in the admin tool.

The release notes for 6.0.4 say 2GB of RAM is required and 4GB is recommended.

Good luck.

-tom

I run Zimbra on Debian Vserver with 8Gb RAM, but after re-install Zimbra the problem was solved...

Thanks for your help.

Sam.

[Samp]

Hi,

This morning the problem back again, but nothing have changed in the config. When I check stats I got the same message as before:

Mail : system failure: Unable to read logger stats Code d'erreur : service.FAILURE Method: GetLoggerStatsRequest Détails :soap:Receiver

And each minute I got in syslog this:

Feb 3 16:00:00 zimbra zimbramon[11236]: 11236:info: zmstat df.csv: timestamp, path, disk, disk_use, disk_space, disk_pct_used:: 02/03/2010 16:00:00,
Feb 3 16:00:00 zimbra zimbramon[11325]: 11325:info: zmstat fd.csv: timestamp, fd_count:: 02/03/2010 16:00:00, 2112
Feb 3 16:00:00 zimbra zimbramon[11230]: 11230:info: zmstat cpu.csv: timestamp, cpu:user, cpu:nice, cpu:sys, cpu:idle, cpu:iowait, cpu:irq, cpu:softi
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: zmstat mysql.csv: timestamp, Aborted_clients, Aborted_connects, Binlog_cache_disk_use, Binlog_ca
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: :::2EC3600C-10DD-11DF-8E73-3A758863A44F:::, Com_purge_before_date, Com_rename_table, Com_repair,
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: :::2EC365FC-10DD-11DF-8E73-3A758863A44F::, Com_stmt_close, Com_stmt_execute, Com_stmt_fetch, C
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: :::2EC36B9C-10DD-11DF-8E73-3A758863A44F:::ed, Innodb_buffer_pool_pages_free, Innodb_buffer_pool_
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: :::2EC36DD6-10DD-11DF-8E73-3A758863A44F:::ts, Innodb_row_lock_time, Innodb_row_lock_time_avg, In
Feb 3 16:00:00 zimbra zimbramon[11364]: 11364:info: :::2EC36FF2-10DD-11DF-8E73-3A758863A44F:::_threads, Slow_queries, Sort_merge_passes, Sort_range,
Feb 3 16:00:00 zimbra zimbramon[11364]: :::2EC3720E-10DD-11DF-8E73-3A758863A44F:::5606,2,0,0,0,0,0,0,0,0,0,0,126,0,0, 0,0,0,0,49,0,0,0,0,0,0,0,0,0,0,
Feb 3 16:00:00 zimbra zimbramon[11228]: 11228:info: zmstat proc.csv: timestamp, system, user, sys, idle, iowait, mailbox, mailbox-total-cpu, mailbox
Feb 3 16:00:00 zimbra zimbramon[11228]: :::2EE71B6E-10DD-11DF-AEBA-B2748863A44F:::count, clam, clam-total-cpu, clam-utime, clam-stime, clam-totalMB,
Feb 3 16:00:01 zimbra zimbramon[11383]: 11383:info: zmstat mtaqueue.csv: timestamp, KBytes, requests:: 02/03/2010 16:00:01, 8, 2
Feb 3 16:00:01 zimbra /USR/SBIN/CRON[28804]: (zimbra) CMD (/opt/zimbra/libexec/zmqueuelog)
Feb 3 16:00:01 zimbra /USR/SBIN/CRON[28805]: (zimbra) CMD (/opt/zimbra/libexec/zmlogprocess > /tmp/logprocess.out 2>&1)
Feb 3 16:00:01 zimbra /USR/SBIN/CRON[28810]: (zimbra) CMD (/opt/zimbra/libexec/zmcheckduplicatemysqld -e > /dev/null 2>&1)
Feb 3 16:00:01 zimbra /USR/SBIN/CRON[28809]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog)
Feb 3 16:00:01 zimbra zimbramon[28804]: 28804:info: 2010-02-03 16:00:01, QUEUE: 8 2
Feb 3 16:00:04 zimbra zimbramon[28806]: 28806:info: MTA: zimbra.geismar.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,
Feb 3 16:00:04 zimbra zmmailboxdmgr[29314]: status requested
Feb 3 16:00:04 zimbra zmmailboxdmgr[29314]: status OK
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: antispam: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: antivirus: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: ldap: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: logger: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: mailbox: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: mta: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: snmp: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: spell: Running
Feb 3 16:00:04 zimbra zimbramon[28809]: 28809:info: 2010-02-03 16:00:01, STATUS: zimbra.geismar.com: stats: Running

The syslog is now more than 10Mb !

The /var/log/zimbra-stats.log is empty after the morning logrotate...

I have to run as root /opt/zimbra/bin/zmsyslogsetup to solve the problem but the Daily mail report is not run when the logger problem occured.

Release 6.0.4_GA_2038.DEBIAN5 DEBIAN5 FOSS edition.

Please help !

Sam.

[dhull]

I just upgraded to 6.0.4 and my services are all down. I only have 1.7G of RAM though. Maybe that's my problem. Would also like help on this one...

[Samp]

For the moment I fixed by add /opt/zimbra/bin/zmsyslogsetup on zimbra-stats.log :

/var/log/zimbra-stats.log {
<------>daily
<------>missingok
<------>notifempty
<------>create 0644 zimbra zimbra
<------>postrotate
<------>killall -HUP syslogd 2> /dev/null || true
<------>su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" > /dev/null 2>&1 || true
<------>/opt/zimbra/bin/zmsyslogsetup
<------>endscript
<------>rotate 0
}

I don't know if it's the best way to fix it but that's work.

Sam.

[jwhbud]

Sam,
Where exactley are you adding the stuff you said seemed to fix the problem? Are you adding it right to zimbra-stats.log?

[Samp]

Originally Posted by jwhbud

Sam,
Where exactley are you adding the stuff you said seemed to fix the problem? Are you adding it right to zimbra-stats.log?

Oh sorry I added this in /etc/logrotate.d/zimbra

Sam.