Page 4 of 7 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 63

Thread: upgrade to 6.0.2 stats and status no longer working

  1. #31
    Join Date
    Jan 2008
    Posts
    62
    Rep Power
    7

    Default

    What stops at 6:24am? the zmlogger process? Is it still running?

    Do you have a stack trace from /opt/zimbra/log/mailbox.log of when you get the server error?


    Quote Originally Posted by HidX View Post
    I understand.
    Actually I came to where to begin my problem.

    After these operations (as "root"), statistics earned:

    Code:
    /etc/init.d/zimbra stop
    /opt/zimbra/bin/zmsyslogsetup 
    /etc/init.d/rsyslog restart 
    /opt/zimbra/libexec/zmfixperms 
    /etc/init.d/zimbra start
    In the file "/etc/rsyslog.conf", add the following lines:

    Code:
    daemon.*;mail.*;\
            news.err;\
            *.=debug;*.=info;\
            *.=notice;*.=warn       |/dev/xconsole
    local0.*                -/var/log/zimbra.log
    local1.*                -/var/log/zimbra-stats.log
    auth.*                  -/var/log/zimbra.log
    mail.*                -/var/log/zimbra.log

    and in the log "/var/log/zimbra-stats.log" began to receive data.
    The directory "/opt/zimbra/ logger" AK is beginning to fill with data (before she ever took 44kb).

    But the statistics still show stops at exactly 6:24 am Moscow time:



    It is not critical, but not pleasant.

  2. #32
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    53
    Rep Power
    6

    Default

    Quote Originally Posted by pfnguyen View Post
    What stops at 6:24am? the zmlogger process? Is it still running?

    Do you have a stack trace from /opt/zimbra/log/mailbox.log of when you get the server error?
    No. All services are quietly working. And "zmlogger" including.
    Even the statistics seem to continue to write.

    Not show itself statistics, in the section administrator. Including and not see the status of services (in the admin section), showing red crosses, and reported that the data are outdated.

    In logs:
    Code:
    cat /opt/zimbra/log/mailbox.log.2009-11-23 | grep WARN
    2009-11-23 00:43:56,519 WARN  [Shutdown] [] ZimbraHttpConnectionManager - shutting down http client idle connection reaper thread
    2009-11-23 00:45:47,734 WARN  [main] [] log - No value for env-entry-name trustedIPs
    2009-11-23 22:29:07,810 WARN  [ScheduledTask-9] [name=bmw@domen.ru;mid=3;ds=RSS-12492;] datasource - Scheduled DataSource import failed.
    
    
    cat /opt/zimbra/log/mailbox.log.2009-11-23 | grep error
    There is nothing about this problems.

  3. #33
    Join Date
    Jan 2008
    Posts
    62
    Rep Power
    7

    Default

    grep Exception, not grep error (and if you do find any related to logger--particularly GetLoggerStats, please post context).

    Quote Originally Posted by HidX View Post
    No. All services are quietly working. And "zmlogger" including.
    Even the statistics seem to continue to write.

    Not show itself statistics, in the section administrator. Including and not see the status of services (in the admin section), showing red crosses, and reported that the data are outdated.

    In logs:
    Code:
    cat /opt/zimbra/log/mailbox.log.2009-11-23 | grep WARN
    2009-11-23 00:43:56,519 WARN  [Shutdown] [] ZimbraHttpConnectionManager - shutting down http client idle connection reaper thread
    2009-11-23 00:45:47,734 WARN  [main] [] log - No value for env-entry-name trustedIPs
    2009-11-23 22:29:07,810 WARN  [ScheduledTask-9] [name=bmw@domen.ru;mid=3;ds=RSS-12492;] datasource - Scheduled DataSource import failed.
    
    
    cat /opt/zimbra/log/mailbox.log.2009-11-23 | grep error
    There is nothing about this problems.

  4. #34
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    53
    Rep Power
    6

    Default

    Quote Originally Posted by pfnguyen View Post
    grep Exception, not grep error (and if you do find any related to logger--particularly GetLoggerStats, please post context).
    Such errors. Here are a few.

    cat /opt/zimbra/log/mailbox.log.2009-11-22 | grep Exception

    Code:
    java.lang.IllegalArgumentException: Column 'TABLE_SCHEMA' does not exist
    com.zimbra.common.service.ServiceException: parse error: could not parse feed
    ExceptionId:ScheduledTask-1:1258868714254:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.PARSE_ERROR(ServiceException.java:265)
    Caused by: org.dom4j.DocumentException: Error on line 10 of document  : The element type "META" must be terminated by the matching end-tag "". Nested exception: The element type "META" must be terminated by the matching end-tag "".
    
    
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-1://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258888746751:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-0://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258888746751:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    ExceptionId:btpool0-9://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258920646275:b88e2cc112202127
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-4://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258920646299:b88e2cc112202127
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused

  5. #35
    Join Date
    Jan 2008
    Posts
    62
    Rep Power
    7

    Default

    Like I said, post context around anything that's GetLoggerRequest -- also include any output from /opt/zimbra/log/zmlogswatch.out

    Quote Originally Posted by HidX View Post
    Such errors. Here are a few.

    cat /opt/zimbra/log/mailbox.log.2009-11-22 | grep Exception

    Code:
    java.lang.IllegalArgumentException: Column 'TABLE_SCHEMA' does not exist
    com.zimbra.common.service.ServiceException: parse error: could not parse feed
    ExceptionId:ScheduledTask-1:1258868714254:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.PARSE_ERROR(ServiceException.java:265)
    Caused by: org.dom4j.DocumentException: Error on line 10 of document  : The element type "META" must be terminated by the matching end-tag "". Nested exception: The element type "META" must be terminated by the matching end-tag "".
    
    
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-1://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258888746751:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-0://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258888746751:14bd0f1faafe13ba
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    ExceptionId:btpool0-9://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258920646275:b88e2cc112202127
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-4://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1258920646299:b88e2cc112202127
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
    Caused by: java.net.ConnectException: Connection refused

  6. #36
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    53
    Rep Power
    6

    Default

    Quote Originally Posted by pfnguyen View Post
    Like I said, post context around anything that's GetLoggerRequest -- also include any output from /opt/zimbra/log/zmlogswatch.out
    In the log /opt/zimbra/log/zmlogswatch.out

    Today's (zmlogswatch.out):

    Code:
    Tue Nov 24 02:15:36 2009: Spawned: 10572 -- Connected from 127.0.0.1:49391
    Tue Nov 24 02:15:36 2009: Spawned: 10577 -- Connected from 127.0.0.1:49392
    Tue Nov 24 02:15:36 2009: Spawned: 10578 -- Connected from 127.0.0.1:49393
    Tue Nov 24 02:23:19 2009: Spawned: 19305 -- Connected from 127.0.0.1:52854
    Tue Nov 24 02:23:19 2009: Spawned: 19306 -- Connected from 127.0.0.1:52855
    Tue Nov 24 02:23:19 2009: Spawned: 19307 -- Connected from 127.0.0.1:52856
    ........
    For other days(zmlogswatch.out.1):

    Code:
    Tue Nov 17 23:44:49 2009: Spawned: 15881 -- Connected from 127.0.0.1:53524
    Tue Nov 17 23:44:49 2009: Spawned: 15884 -- Connected from 127.0.0.1:53525
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.
    Wed Nov 18 02:34:36 2009: Spawned: 10057 -- Connected from 127.0.0.1:41066
    Wed Nov 18 02:34:36 2009: Spawned: 10059 -- Connected from 127.0.0.1:41067
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.
    Wed Nov 18 02:34:37 2009: Spawned: 10131 -- Connected from 127.0.0.1:41068
    Wed Nov 18 02:34:39 2009: Spawned: 10173 -- Connected from 127.0.0.1:41070
    Wed Nov 18 02:34:39 2009: Spawned: 10174 -- Connected from 127.0.0.1:41069
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 225.

  7. #37
    Join Date
    Jan 2008
    Posts
    62
    Rep Power
    7

    Default

    That looks fine--you still haven't given any context around the Exceptions as requested.

  8. #38
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    53
    Rep Power
    6

    Default

    Quote Originally Posted by pfnguyen View Post
    That looks fine--you still haven't given any context around the Exceptions as requested.
    Do not quite understand you. You would like what I would have looked through all logs (/opt/zimbra/log) for "Exceptions"?

  9. #39
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    53
    Rep Power
    6

    Default

    Quote Originally Posted by HidX View Post
    Do not quite understand you. You would like what I would have looked through all logs (/opt/zimbra/log) for "Exceptions"?
    Here is the error that occurs when an appeal to the statistics:

    tail -f mailbox.log

    Code:
    2009-11-24 13:08:51,722 INFO  [btpool0-14://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest] [name=admin@domen.ru;mid=2;ip=79.165.163.197;ua            =ZimbraWebClient - IE8 (Win);] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: Unable to read logger stats
    ExceptionId:btpool0-14://mail.domen.ru:7071/service/admin/soap/GetLoggerStatsRequest:1259057331722:5d23b428ede58845
    Code:service.FAILURE
            at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:247)
            at com.zimbra.cs.service.admin.GetLoggerStats.execfetch(GetLoggerStats.java:447)
            at com.zimbra.cs.service.admin.GetLoggerStats.fetchColumnData(GetLoggerStats.java:262)
            at com.zimbra.cs.service.admin.GetLoggerStats.handle(GetLoggerStats.java:169)
            at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
            at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:272)
            at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
            at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
            at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
            at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
            at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
            at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
            at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
            at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
            at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
            at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
            at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
            at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
            at org.mortbay.jetty.Server.handle(Server.java:324)
            at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:525)
            at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
            at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
            at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
            at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
            at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
            at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    Caused by: java.net.ConnectException: Connection refused
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
            at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
            at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
            at java.net.Socket.connect(Socket.java:525)
            at java.net.Socket.connect(Socket.java:475)
            at java.net.Socket.(Socket.java:372)
            at java.net.Socket.(Socket.java:215)
            at com.zimbra.cs.service.admin.GetLoggerStats.execfetch(GetLoggerStats.java:388)
            ... 35 more

  10. #40
    Join Date
    Nov 2009
    Posts
    5
    Rep Power
    5

    Default Same problem

    I'm having the same problem as the OP. If i delete the logger database and fix the system permissions and then restart Zimbra it works, but the next day when the system rotates the log files (3.16AM) stats stop working and both zimbra.log and zimbra-stats.log stay empty (they gather data after a database clean/permission fix).

    We use 6.0.2_GA_1912 on Fedora 11 32 bits.

    Here is the requested info:
    Code:
    [07:58:22] $ zmloggerctl status; echo $?; ps ax | grep zmlogger
    0
    23740 pts/0    R+     0:00 grep zmlogger
    Code:
    [07:58:54] $ /opt/zimbra/libexec/zmrrdfetch -f zmmtastats | more
    
    Host: #
    
    timestamp,filter_misc,clam_events,mta_delay,mta_volume,filter_virus,filter_count
    ,mta_count,filter_spam,sendmail_events
    1259056770,,,,,,,,,
    1259056800,,,,,,,,,
    1259056830,,,,,,,,,
    1259056860,,,,,,,,,
    1259056890,,,,,,,,,
    1259056920,,,,,,,,,
    1259056950,,,,,,,,,
    Code:
    [07:59:48] $ /opt/zimbra/libexec/zmrrdfetch -c -f zmmtastats | more
    
    Host: #
    
    timestamp,filter_misc,clam_events,mta_delay,mta_volume,filter_virus,filter_count
    ,mta_count,filter_spam,sendmail_events
    1259057100,,,,,,,,,
    1259057400,,,,,,,,,
    1259057700,,,,,,,,,
    1259058000,,,,,,,,,
    1259058300,,,,,,,,,
    1259058600,,,,,,,,,
    1259058900,,,,,,,,,
    Code:
    [08:00:14] $ grep -w MTA /var/log/zimbra-stats.log
    (no output, the file is empty)
    Code:
    [08:00:21] $ tail /var/log/zimbra-stats.log
    (no output, the file is empty)
    Code:
    [08:00:48] $ zmsoap -z GetLoggerStatsRequest stats/@name=zmmtastats | head -20
    ERROR: service.FAILURE (system failure: Unable to read logger stats)
    Code:
    [08:01:15] $ zmsoap -z GetLoggerStatsRequest stats/@name=zmmtastats @limit=1 | head -50
    ERROR: service.FAILURE (system failure: Unable to read logger stats)
    Please advice ASAP.

    Thanks!
    Ricardo

Similar Threads

  1. Messages not being delivered
    By buee in forum Administrators
    Replies: 53
    Last Post: 10-23-2009, 10:28 AM
  2. Replies: 5
    Last Post: 05-28-2009, 12:53 AM
  3. Error after installation
    By robsontuxlinux in forum Installation
    Replies: 13
    Last Post: 09-11-2008, 09:48 PM
  4. zmmailboxdctl is stopped frequently..
    By tamilnandhu in forum Installation
    Replies: 13
    Last Post: 04-12-2008, 08:59 AM
  5. Replies: 4
    Last Post: 11-14-2007, 01:19 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
  •