Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: status not updating properly

Hybrid View

  1. #1
    Join Date
    Jul 2008
    Location
    Corvallis, OR
    Posts
    54
    Rep Power
    7

    Default status not updating properly

    I've got a problem where the service status is not getting updated properly; logswatch and swatch are running:


    0 31582 18076 1 16 0 6720 4804 wait S ? 0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/
    0 31582 18085 18076 18 0 8744 6768 pipe_w S ? 2:27 /usr/bin/perl /tmp/.swatch_script.18076
    0 31582 18093 18085 15 0 8928 4768 - S ? 7:33 /usr/bin/perl /opt/zimbra/libexec/zmlogger
    0 31582 18351 1 19 0 6728 4820 wait S ? 0:00 /usr/bin/perl /opt/zimbra/libexec/swatch --config-file=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log
    0 31582 18372 18351 15 0 8884 6776 - S ? 1:20 /usr/bin/perl /tmp/.swatch_script.18351


    In looking at the code for zmlogger, I see that it's looking at the STATUS lines in /var/log/zimbra.log, and those are updating properly:


    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: imapproxy: Running
    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: logger: Running
    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: mailbox: Running
    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: snmp: Running
    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: spell: Running
    Apr 17 18:06:19 zmail01-store01 zimbramon[16128]: 16128:info: 2009-04-17 18:06:01, STATUS: zmail01-store01.server.peak.org: stats: Running


    but the database is not being updated:


    mysql> select * from service_status;
    +---------------------------------+-----------+---------------------+--------+-----------------+
    | server | service | time | status | loghostname |
    +---------------------------------+-----------+---------------------+--------+-----------------+
    | zmail01-store01.server.peak.org | stats | 2009-04-17 10:20:03 | 1 | zmail01-store01 |
    | zmail01-store01.server.peak.org | spell | 2009-04-17 10:20:03 | 1 | zmail01-store01 |
    | zmail01-store01.server.peak.org | snmp | 2009-04-17 10:20:03 | 1 | zmail01-store01 |
    | zmail01-store01.server.peak.org | mailbox | 2009-04-17 10:20:03 | 1 | zmail01-store01 |
    | zmail01-store01.server.peak.org | logger | 2009-04-17 10:20:03 | 1 | zmail01-store01 |
    | zmail01-store01.server.peak.org | imapproxy | 2009-04-17 10:20:03 | 1 | zmail01-store01 |


    I'm turning on debug in zmlogger, but thought I would post here now in case something like this has been seen before...

  2. #2
    Join Date
    Jul 2008
    Location
    Corvallis, OR
    Posts
    54
    Rep Power
    7

    Default

    When I restarted zimbra to get the zmlogger debug to take effect, the service status updated as I expected it would, however the web page still says "data is stale" after all the entries, even though the time stamps are within a couple minutes of current???

  3. #3
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    Code:
    su - zimbra
    logmysql
    use zimbra_logger;
    select * from mta order by arrive_time desc limit 10;
    Are you seeing upto date data ??

  4. #4
    Join Date
    Jun 2008
    Posts
    45
    Rep Power
    7

    Default

    Quote Originally Posted by uxbod View Post
    Code:
    su - zimbra
    logmysql
    use zimbra_logger;
    select * from mta order by arrive_time desc limit 10;
    Are you seeing upto date data ??
    We're having the exact same problem with our server, and running this showed that the stats haven't been updated since Dec. 6th, 2008. Is there a way to flush this out and get the stats updated again?

    Thanks!
    OS : Ubuntu 6.02 LTS
    ZCS : zcs-NETWORK-6.0.8_GA_2661.UBUNTU6

  5. #5
    Join Date
    Jul 2008
    Location
    openhagen
    Posts
    81
    Rep Power
    7

    Default

    We were having the excact same issue but found out that the cron daemon wasn't running. Backups were not done either

  6. #6
    Join Date
    Jun 2008
    Posts
    45
    Rep Power
    7

    Default

    I did some reading on Logger - Zimbra :: Wiki
    And took the advice of checking the mysql tables.

    Here's the output:
    Code:
    mysql> check table raw_logs;
    +------------------------+-------+----------+-------------------------------------------------------------------------------+
    | Table                  | Op    | Msg_type | Msg_text                                                                      |
    +------------------------+-------+----------+-------------------------------------------------------------------------------+
    | zimbra_logger.raw_logs | check | warning  | Table is marked as crashed                                                    |
    | zimbra_logger.raw_logs | check | warning  | 3 clients are using or haven't closed the table properly                      |
    | zimbra_logger.raw_logs | check | error    | Can't read key from filepos: 3407872                                          |
    | zimbra_logger.raw_logs | check | Error    | Incorrect key file for table './zimbra_logger/raw_logs.MYI'; try to repair it |
    | zimbra_logger.raw_logs | check | error    | Corrupt                                                                       |
    +------------------------+-------+----------+-------------------------------------------------------------------------------+
    5 rows in set (0.36 sec)

    I then did a

    Code:
    repair table raw_logs;
    And it's been running that for almost 30 minutes now...was that a bad idea?
    OS : Ubuntu 6.02 LTS
    ZCS : zcs-NETWORK-6.0.8_GA_2661.UBUNTU6

  7. #7
    Join Date
    Jun 2008
    Posts
    45
    Rep Power
    7

    Default

    So after 2 hours I got this

    Code:
    mysql> repair table raw_logs;
    
    +------------------------+--------+----------+--------------------------------------------------+
    | Table                  | Op     | Msg_type | Msg_text                                         |
    +------------------------+--------+----------+--------------------------------------------------+
    | zimbra_logger.raw_logs | repair | warning  | Number of rows changed from 21425438 to 18347072 |
    | zimbra_logger.raw_logs | repair | status   | OK                                               |
    +------------------------+--------+----------+--------------------------------------------------+
    2 rows in set (1 hour 58 min 54.17 sec)
    OS : Ubuntu 6.02 LTS
    ZCS : zcs-NETWORK-6.0.8_GA_2661.UBUNTU6

  8. #8
    Join Date
    Jun 2008
    Posts
    45
    Rep Power
    7

    Default

    I thought maybe upgrading from 5.0.13 to 5.0.15 might fix up my issues, but from the output below it looks like I have a deeper problem. Has anyone else experienced the logger errors I'm having and the association to no stats being displayed?

    Code:
    Do you want to verify logger database integrity? [Y]
    Verifying integrity of logger database.  This may take a while.
    mysqld is alive
    Generating report
    Logger Database errors found.
    /opt/zimbra/logger/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.logger.cnf -S /opt/zimbra/logger/db/mysql.sock -A -C -s -u root --password=.***omited** --auto-repair
    zimbra_logger.mta
     warning  : 2 clients are using or haven't closed the table properly
     zimbra_logger.processing_history
     warning  : 3 clients are using or haven't closed the table properly
     zimbra_logger.service_status
     warning  : 6 clients are using or haven't closed the table properly
    OS : Ubuntu 6.02 LTS
    ZCS : zcs-NETWORK-6.0.8_GA_2661.UBUNTU6

  9. #9
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    Code:
    su - zimbra
    logmysql
    use zimbra_logger;
    repair table mta;
    repair table processing_history;
    repair table service_status;
    exit

  10. #10
    Join Date
    Jun 2008
    Posts
    45
    Rep Power
    7

    Default

    uxbod thanks for the quick reply, I performed those commands on the database, and restarted the services. I still however do not see any stats on the Mesage Count, Message Volume, or AS/AV tabs. I've read else where that it does take some time for them to refresh.
    OS : Ubuntu 6.02 LTS
    ZCS : zcs-NETWORK-6.0.8_GA_2661.UBUNTU6

Similar Threads

  1. [SOLVED] mysql.server not running
    By king0770 in forum Administrators
    Replies: 23
    Last Post: 07-25-2009, 04:07 PM
  2. Error after installation
    By robsontuxlinux in forum Installation
    Replies: 13
    Last Post: 09-11-2008, 10:48 PM
  3. zmmailboxdctl is stopped frequently..
    By tamilnandhu in forum Installation
    Replies: 13
    Last Post: 04-12-2008, 09:59 AM
  4. postfix build error while building Zimbra source
    By anuradha_mihsra in forum Developers
    Replies: 6
    Last Post: 07-19-2007, 11:22 AM
  5. Trouble sending mail from Outlook
    By czaveri in forum Users
    Replies: 15
    Last Post: 07-24-2006, 12:01 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
  •