Page 6 of 7 FirstFirst ... 4567 LastLast
Results 51 to 60 of 63

Thread: upgrade to 6.0.2 stats and status no longer working

  1. #51
    Join Date
    Nov 2008
    Posts
    19
    Rep Power
    7

    Default

    I came in this morning, checked the admin console and status of my 2 servers was blue. Statistics for each was unavailable an I got an error message. Restarting rsyslog fixed the problem immediately (seconds). Statistics graphs now available, no error message. An earlier post suggested adding a cron job as root to restart rsyslog. I'm doing the same.

  2. #52
    Join Date
    Jul 2009
    Location
    Athens Greece
    Posts
    7
    Rep Power
    6

    Default

    I concur, the same behaviour is exhibited by ZCS 6.0.3 on Debian Lenny x64. Once rsyslog is restarted, server monitoring starts working again (within a few minutes) on the web admin console.

    At this point in time, I think I also have no other choice but to add a cronjob to restart rsyslog every day. I wish as well that a more decent fix could be provided but I am not sure for which bug I should vote (three were mentioned earlier in this thread): 42332 is still open (but I am not sure it is exactly the same problem), 42053 & 42293 have been closed.

  3. #53
    Join Date
    Jan 2008
    Posts
    16
    Rep Power
    7

    Default

    zmsyslogsetup failed for me:

    root@zimbra:/etc# /opt/zimbra/bin/zmsyslogsetup
    ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException zimbra.myserver.org:636)
    I had to set startTLS from /opt/zimbra/bin/zmlocalconfig -e ldap_starttls_supported=0
    to /opt/zimbra/bin/zmlocalconfig -e ldap_starttls_supported=1 before the operation. And back afterwards.

  4. #54
    Join Date
    Jan 2008
    Posts
    16
    Rep Power
    7

    Default

    Gnah!

    Even this did not help. I'm stuck with the same problem.

  5. #55
    Join Date
    Aug 2009
    Location
    Palma de Mallorca, Spain
    Posts
    66
    Rep Power
    6

    Default I think I know why a few people here have problems ...

    I experienced the same problem and started looking around, as it seems people with syslog are fine, people with rsyslog have problems, i tracked this down to (at least at my installation):

    in /etc/logrotate.d/ is the file zimbra.

    The first two entries are for the syslogs, here in the postrotate section, which does stuff like reloading the syslogd after logrotation, etc., i had (amongst other):

    killall -HUP syslogd 2> /dev/null || true

    since my system is using rsyslog instead of standard syslog it will never reload the syslog-deamon and therefore you have problems with the logfiles. This is even more problematic as zimbra begins with z and therefore it is the last script which gets executed from logrotate, if it would not be the last one, there would have been a chance that a later script reloads the syslog daemon :-) I changed this line to:

    killall -HUP rsyslogd 2> /dev/null || true

    (notice the r in front of rsyslogd)

    And hopefully tomorrow will be all good!

    I believe this is a bug from zimbra as the tool for installing the logging facility should check if the system uses syslogd or rsyslogd and change the configuration accordingly.

    hope this helps anybody,

    best regards
    Raimund

  6. #56
    Join Date
    Jul 2009
    Location
    Athens Greece
    Posts
    7
    Rep Power
    6

    Default

    Excellent stuff Raimund, great digging!

    It is so simple but yet it has managed to escape everyone's attention.

    Has it worked for you? I just saw your post and made the change in our server so I need to wait a day to see the results.

    If it is the case that this was the problem, have you opened a bug with Zimbra?

    Thanks again for your help, I hope it also works out for me, Tasis

  7. #57
    Join Date
    Aug 2009
    Location
    Palma de Mallorca, Spain
    Posts
    66
    Rep Power
    6

    Default Yes, it worked out fine for me

    Since I made these chances I do not have problems with the stats and status.

    However, until now I did not file a bug, but you are right and I will do this now!

    I'm glad my finding was useful for at least another person :-)

    Best
    Raimund
    Last edited by Hatrix; 02-10-2010 at 02:48 AM.

  8. #58
    Join Date
    Aug 2009
    Location
    Palma de Mallorca, Spain
    Posts
    66
    Rep Power
    6

    Default Created a patch in bugs, go voting :-)

    Hi,

    there was already a bug in the bugtracking system. I created and added a patch for the zmsyslogsetup utility which would automatically detect and change the configuration from syslog to rsyslog where appropriate.

    If this problem concerns you, please consider voting on this bug/patch as I am sure you don't want to take care of this on the next upgrade as well ;-)

    Bug 43081 – Server statistics fail after logrotate with rsyslogd

    best
    Raimund

  9. #59
    Join Date
    Oct 2007
    Posts
    3
    Rep Power
    8

    Default

    Quote Originally Posted by scottnelson View Post
    I created a cron entry to do this for me at 5am every morning myself.

    It's been working good for me.

    crontab entry is: ( as root )

    0 5 * * * /etc/init.d/rsyslog restart
    confirmed it work. (debian x64) time for crontab is after daily crontab +2min

    Code:
     cat /etc/crontab
    # /etc/crontab: system-wide crontab
    # Unlike any other crontab you don't have to run the `crontab'
    # command to install the new version when you edit this file
    # and files in /etc/cron.d. These files also have username fields,
    # that none of the other crontabs do.
    
    SHELL=/bin/sh
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
    
    # m h dom mon dow user  command
    17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
    25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
    52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
    #
    add
    Code:
     crontab -l
    # m h  dom mon dow   command
    53 6 * * * /etc/init.d/rsyslog restart &

  10. #60
    Join Date
    Aug 2010
    Posts
    5
    Rep Power
    5

    Default hi

    Hi, i have same problem, in my case, (6.0.7_GA_2473.DEBIAN5_64.FOSS) with rsyslog.

    on /etc/logrotate.d/ i got two zimbra files:
    -r--r--r-- 1 root root 2600 Jul 8 10:16 zimbra
    -r--r--r-- 1 root root 2598 Jul 8 10:09 zimbra~

    The first file is OK, i have no syslog entries, just rsyslog.

    the second file, with ~, has entries to syslog instead rsyslog, so i change do rsyslog, lets eait and see if it works, bytheway, i think logrotate just look the first file.

    A question, is this perm. ok(-r--r--r--)?

Similar Threads

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