Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 42

Thread: [SOLVED] Upgrade from 4.5.6 CE to 4.5.7 CE: stats service shown as stopped

  1. #21
    bjquinn is offline Advanced Member
    Join Date
    Nov 2005
    Posts
    175
    Rep Power
    9

    Default

    For what it's worth, I'll just post a "me too".

    Fresh install of 4.5.7, not an upgrade
    CentOS5

    I did a yum install sysstat which seemed to make zmcontrol status show the stats service as running.

    However, I still have the problems mentioned by everyone else, namely -

    1. I only seem to get anything interesting in the Admin interface stats page if I run zmgengraphs and such by hand, and even then I don't seem to get everything.

    2. I *NEVER* get any AS/AV stats. Sadly, that's really one of the main reasons I was upgrading to Zimbra was to improve spam blocking and to keep track of those kinds of stats better.

    Surely they can't only put the fix in 5.0? An upgrade is far too dangerous and time-consuming for me to do right after upgrading to 4.5.7 just recently!

  2. #22
    mikets is offline Active Member
    Join Date
    May 2006
    Posts
    41
    Rep Power
    9

  3. #23
    cvidal is offline Project Contributor
    Join Date
    Dec 2005
    Posts
    150
    Rep Power
    9

    Default Q&D Fix

    It looks like a path problem. If you run:

    /opt/zimbra/libexec/zmstatuslog

    as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

    The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

    Code:
    */2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog
    That's it! :-)

    Carlos
    Last edited by cvidal; 09-28-2007 at 01:28 PM.

  4. #24
    centrex is offline Special Member
    Join Date
    Aug 2007
    Posts
    100
    Rep Power
    7

    Default

    Quote Originally Posted by cvidal View Post
    It looks like a path problem. If you run:

    /opt/zimbra/libexec/zmstatuslog

    as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

    The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

    Code:
    */2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog
    That's it! :-)

    Carlos
    Excellent workaround Carlos, I implemented it now and so far, so good Service is showing as running now in admin console. Tomorrow I will know if the stats are logging correctly..

  5. #25
    centrex is offline Special Member
    Join Date
    Aug 2007
    Posts
    100
    Rep Power
    7

    Default

    Carlos' fix works!

    But now that stats are running again, a new issue has been revealed: The most important (to me) tab, "Anti-Spam/Anti-Virus Activity" is not being populated.

    There must be another glitch in 4.5.7 somewhere.

    Can anyone tell me which script gathers data for this tab ?

  6. #26
    cvidal is offline Project Contributor
    Join Date
    Dec 2005
    Posts
    150
    Rep Power
    9

    Default

    Quote Originally Posted by centrex View Post
    Carlos' fix works!

    But now that stats are running again, a new issue has been revealed: The most important (to me) tab, "Anti-Spam/Anti-Virus Activity" is not being populated.

    There must be another glitch in 4.5.7 somewhere.

    Can anyone tell me which script gathers data for this tab ?
    May be you don't receive any spam at all!

    Jokes appart, the script responsible for generating the graphs is called zmgengraphs and is also triggered by cron every 10 minutes. Here the script behavior is the same when you run it manually, so the previous fix doesn't work in this case :-(

    Looking at the code, I see the graphs are generating by querying MySQL (the zimbra_logger database). Looking at the database I see that the counts are in zero and no stats are grabbed, so the bug is in the data grabbing process (swatch?).

    Looking in bugzilla, there is already an open item (bug 20578).

    Carlos
    Last edited by cvidal; 09-30-2007 at 03:52 AM.

  7. #27
    centrex is offline Special Member
    Join Date
    Aug 2007
    Posts
    100
    Rep Power
    7

    Default

    Quote Originally Posted by cvidal View Post
    Looking in bugzilla, there is already an open item (bug 20578).

    Carlos
    20578 indeed looks like my thing. I voted for it. Good find

  8. #28
    randall is offline Advanced Member
    Join Date
    Jun 2007
    Location
    Philippines
    Posts
    193
    Rep Power
    8

    Default

    Quote Originally Posted by cvidal View Post
    It looks like a path problem. If you run:

    /opt/zimbra/libexec/zmstatuslog

    as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

    The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

    Code:
    */2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog
    That's it! :-)

    Carlos
    Is this one specific to OS? I'm using Ubuntu 6.06, and I tried the same line, but it's not working.

    Any idea?

    Thanks in advance.

  9. #29
    fisch09 is offline Special Member
    Join Date
    Dec 2006
    Location
    Melbourne, VIC, Australia
    Posts
    120
    Rep Power
    8

    Default ~/.bashrc

    Hi,

    I also came across the issue with cron / .bashrc .
    I wrote some scripts that worked fine when run as user zimbra from the command line but did not work from cron. Adding a "source ~/.bashrc" as first line into this scripts fixed this. OS is as well Ubuntu 6.06.

    Kind Regards
    Andre

  10. #30
    randall is offline Advanced Member
    Join Date
    Jun 2007
    Location
    Philippines
    Posts
    193
    Rep Power
    8

    Default

    Quote Originally Posted by fisch09 View Post
    Hi,

    I also came across the issue with cron / .bashrc .
    I wrote some scripts that worked fine when run as user zimbra from the command line but did not work from cron. Adding a "source ~/.bashrc" as first line into this scripts fixed this. OS is as well Ubuntu 6.06.

    Kind Regards
    Andre
    Thanks for the post Andre.

    Should I add that script to the crontab or to the .bashrc?

    Many thanks again.

Page 3 of 5 FirstFirst 12345 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. 4.0.4 to 4.5.6 upgrade failed in network edition
    By chenthil in forum Administrators
    Replies: 1
    Last Post: 08-27-2007, 09:36 AM
  2. Replies: 6
    Last Post: 07-04-2007, 08:36 AM
  3. Web client logon fails (INVALID_PDU)
    By jermxx in forum Installation
    Replies: 8
    Last Post: 02-20-2007, 02:20 PM
  4. Tomcat broken after upgrade to 4
    By dotslashroot in forum Migration
    Replies: 13
    Last Post: 01-31-2007, 06:05 PM
  5. MTA Service Stopped
    By Ryan Frantz in forum Administrators
    Replies: 7
    Last Post: 11-23-2005, 02:03 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •