Results 1 to 8 of 8

Thread: zmstats allproc Logger problem zcs 6.0.6 opensuse 11.2

  1. #1
    avery is offline Beginner Member
    Join Date
    Apr 2010
    Posts
    2
    Rep Power
    5

    Default zmstats allproc Logger problem zcs 6.0.6 opensuse 11.2

    Hello!

    I installed zcs 6.0.6 Open Sourse on openSUSE 11.2. All work fine, except server status in Admin GUI Concole and server statistics. All servers in Admin GUI marked red X. There is no statistic too.


    I dig lot of posts here about logger problem, but still have this issue.

    My system information:

    mail:/ # uname -a
    Linux mail 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux

    zimbra@mail:~> rpm -qa | grep zimbra
    zimbra-snmp-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-ldap-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-proxy-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-logger-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-apache-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-mta-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-spell-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-core-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-memcached-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra-store-6.0.6_GA_2324.SLES11_64-20100406160604.x86_64
    zimbra@mail:~> rpm -qa | grep syslog
    syslog-ng-2.0.9-29.2.1.x86_64
    rsyslog-4.4.1-3.1.x86_64

    zimbra@mail:~> zmcontrol status
    Host XXXXXXXXX.com
    antispam Running
    antivirus Running
    imapproxy Running
    ldap Running
    logger Running
    mailbox Running
    memcached Running
    mta Running
    snmp Running
    spell Running
    stats Running

    zimbra@mail:~> zmstatctl status
    Running: zmstat-mysql
    Running: zmstat-io-x
    Running: zmstat-allprocs
    Running: zmstat-fd
    Running: zmstat-cpu
    Running: zmstat-df
    Running: zmstat-vm
    Running: zmstat-mtaqueue
    Running: zmstat-proc
    Running: zmstat-nginx
    Running: zmstat-io
    Zmlogger status shows nothing:

    zimbra@mail:~> zmloggerctl status
    zimbra@mail:~>
    But proccess is russing:
    zimbra@mail:~> zmloggerctl status; echo $?; ps ax | grep zmlogger
    0
    6319 pts/3 S+ 0:00 grep zmlogger
    18993 ? S 0:00 /usr/bin/perl /opt/zimbra/libexec/zmlogger
    19121 ? S 0:00 zmlogger: zmrrdfetch: server
    zimbra@mail:~> /opt/zimbra/libexec/zmrrdfetch -f zmmtastats
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 239.

    zimbra@mail:~> /opt/zimbra/libexec/zmrrdfetch -c -f zmmtastats
    no structure found for zmmtastats at /opt/zimbra/libexec/zmrrdfetch line 239.

    zimbra@mail:~> zmsoap -z GetLoggerStatsRequest stats/@name=zmmtastats | head -20
    <GetLoggerStatsResponse xmlns="urn:zimbraAdmin"/>
    zimbra@mail:~> zmsoap -z GetLoggerStatsRequest stats/@name=zmmtastats @limit=1 | head -50
    <GetLoggerStatsResponse xmlns="urn:zimbraAdmin"/>


    mail:/etc/syslog-ng # grep -w MTA /var/log/zimbra-stats.log
    2010-04-29T18:30:05.783102+04:00 mail zimbramon[22548]: 22548:info: MTA: XXXXXXX.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,mta_count,filter_spam,sendmai l_events:: 0,0,0,0,0,0,0,0,0
    2010-04-29T18:40:06.759589+04:00 mail zimbramon[4127]: 4127:info: MTA: XXXXXXX.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,mta_count,filter_spam,sendmai l_events:: 0,0,0,0,0,0,0,0,0
    2010-04-29T18:50:06.905682+04:00 mail zimbramon[17795]: 17795:info: MTA: XXXXXXX.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,mta_count,filter_spam,sendmai l_events:: 0,0,0,0,0,0,0,0,0
    2010-04-29T19:00:06.506508+04:00 mail zimbramon[31842]: 31842:info: MTA: XXXXXXX.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,mta_count,filter_spam,sendmai l_events:: 0,0,0,0,0,0,0,0,0
    2010-04-29T19:10:06.675793+04:00 mail zimbramon[13676]: 13676:info: MTA: XXXXXXX.com: filter_misc,clam_events,mta_delay,mta_volume,filte r_virus,filter_count,mta_count,filter_spam,sendmai l_events:: 0,0,0,0,0,0,0,0,0
    ... etc.

    mail:/etc/syslog-ng # tail /var/log/zimbra-stats.log
    2010-04-30T13:40:08.166038+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: antivirus: Running
    2010-04-30T13:40:08.166162+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: imapproxy: Running
    2010-04-30T13:40:08.166287+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: ldap: Running
    2010-04-30T13:40:08.166411+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: logger: Running
    2010-04-30T13:40:08.166536+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: mailbox: Running
    2010-04-30T13:40:08.166659+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: memcached: Running
    2010-04-30T13:40:08.166789+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: mta: Running
    2010-04-30T13:40:08.166913+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: snmp: Running
    2010-04-30T13:40:08.167036+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: spell: Running
    2010-04-30T13:40:08.167159+04:00 mail zimbramon[6336]: 6336:info: 2010-04-30 13:40:01, STATUS: XXXXXXXXXX.com: stats: Running

    zimbra@mail:~> tail /opt/zimbra/log/zmlogswatch.out
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 638.
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 638.
    Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 547, <> line 639.
    Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 557, <> line 639.
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 639.
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 639.
    Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 547, <> line 640.
    Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 557, <> line 640.
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 640.
    Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 640.
    zimbra@mail:~> tail /opt/zimbra/log/zmswatch.out

    *** swatch version 3.2.3 (pid:24372) started at Fri Apr 30 13:30:57 MSD 2010

    SMTP notification: 2010-04-30T13:32:55.926062+04:00 mail zimbramon[19132]: 19132:err: Service status change: XXXXXXXXXX.com stats changed from stopped to running
    SNMP notification: 2010-04-30T13:32:55.926062+04:00 mail zimbramon[19132]: 19132:err: Service status change: XXXXXXXXXX.com stats changed from stopped to running



    zimbra@mail:~> tail /opt/zimbra/zmstat/zmstat.out
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    I think the proble is somewhere in zmstats or zmstat-allprocs or in syslog output format

    zimbra@mail:~> head /opt/zimbra/zmstat/zmstat.out
    apache-convertd not running, not launching zmstat-convertd
    Warning: Not possible to monitor process stats
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.

    my syslon-ng.conf:

    #
    # Global options.
    #
    options { long_hostnames(off); sync(0); perm(0640); stats(3600); };

    #
    # 'src' is our main source definition. you can add
    # more sources driver definitions to it, or define
    # your own sources, i.e.:
    #
    #source my_src { .... };
    #
    source src {
    #
    # include internal syslog-ng messages
    # note: the internal() soure is required!
    #
    internal();

    #
    # the default log socket for local logging:
    #
    unix-dgram("/dev/log");

    #
    # uncomment to process log messages from network:
    #
    #udp(ip("0.0.0.0") port(514));
    };


    #
    # Filter definitions
    #
    filter f_iptables { facility(kern) and match("IN=") and match("OUT="); };

    filter f_console { level(warn) and facility(kern) and not filter(f_iptables)
    or level(err) and not facility(authpriv); };

    filter f_newsnotice { level(notice) and facility(news); };
    filter f_newscrit { level(crit) and facility(news); };
    filter f_newserr { level(err) and facility(news); };
    filter f_news { facility(news); };

    filter f_mailinfo { level(info) and facility(mail); };
    filter f_mailwarn { level(warn) and facility(mail); };
    filter f_mailerr { level(err, crit) and facility(mail); };
    filter f_mail { facility(mail); };

    filter f_cron { facility(cron); };

    filter f_local { facility(local0, local1, local2, local3,
    local4, local5, local6, local7); };

    #
    # acpid messages
    #
    filter f_acpid_full { match('^acpid:'); };
    filter f_acpid { level(emerg..notice) and match('^acpid:'); };

    # this is for the old acpid < 1.0.6
    filter f_acpid_old { match('^\[acpid\]:'); };

    filter f_netmgm { match('^NetworkManager:'); };

    filter f_messages { not facility(news, mail) and not filter(f_iptables); };
    filter f_warn { level(warn, err, crit) and not filter(f_iptables); };
    filter f_alert { level(alert); };


    #
    # Enable this and adopt IP to send log messages to a log server.
    #
    #destination logserver { udp("10.10.10.10" port(514)); };
    #log { source(src); destination(logserver); };

    #
    # Enable this, if you want to keep all messages in one file:
    # (don't forget to provide logrotation config)
    #
    #destination allmessages { file("/var/log/allmessages"); };
    #log { source(src); destination(allmessages); };

    #
    # Most warning and errors on tty10 and on the xconsole pipe:
    #
    destination console { pipe("/dev/tty10" owner(-1) group(-1) perm(-1)); };
    log { source(src); filter(f_console); destination(console); };

    destination xconsole { pipe("/dev/xconsole" owner(-1) group(-1) perm(-1)); };
    log { source(src); filter(f_console); destination(xconsole); };

    # Enable this, if you want that root is informed immediately,
    # e.g. of logins:
    #
    #destination root { usertty("root"); };
    #log { source(src); filter(f_alert); destination(root); };


    #
    # News-messages in separate files:
    #
    destination newscrit { file("/var/log/news/news.crit"
    owner(news) group(news)); };
    log { source(src); filter(f_newscrit); destination(newscrit); };

    destination newserr { file("/var/log/news/news.err"
    owner(news) group(news)); };
    log { source(src); filter(f_newserr); destination(newserr); };

    destination newsnotice { file("/var/log/news/news.notice"
    owner(news) group(news)); };
    log { source(src); filter(f_newsnotice); destination(newsnotice); };

    #
    # and optionally also all in one file:
    # (don't forget to provide logrotation config)
    #
    #destination news { file("/var/log/news.all"); };
    #log { source(src); filter(f_news); destination(news); };


    #
    # Mail-messages in separate files:
    #
    #destination mailinfo { file("/var/log/mail.info"); };
    #log { source(src); filter(f_mailinfo); destination(mailinfo); };

    #destination mailwarn { file("/var/log/mail.warn"); };
    #log { source(src); filter(f_mailwarn); destination(mailwarn); };

    #destination mailerr { file("/var/log/mail.err" fsync(yes)); };
    #log { source(src); filter(f_mailerr); destination(mailerr); };

    #
    # and also all in one file:
    #
    #destination mail { file("/var/log/mail"); };
    #log { source(src); filter(f_mail); destination(mail); };


    #
    # acpid messages in one file:
    #
    destination acpid { file("/var/log/acpid"); };
    destination null { };
    log { source(src); filter(f_acpid); destination(acpid); flags(final); };
    #
    # if you want more verbose acpid logging, comment the destination(null)
    # line and uncomment the destination(acpid) line
    #
    log { source(src); filter(f_acpid_full); destination(null); flags(final); };
    # log { source(src); filter(f_acpid_full); destination(acpid); flags(final); };
    #
    # old acpid < 1.0.6
    log { source(src); filter(f_acpid_old); destination(acpid); flags(final); };

    #
    # NetworkManager messages in one file:
    #
    destination netmgm { file("/var/log/NetworkManager"); };
    log { source(src); filter(f_netmgm); destination(netmgm); flags(final); };


    #
    # Cron-messages in one file:
    # (don't forget to provide logrotation config)
    #
    #destination cron { file("/var/log/cron"); };
    #log { source(src); filter(f_cron); destination(cron); };


    #
    # Some boot scripts use/require local[1-7]:
    #
    destination localmessages { file("/var/log/localmessages"); };
    log { source(src); filter(f_local); destination(localmessages); };


    #
    # All messages except iptables and the facilities news and mail:
    #
    destination messages { file("/var/log/messages"); };
    log { source(src); filter(f_messages); destination(messages); };


    #
    # Firewall (iptables) messages in one file:
    #
    destination firewall { file("/var/log/firewall"); };
    log { source(src); filter(f_iptables); destination(firewall); };


    #
    # Warnings (except iptables) in one file:
    #
    destination warn { file("/var/log/warn" fsync(yes)); };
    log { source(src); filter(f_warn); destination(warn); };


    #source zimbra_src { unix-stream("/dev/log" keep-alive(yes) max-connections(20)); }; # zimbra
    filter zimbra_local0 { facility(local0); }; # zimbra
    filter zimbra_local1 { facility(local1); }; # zimbra
    filter zimbra_auth { facility(auth); }; # zimbra
    filter zimbra_mail { facility(mail); }; # zimbra
    destination zimbra_mail { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
    destination zimbra_local1 { file("/var/log/zimbra-stats.log" owner("zimbra")); }; # zimbra
    destination zimbra_local0 { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
    destination zimbra_auth { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
    log { source(src); filter(zimbra_mail); destination(zimbra_mail); }; # zimbra
    log { source(src); filter(zimbra_local0); destination(zimbra_local0); }; # zimbra
    log { source(src); filter(zimbra_local1); destination(zimbra_local1); }; # zimbra
    log { source(src); filter(zimbra_auth); destination(zimbra_auth); }; # zimbra

    /var/log/zimbra-stat.log is not empty:

    zimbra@mail:~> tail -n 2 /var/log/zimbra-stats.log
    2010-04-30T13:53:30.738445+04:00 mail zimbramon[27377]: 27377:info: :::3B806BCE-543E-11DF-A5C4-DDB672A52BCF:::_threads, Slow_queries, Sort_merge_passes, Sort_range, Sort_rows, Sort_scan, Ssl_accept_renegotiates, Ssl_accepts, Ssl_callback_cache_hits, Ssl_cipher, Ssl_cipher_list, Ssl_client_connects, Ssl_connect_renegotiates, Ssl_ctx_verify_depth, Ssl_ctx_verify_mode, Ssl_default_timeout, Ssl_finished_accepts, Ssl_finished_connects, Ssl_session_cache_hits, Ssl_session_cache_misses, Ssl_session_cache_mode, Ssl_session_cache_overflows, Ssl_session_cache_size, Ssl_session_cache_timeouts, Ssl_sessions_reused, Ssl_used_session_cache_entries, Ssl_verify_depth, Ssl_verify_mode, Ssl_version, Table_locks_immediate, Table_locks_waited, Tc_log_max_pages_used, Tc_log_page_size, Tc_log_page_waits, Threads_cached, Threads_connected, Threads_created, Threads_running, Uptime:: 04/30/2010 13:53:30,0,0,0,0,18741,3744:::3B806F84-543E-11DF-A5C4-DDB672A52BCF:::
    2010-04-30T13:53:30.738466+04:00 mail zimbramon[27377]: :::3B806F84-543E-11DF-A5C4-DDB672A52BCF:::47,1,0,0,0,0,0,0,0,0,0,0,9,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0, 0,0,0,0,0,0,1,0,0,0,0,0,44,0,72,136,0,0,0,1,0,0,0, 0,0,0,0,22,0,0,0,0,0,0,0,0,0,0,74,0,0,0,1,0,0,0,0, 0,0,0,0,0,0,0,2,0,0,0,0,0,0,0,OFF,76,0,5,47,0,0,0, 1,13,0,0,0,13,47,117,0,0,11352,6,0,0,0,11273,146,0 ,25,38316,2,38464,1,0,5900,95,0,34,22,0,0,0,457523 2,121,26,825856,25,4,0,3,5,10,0,0,4096,16384,0,146 ,25,0,0,0,0,0,0,1,130,3,0,6694,0,0,0,0,0,0.000000, 2,0,27,0,24,30,0,0,0,0,0,0,0,0,0,407,407,NULL,0,0, 7,0,52,0,0,OFF,0,5,0,0,0,0,0,0,0,,,0,0,0,0,0,0,0,0 ,0,NONE,0,0,0,0,0,0,0,,43,0,0,0,0,0,2,2,1,1431
    My /otp/zimbra/zmstat/allproc.csv

    zimbra@mail:~> head /opt/zimbra/zmstat/allprocs.csv
    timestamp, process, utime, stime, cputime, rchar, wchar, read_bytes, write_bytes, rss, processes, threads
    04/30/2010 13:32:30, mc, 0, 0, 0, 0, 0, 0, 0, 7772, 2, 2
    04/30/2010 13:32:30, scsi_eh_1, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0
    04/30/2010 13:32:30, events/3, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0
    04/30/2010 13:32:30, init, 0, 0, 0, 0, 0, 0, 0, 668, 1, 1
    04/30/2010 13:32:30, kdmflush, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0
    04/30/2010 13:32:30, dbus-launch, 0, 0, 0, 0, 0, 0, 0, 2920, 4, 4
    04/30/2010 13:32:30, kblockd/1, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0
    04/30/2010 13:32:30, avahi-daemon, 0, 0, 0, 0, 0, 0, 0, 3916, 1, 1
    04/30/2010 13:32:30, kblockd/3, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0
    This post upgrade to 6.0.2 stats and status no longer working is not useful for me.

    How can I solve this issue?

    Thanks for any help!

  2. #2
    breverend is offline Intermediate Member
    Join Date
    Jun 2009
    Posts
    22
    Rep Power
    6

    Default

    Hi,

    I'm having the same issue on a fresh install of ZCS 6.0.7 on a centos 5.5.

    I used RHE package, and I got basically the same issue as you.

    Only difference is in the zmlogswatch.out :
    Code:
    [zimbra@mail ~]$ tail log/zmlogswatch.out
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 235.
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 235.
    Use of uninitialized value in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 547, <> line 236.
    Use of uninitialized value in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 557, <> line 236.
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 236.
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 236.
    Use of uninitialized value in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 547, <> line 237.
    Use of uninitialized value in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 557, <> line 237.
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 237.
    Use of uninitialized value in string eq at /opt/zimbra/libexec/zmlogger line 564, <> line 237.
    How did you find this, if you managed to ?

    Thanks

  3. #3
    Hivos's Avatar
    Hivos is offline Advanced Member
    Join Date
    Aug 2009
    Location
    The Hague -- The Netherlands
    Posts
    214
    Rep Power
    6

    Default

    Same issue here on ZCS NE Ubuntu 8.0.4 32b:
    zmstat.out is filled with:
    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.
    This line says the following:
    $curr_stats->{$pid}->{$stat} - $prev_stats->{$pid}->{$stat};
    Which doesn't get me much further for now...

  4. #4
    dhickey is offline Intermediate Member
    Join Date
    Feb 2006
    Posts
    23
    Rep Power
    9

    Default

    Add me to the list..6.0.7 with patch applied running on REHL 4 32 bit..

    Stats not working and zmstat.out filled with -

    Use of uninitialized value in subtraction (-) at /opt/zimbra/libexec/zmstat-allprocs line 118.

    Don

  5. #5
    stiller is offline Partner (VAR/HSP)
    Join Date
    May 2008
    Posts
    92
    Rep Power
    7

    Default me too

    Here as well, NE 6.0.7 on Centos 5.5 64 bit.
    Snelbij | Uw informatie ter beschikking.
    https://www.snelbij.nl

  6. #6
    humblemumble is offline Starter Member
    Join Date
    Aug 2010
    Posts
    2
    Rep Power
    5

    Default workaround

    hello,

    i managed to go around that message by setting up the zimbraLogHostname via :
    zmprov mcf zimbraLogHostname <hostname of the server>

    and restarting daemons. Now i can see the flash statistics in advanced statistics tab.

    install :
    Release 6.0.7_GA_2473.UBUNTU8_64 UBUNTU8_64 FOSS edition

    so it wasnt maybe setup by installation or it required some post install task which i missed. Maybe a bug.

    br/hm

  7. #7
    guillotte is offline Starter Member
    Join Date
    Oct 2010
    Posts
    3
    Rep Power
    4

    Default

    Unfortunately it did not work for me.
    I also I have openSUSE 11.2 ZCS 64 and updated to 6.0.8
    Data:

    rpm -qa | grep syslog
    rsyslog-3.18.3-7.1.x86_64
    syslogd-1.4.1-711.2.x86_64

    ps ax |grep syslog
    10626 ? Sl 0:06 /sbin/rsyslogd -c 4 -f /etc/rsyslog.conf


    tail zmstat.out
    Warning: Not possible to monitor process stats
    Warning: Not possible to monitor process stats

    The rest is a copy of AVERY.
    Is anyone able to resolve this situation?

    is perhaps because this platform is not supported?
    /opt/zimbra/libexec/get_plat_tag.sh
    openSUSEUNKNOWN_64

  8. #8
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,582
    Rep Power
    57

    Default

    Quote Originally Posted by guillotte View Post
    is perhaps because this platform is not supported?
    Quite likely. You would have a better experience if you installed Zimbra on a supported platform, I'd suggest picking a 'server' distribution such as RHEL (or CentOS), SLES or Ubuntu LTS.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Address auto-complete in ZCS 6.0.6
    By soxfan in forum Administrators
    Replies: 63
    Last Post: 02-17-2011, 07:31 AM
  2. [SOLVED] Logger Problem
    By riccabarg in forum Installation
    Replies: 1
    Last Post: 03-19-2010, 04:45 AM
  3. ZCS 4.5.7 CentOS5 - Enabled logger, system crashed
    By blueflametuna in forum Administrators
    Replies: 2
    Last Post: 01-30-2010, 01:41 PM
  4. Replies: 34
    Last Post: 12-05-2007, 11:29 PM
  5. Multi-server install - logger problem
    By mrfileio in forum Administrators
    Replies: 1
    Last Post: 11-29-2006, 06:53 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
  •