Page 3 of 7 FirstFirst 12345 ... LastLast
Results 21 to 30 of 64

Thread: No data in server statistics

  1. #21
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Rob, What does your zimbra crontab look like? Is swatch running?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  2. #22
    rhostager is offline Senior Member
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    9

    Default

    Quote Originally Posted by KevinH
    Rob, What does your zimbra crontab look like? Is swatch running?
    Here is the crontab for zimbra:

    [root@mail01 ~]# crontab -u zimbra -l
    # ZIMBRASTART -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRAEND
    #
    # Log pruning
    #
    30 2 * * * find /opt/zimbra/log/ -type f -name \*log\* -mtime +8 -daystart -exec rm {} \; > /dev/null 2>&1
    30 2 * * * find /opt/zimbra/tomcat/logs/ -type f -name \*log\* -mtime +8 -daystart -exec rm {} \; > /dev/null 2>&1
    0 2 * * * /opt/zimbra/bin/zmroll_catalina.sh > /dev/null 2>&1
    #
    # Status logging
    #
    * * * * * /opt/zimbra/bin/zmstatuslog
    */10 * * * * /opt/zimbra/bin/zmdisklog
    #
    # crontab.store
    #
    # Purge messages
    #
    0 3 * * * /opt/zimbra/bin/zmpurgemessages > /dev/null 2>&1
    #
    # Clean up the quarantine dir
    #
    0 1 * * * find /opt/zimbra/amavisd/quarantine -type f -mtime +7 -exec rm -f {} \; > /dev/null 2>&1
    #
    # Table maintenance
    #
    30 1 * * * /opt/zimbra/bin/zmmaintaintables >> /dev/null 2>&1
    # BACKUP BEGIN
    # BACKUP END
    #
    # crontab.logger
    #
    # process logs
    #
    00,10,20,30,40,50 * * * * /opt/zimbra/bin/zmlogprocess > /tmp/logprocess.out 2>&1
    #
    # Graph generation
    #
    10 * * * * /opt/zimbra/bin/zmgengraphs >> /tmp/gengraphs.out 2>&1
    #
    # crontab.mta
    #
    #
    # Queue logging
    #
    */10 * * * * /opt/zimbra/bin/zmqueuelog
    # ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART



    I see logswatch running on 2 processes.

    - Rob

  3. #23
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Anything if you run this manually: /opt/zimbra/bin/zmlogprocess
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  4. #24
    vogon1 is offline Active Member
    Join Date
    Oct 2005
    Posts
    39
    Rep Power
    9

    Default

    There is also logrotate that does some killing, see http://bugzilla.zimbra.com/show_bug.cgi?id=5824

  5. #25
    rhostager is offline Senior Member
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    9

    Default

    Quote Originally Posted by KevinH
    Anything if you run this manually: /opt/zimbra/bin/zmlogprocess
    Here is the output:

    [zimbra@mail01 ~]$ /opt/zimbra/bin/zmlogprocess
    Processing mta entries from 0
    Found 1 messages
    Inserted 1 rows
    Saving ID 0
    Deleting processed postfix logs from raw_logs...Done
    Processing clamd entries from 6280
    Found 0 entries
    Deleting processed clamd logs from raw_logs...Done
    Processing amavis entries from 6111
    Found 0 entries
    Deleting processed amavis logs from raw_logs...Done
    Processing sendmail entries from 5027
    Found 0 entries
    Deleting processed sendmail logs from raw_logs...Done
    Processing zimbramon entries from 6317
    Found 0 entries
    Deleting processed zimbramon logs from raw_logs...Done
    Aggregating hour mta from 2006-02-03 00:00:00 to 2006-02-03 01:00:00
    Aggregating hour mta from 2006-02-03 01:00:00 to 2006-02-03 02:00:00
    Aggregating hour mta from 2006-02-03 02:00:00 to 2006-02-03 03:00:00
    Aggregating hour mta from 2006-02-03 03:00:00 to 2006-02-03 04:00:00
    Aggregating hour mta from 2006-02-03 04:00:00 to 2006-02-03 05:00:00
    Aggregating hour mta from 2006-02-03 05:00:00 to 2006-02-03 06:00:00
    Aggregating hour mta from 2006-02-03 06:00:00 to 2006-02-03 07:00:00
    Aggregating hour mta from 2006-02-03 07:00:00 to 2006-02-03 08:00:00
    Aggregating hour mta from 2006-02-03 08:00:00 to 2006-02-03 09:00:00
    Aggregating hour mta from 2006-02-03 09:00:00 to 2006-02-03 10:00:00
    Aggregating hour mta from 2006-02-03 10:00:00 to 2006-02-03 11:00:00
    Aggregating hour mta from 2006-02-03 11:00:00 to 2006-02-03 12:00:00
    Aggregating hour mta from 2006-02-03 12:00:00 to 2006-02-03 13:00:00
    Aggregating hour mta from 2006-02-03 13:00:00 to 2006-02-03 14:00:00
    Aggregating hour mta from 2006-02-03 14:00:00 to 2006-02-03 15:00:00
    Aggregating hour mta from 2006-02-03 15:00:00 to 2006-02-03 16:00:00
    Aggregating hour mta from 2006-02-03 16:00:00 to 2006-02-03 17:00:00
    Aggregating hour mta from 2006-02-03 17:00:00 to 2006-02-03 18:00:00
    Aggregating day mta from 2006-02-02 00:00:00 to 2006-02-03 00:00:00
    Aggregating hour amavis from 2006-02-03 00:00:00 to 2006-02-03 01:00:00
    Aggregating hour amavis from 2006-02-03 01:00:00 to 2006-02-03 02:00:00
    Aggregating hour amavis from 2006-02-03 02:00:00 to 2006-02-03 03:00:00
    Aggregating hour amavis from 2006-02-03 03:00:00 to 2006-02-03 04:00:00
    Aggregating hour amavis from 2006-02-03 04:00:00 to 2006-02-03 05:00:00
    Aggregating hour amavis from 2006-02-03 05:00:00 to 2006-02-03 06:00:00
    Aggregating hour amavis from 2006-02-03 06:00:00 to 2006-02-03 07:00:00
    Aggregating hour amavis from 2006-02-03 07:00:00 to 2006-02-03 08:00:00
    Aggregating hour amavis from 2006-02-03 08:00:00 to 2006-02-03 09:00:00
    Aggregating hour amavis from 2006-02-03 09:00:00 to 2006-02-03 10:00:00
    Aggregating hour amavis from 2006-02-03 10:00:00 to 2006-02-03 11:00:00
    Aggregating hour amavis from 2006-02-03 11:00:00 to 2006-02-03 12:00:00
    Aggregating hour amavis from 2006-02-03 12:00:00 to 2006-02-03 13:00:00
    Aggregating hour amavis from 2006-02-03 13:00:00 to 2006-02-03 14:00:00
    Aggregating hour amavis from 2006-02-03 14:00:00 to 2006-02-03 15:00:00
    Aggregating hour amavis from 2006-02-03 15:00:00 to 2006-02-03 16:00:00
    Aggregating hour amavis from 2006-02-03 16:00:00 to 2006-02-03 17:00:00
    Aggregating hour amavis from 2006-02-03 17:00:00 to 2006-02-03 18:00:00
    Aggregating day amavis from 2006-02-02 00:00:00 to 2006-02-03 00:00:00
    Aggregating hour disk from 2006-02-03 00:00:00 to 2006-02-03 01:00:00
    Aggregating hour disk from 2006-02-03 01:00:00 to 2006-02-03 02:00:00
    Aggregating hour disk from 2006-02-03 02:00:00 to 2006-02-03 03:00:00
    Aggregating hour disk from 2006-02-03 03:00:00 to 2006-02-03 04:00:00
    Aggregating hour disk from 2006-02-03 04:00:00 to 2006-02-03 05:00:00
    Aggregating hour disk from 2006-02-03 05:00:00 to 2006-02-03 06:00:00
    Aggregating hour disk from 2006-02-03 06:00:00 to 2006-02-03 07:00:00
    Aggregating hour disk from 2006-02-03 07:00:00 to 2006-02-03 08:00:00
    Aggregating hour disk from 2006-02-03 08:00:00 to 2006-02-03 09:00:00
    Aggregating hour disk from 2006-02-03 09:00:00 to 2006-02-03 10:00:00
    Aggregating hour disk from 2006-02-03 10:00:00 to 2006-02-03 11:00:00
    Aggregating hour disk from 2006-02-03 11:00:00 to 2006-02-03 12:00:00
    Aggregating hour disk from 2006-02-03 12:00:00 to 2006-02-03 13:00:00
    Aggregating hour disk from 2006-02-03 13:00:00 to 2006-02-03 14:00:00
    Aggregating hour disk from 2006-02-03 14:00:00 to 2006-02-03 15:00:00
    Aggregating hour disk from 2006-02-03 15:00:00 to 2006-02-03 16:00:00
    Aggregating hour disk from 2006-02-03 16:00:00 to 2006-02-03 17:00:00
    Aggregating hour disk from 2006-02-03 17:00:00 to 2006-02-03 18:00:00
    Aggregating day disk from 2006-02-02 00:00:00 to 2006-02-03 00:00:00
    RAW: 31
    SUM: 730
    Pruning raw mta logs from 2006-01-03 00:00:00
    Pruning raw amavis logs from 2006-01-03 00:00:00
    Pruning raw disk logs from 2006-01-03 00:00:00
    Pruning summary mta logs from 2004-02-04 00:00:00
    Pruning summary amavis logs from 2004-02-04 00:00:00
    Pruning summary disk logs from 2004-02-04 00:00:00
    [zimbra@mail01 ~]$


    "Found 0 entries" does not sound good.

    - Rob

  6. #26
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Any of the info here help:

    statistics and monitoring
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  7. #27
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default syslog

    Logger is running on this host, right? And swatch is watching /var/log/zimbra.log? Is this a single host install?

  8. #28
    nathans is offline Junior Member
    Join Date
    Jan 2006
    Posts
    5
    Rep Power
    9

    Default

    I've got an always-empty mta_aggregate table too, and no information on the server status or statistics pages.

    Quote Originally Posted by KevinH
    Anything if you run this manually: /opt/zimbra/bin/zmlogprocess
    When I run the script manually, this is part of the output:

    RAW: 31
    SUM: 730

    But, in /tmp/logprocess.out, there is this instead:

    sh: zmprov: command not found
    RAW:
    sh: zmprov: command not found
    SUM:

    If I'm reading the zmlogprocess code correctly, this means that $rawBegin and $summaryBegin get set to $now, so the script removes basically all log entries from the database.

  9. #29
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default sounds like a bug

    sounds like my bug, to be specific. I remember traffic about using full pathnames in that script, but I'm not sure if I made the code change yet or not. I'll check that out on monday - but you should edit your logprocess script to fully path all the zm* commands.

  10. #30
    nathans is offline Junior Member
    Join Date
    Jan 2006
    Posts
    5
    Rep Power
    9

    Default aha! syslog-ng

    Silly me, I'd forgotten my box with this issue is running SuSE 10, to try out the community edition. That means it's running syslog-ng by default, unlike a RHEL system. Nothing was actually getting written to /var/log/zimbra.log.

    In addition to making that edit to the zmlogprocess script, I added a few lines to /etc/syslog-ng/syslog-ng.conf and sent a HUP to syslog-ng, and now /var/log/zimbra.log is really getting used and data is showing up in the mysql tables.

    filter f_zimbra { facility(local0, mail); };
    destination zimbralog { file("/var/log/zimbra.log" owner(zimbra)); };
    log {source(src); filter(f_zimbra); destination(zimbralog); };

Page 3 of 7 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. initializing ldap...FAILED(256)ERROR
    By manjunath in forum Installation
    Replies: 39
    Last Post: 06-07-2013, 10:27 AM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. need advice on configuring zimbra to work with fax server
    By pheonix1t in forum Administrators
    Replies: 0
    Last Post: 07-11-2007, 07:46 PM
  4. Replies: 1
    Last Post: 04-25-2007, 07:12 AM
  5. Error 256 on Installation
    By RuinExplorer in forum Installation
    Replies: 5
    Last Post: 10-19-2006, 09:19 AM

Posting Permissions

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