Page 5 of 7 FirstFirst ... 34567 LastLast
Results 41 to 50 of 64

Thread: No data in server statistics

  1. #41
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    10

    Default

    Quote Originally Posted by marcmac
    Anything in /opt/zimbra/log/logmysqld.log?

    I can't tell, from what you've posted, if it's failing to connect due to permissions, or something else (something wrong with the perl libs, perhaps?)

    Does stoppping/starting the logger db have any effect?

    logmysqld.log does not exist. logger_mysqld.log has no errors in it.

    I have restarted the server several times with no change. How do you start/stop the logger db?

    - Rob

  2. #42
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default zmloggerctl

    zmloggerctl stop/start will stop the db and the swatch process

  3. #43
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default debugging output

    You may want to add a print statement to logprocess script to output the connection info to verify it's getting the right data. compare to zmlocalconfig -s (-s == show passwords).

    Also - the zmlogger script is the one that does the db inserts - it's launched from swatch. Any errors related to it in /tmp/logswatch.out?

  4. #44
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    10

    Default

    Quote Originally Posted by marcmac
    zmloggerctl stop/start will stop the db and the swatch process
    No errors to the console when I did this. /tmp/logprocess.out no longer has the connect errors and seems to be processing the logs. I still only have graphs for Anti-Spam/Anti-Virus Activity. All other graphs are "Data not available".

    The files and subdirectories under /opt/zimbra seem to have a mix of owership between root and zimbra. For example, all of the items under /opt/zimbra/bin are owned by root. Is this normal?

    - Rob

  5. #45
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    10

    Default

    Quote Originally Posted by marcmac
    You may want to add a print statement to logprocess script to output the connection info to verify it's getting the right data. compare to zmlocalconfig -s (-s == show passwords).

    Also - the zmlogger script is the one that does the db inserts - it's launched from swatch. Any errors related to it in /tmp/logswatch.out?

    No errors in logswatch.out.

    - Rob

  6. #46
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default errors

    anything interesting when you have logprocess print out the connection info?

  7. #47
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    10

    Default

    Quote Originally Posted by marcmac
    anything interesting when you have logprocess print out the connection info?
    The connection info seems to be correct (user id and passwords match) and zmlogprocess seems to be working but no go on the graphs.

    - Rob

  8. #48
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default long thread - recap

    To recap:
    you get AV/AS data, but nothing for message count or message volume? Is this true of the per server stats as well as the systemwide graphs?

    zmlogprocess WAS logging connection errors, but no longer is?

    Let's try this:

    edit /opt/zimbra/bin/zmlogger, and set DEBUG=1 on line 111. Stop ant start the logger (zmloggerctl), send a few messages through the MTA, and then stop the logger again.

    What's in /tmp/zmlogger.out?

    Also - try this:
    logger -p mail.info "testing"

    Check to make sure the line "testing" got logged to /var/log/zimbra.log

  9. #49
    Join Date
    Nov 2005
    Posts
    61
    Rep Power
    10

    Default

    Quote Originally Posted by marcmac
    To recap:
    you get AV/AS data, but nothing for message count or message volume? Is this true of the per server stats as well as the systemwide graphs?
    The ONLY graphs I get are under AV/AS on the systemwide page.

    Quote Originally Posted by marcmac
    zmlogprocess WAS logging connection errors, but no longer is?
    I got the errors again complaining about the socket but don't know if that happened during the start/stop process:

    DBI connect('database=zimbra_logger;mysql_read_default _file=/opt/zimbra/conf/my.
    logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock','zimbra',...) failed:
    Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.
    sock' (2) at /opt/zimbra/bin/zmlogprocess line 63
    DB: Can't connect to dbi:mysql:database=zimbra_logger;mysql_read_defaul t_file=/o
    pt/zimbra/conf/my.logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock: Can'
    t connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock
    ' (2)

    I restarted the server and now have normal processing messages in logprocess.out:

    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 10143
    Found 0 entries
    Deleting processed clamd logs from raw_logs...Done
    Processing amavis entries from 10122
    Found 0 entries
    Deleting processed amavis logs from raw_logs...Done
    Processing sendmail entries from 8410
    Found 0 entries
    Deleting processed sendmail logs from raw_logs...Done
    Processing zimbramon entries from 10161
    Found 3 entries
    Saving ID 10172
    Deleting processed zimbramon logs from raw_logs...Done
    Aggregating hour mta from 2006-02-08 00:00:00 to 2006-02-08 01:00:00
    Aggregating hour mta from 2006-02-08 01:00:00 to 2006-02-08 02:00:00
    Aggregating hour mta from 2006-02-08 02:00:00 to 2006-02-08 03:00:00
    Aggregating hour mta from 2006-02-08 03:00:00 to 2006-02-08 04:00:00
    Aggregating hour mta from 2006-02-08 04:00:00 to 2006-02-08 05:00:00
    Aggregating hour mta from 2006-02-08 05:00:00 to 2006-02-08 06:00:00
    Aggregating hour mta from 2006-02-08 06:00:00 to 2006-02-08 07:00:00
    Aggregating hour mta from 2006-02-08 07:00:00 to 2006-02-08 08:00:00
    Aggregating hour mta from 2006-02-08 08:00:00 to 2006-02-08 09:00:00
    Aggregating hour mta from 2006-02-08 09:00:00 to 2006-02-08 10:00:00
    Aggregating hour mta from 2006-02-08 10:00:00 to 2006-02-08 11:00:00
    Aggregating hour mta from 2006-02-08 11:00:00 to 2006-02-08 12:00:00
    Aggregating hour mta from 2006-02-08 12:00:00 to 2006-02-08 13:00:00
    Aggregating hour mta from 2006-02-08 13:00:00 to 2006-02-08 14:00:00
    Aggregating hour mta from 2006-02-08 14:00:00 to 2006-02-08 15:00:00
    Aggregating hour mta from 2006-02-08 15:00:00 to 2006-02-08 16:00:00
    Aggregating hour mta from 2006-02-08 16:00:00 to 2006-02-08 17:00:00
    Aggregating hour mta from 2006-02-08 17:00:00 to 2006-02-08 18:00:00
    Aggregating day mta from 2006-02-07 00:00:00 to 2006-02-08 00:00:00
    Aggregating hour amavis from 2006-02-08 17:00:00 to 2006-02-08 18:00:00
    Aggregating day amavis from 2006-02-07 00:00:00 to 2006-02-08 00:00:00
    Aggregating hour disk from 2006-02-08 00:00:00 to 2006-02-08 01:00:00
    Aggregating hour disk from 2006-02-08 01:00:00 to 2006-02-08 02:00:00
    Aggregating hour disk from 2006-02-08 02:00:00 to 2006-02-08 03:00:00
    Aggregating hour disk from 2006-02-08 03:00:00 to 2006-02-08 04:00:00
    Aggregating hour disk from 2006-02-08 04:00:00 to 2006-02-08 05:00:00
    Aggregating hour disk from 2006-02-08 05:00:00 to 2006-02-08 06:00:00
    Aggregating hour disk from 2006-02-08 06:00:00 to 2006-02-08 07:00:00
    Aggregating hour disk from 2006-02-08 07:00:00 to 2006-02-08 08:00:00
    Aggregating hour disk from 2006-02-08 08:00:00 to 2006-02-08 09:00:00
    Aggregating hour disk from 2006-02-08 09:00:00 to 2006-02-08 10:00:00
    Aggregating hour disk from 2006-02-08 10:00:00 to 2006-02-08 11:00:00
    Aggregating hour disk from 2006-02-08 11:00:00 to 2006-02-08 12:00:00
    Aggregating hour disk from 2006-02-08 12:00:00 to 2006-02-08 13:00:00
    Aggregating hour disk from 2006-02-08 13:00:00 to 2006-02-08 14:00:00
    Aggregating hour disk from 2006-02-08 14:00:00 to 2006-02-08 15:00:00
    Aggregating hour disk from 2006-02-08 15:00:00 to 2006-02-08 16:00:00
    Aggregating hour disk from 2006-02-08 16:00:00 to 2006-02-08 17:00:00
    Aggregating hour disk from 2006-02-08 17:00:00 to 2006-02-08 18:00:00
    Aggregating day disk from 2006-02-07 00:00:00 to 2006-02-08 00:00:00
    RAW: 31
    SUM: 730
    Pruning raw mta logs from 2006-01-08 00:00:00
    Pruning raw amavis logs from 2006-01-08 00:00:00
    Pruning raw disk logs from 2006-01-08 00:00:00
    Pruning summary mta logs from 2004-02-09 00:00:00
    Pruning summary amavis logs from 2004-02-09 00:00:00
    Pruning summary disk logs from 2004-02-09 00:00:00
    Pruning other raw logs from 2006-01-08 00:00:00


    Quote Originally Posted by marcmac
    Let's try this:

    edit /opt/zimbra/bin/zmlogger, and set DEBUG=1 on line 111. Stop ant start the logger (zmloggerctl), send a few messages through the MTA, and then stop the logger again.

    What's in /tmp/zmlogger.out?

    Also - try this:
    logger -p mail.info "testing"

    Check to make sure the line "testing" got logged to /var/log/zimbra.log

    /tmp/zmlogger.out has:

    45717811063380 zmlogger starting up

    testing gets logged to zimbra.log

    BTW: I upgraged to the GA version and had to re-enter the zmprov full paths.

    - Rob

  10. #50
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default logging

    Now that we know that the pieces appear to be working - run some mail through the system, and check to see if the mta stuff ends up in raw_logs.

    If it does, then the problem is in logprocess.

    If it does not, then we need to look at zmlogger.

Similar Threads

  1. initializing ldap...FAILED(256)ERROR
    By manjunath in forum Installation
    Replies: 39
    Last Post: 06-07-2013, 11:27 AM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 01: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, 08:46 PM
  4. Replies: 1
    Last Post: 04-25-2007, 08:12 AM
  5. Error 256 on Installation
    By RuinExplorer in forum Installation
    Replies: 5
    Last Post: 10-19-2006, 10: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
  •