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

Thread: logger stopped

  1. #1
    lodder is offline Starter Member
    Join Date
    Jan 2008
    Posts
    1
    Rep Power
    7

    Default logger stopped

    I was using the admin console, when i got this error:

    Code:
    system failure: getting database logger connection error code: 
    service:FAILURE Method: GetServiceStatusRequest Details:soap:Receiver
    after that i check the logs:

    Code:
    *** logswatch version 3.1.1 (pid:21068) started at Sun Feb 17 18:16:08 CET 2008
    
    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: Too many connections at /opt/zimbra/libexec/zmlogger line 174
    Can't call method "prepare" on unblessed reference at /opt/zimbra/libexec/zmlogger line 61.
    version: Release 5.0.1_GA_1902.DEBIAN4.0 DEBIAN4.0 FOSS edition

    can this be solved?

  2. #2
    Bill Brock is offline Outstanding Member
    Join Date
    May 2007
    Location
    Oklahoma
    Posts
    703
    Rep Power
    9

    Default

    "Server status data not available. To see the server status, logger service must be installed."

    I get this message in the Admin UI all the time. Sometimes it works and sometimes it doesn't. This has happened with ver,4.5.6 thru 5.0.2. I can use webmin to view the logs and they are always there and running. But the Admin UI seems to lose the connection. I can't find a rhyme or reason because webmin can always show me the logs.

  3. #3
    bdial's Avatar
    bdial is offline Moderator
    Join Date
    Jul 2007
    Location
    Baltimore
    Posts
    1,649
    Rep Power
    11

    Default

    Quote Originally Posted by Bill Brock View Post
    "Server status data not available. To see the server status, logger service must be installed."

    I get this message in the Admin UI all the time. Sometimes it works and sometimes it doesn't. This has happened with ver,4.5.6 thru 5.0.2. I can use webmin to view the logs and they are always there and running. But the Admin UI seems to lose the connection. I can't find a rhyme or reason because webmin can always show me the logs.
    I don't think this is related. you're running openSuSE right? I think the problem you're encountering is this:

    zimbra runs it's log rotate. it moves the /var/log/zimbra.log to an archive directory, then triies to killall -HUP syslogd so it restarts the syslog and begins a new log. Unfortunately, opensuse uses syslog-ng which doesn't respond to a sighup. Therefor the log never gets recreated, until the suse logrotate script runs that night which runs as root and knows to issue a /sbin/rcsyslog restart after it's done. This gets all the logs (including zimbra.log) going again.

    the solution to this is to edit the zimbra logrotate to call /sbin/rcsyslog restart and you'll need to give zimbra sudo power for this

  4. #4
    Mank is offline Member
    Join Date
    Oct 2007
    Location
    California
    Posts
    11
    Rep Power
    7

    Default

    I am a SLES 10 user too and was seeing the problem all to often. You're right. Restarting the syslog works.

    I think this should be files as a bug since SLES 10 is a supported OS for Zimbra NE.

  5. #5
    cyberdeath's Avatar
    cyberdeath is offline Active Member
    Join Date
    Jan 2008
    Location
    127.0.0.1, Virginia, USA
    Posts
    42
    Rep Power
    7

    Default

    I am having the exact same problem with SLES 10.

    Quote Originally Posted by bdial
    zimbra runs it's log rotate. it moves the /var/log/zimbra.log to an archive directory, then triies to killall -HUP syslogd so it restarts the syslog and begins a new log. Unfortunately, opensuse uses syslog-ng which doesn't respond to a sighup. Therefor the log never gets recreated, until the suse logrotate script runs that night which runs as root and knows to issue a /sbin/rcsyslog restart after it's done. This gets all the logs (including zimbra.log) going again.

    the solution to this is to edit the zimbra logrotate to call /sbin/rcsyslog restart and you'll need to give zimbra sudo power for this
    What file am I going to need to modify to make what bdial recommended work? I'm not seeing it clearly enough by looking at my crontab. I looked through several of the files that related to logging but to no avail. Suggestions?

    EDIT: After some research...I finally found out that the logrotate file is located under /etc/logrotate.d/zimbra

    I modified the file and changed the following line:

    Code:
    killall -HUP syslogd 2> /dev/null || true
    to:

    Code:
    sudo /sbin/rcsyslog restart 2> /dev/null || true
    Last edited by cyberdeath; 03-30-2008 at 08:46 PM. Reason: Found "solution" to original post
    cyberdeath

  6. #6
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,368
    Rep Power
    10

    Default

    Quote Originally Posted by cyberdeath View Post
    I am having the exact same problem with SLES 10.



    What file am I going to need to modify to make what bdial recommended work? I'm not seeing it clearly enough by looking at my crontab. I looked through several of the files that related to logging but to no avail. Suggestions?

    EDIT: After some research...I finally found out that the logrotate file is located under /etc/logrotate.d/zimbra

    I modified the file and changed the following line:

    Code:
    killall -HUP syslogd 2> /dev/null || true
    to:

    Code:
    sudo /sbin/rcsyslog restart 2> /dev/null || true
    Just saw this same problem on our one-day old 5.0.4 NE SLES10 install.

    Thanks for the code update.

    Has anyone filed a bug report on this yet?

    All the best,
    Mark

  7. #7
    cyberdeath's Avatar
    cyberdeath is offline Active Member
    Join Date
    Jan 2008
    Location
    127.0.0.1, Virginia, USA
    Posts
    42
    Rep Power
    7

    Default

    Added bug report...I didn't see it otherwise (my apologies if it has already been reported):

    Bug 26766 - SLES 10 does not properly restart logger resulting in no statistics

    Quote Originally Posted by cyberdeath View Post
    ...After some research...I finally found out that the logrotate file is located under /etc/logrotate.d/zimbra

    I modified the file and changed the following line:

    Code:
    killall -HUP syslogd 2> /dev/null || true
    to:

    Code:
    sudo /sbin/rcsyslog restart 2> /dev/null || true
    I also should note I edited the /etc/sudoers file to include this (added line):

    Code:
    %zimbra ALL=NOPASSWD:/sbin/rcsyslog
    This is required in order to make the aforementioned solution provided work.
    Last edited by cyberdeath; 04-06-2008 at 07:45 PM. Reason: Included aforementioned post
    cyberdeath

  8. #8
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,368
    Rep Power
    10

    Default

    Thanks for the update regarding /etc/sudoers; I would not have thought about that one off the bat (though I probably should have).

    Thanks for filing the bug report too; FWIW I would have been happy to file one, and I've added myself as an interested party to your bug report.

    P.S. If you paste the output of zmcontrol -v into your profile for the ZCS version, the Zimbra admins here will be much happier, though with a forum name of "cyberdeath" they may give you less grief than they did me a while back! ;-)
    Last edited by LMStone; 04-07-2008 at 11:33 AM. Reason: Clarity

  9. #9
    tonster is offline Zimbra Employee
    Join Date
    Dec 2007
    Location
    Ypsilanti, MI
    Posts
    144
    Rep Power
    7

    Default

    Quote Originally Posted by cyberdeath View Post
    Added bug report...I didn't see it otherwise (my apologies if it has already been reported):

    Bug 26766 - SLES 10 does not properly restart logger resulting in no statistics



    I also should note I edited the /etc/sudoers file to include this (added line):

    Code:
    %zimbra ALL=NOPASSWD:/sbin/rcsyslog
    This is required in order to make the aforementioned solution provided work.
    I haven't run opensuse recently, but if they are running syslog-ng (like they are in SLES), probably the best work-around to this (until the bug is fixed), is to modify /etc/logrotate.d/zimbra and modify the following:
    Code:
    Bad:
          killall -HUP syslogd 2> /dev/null || true
    Good:
          killall -HUP syslog-ng 2> /dev/null || true
    This will eliminate the need to modify sudoers, and be consistent with how things are done throughout the rest of the platforms. My belief is that this is likely to be the change that gets incorporated into the fix for a future update to ZCS.

  10. #10
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,368
    Rep Power
    10

    Default

    In a post above bdial reports that SuSE's syslog doesn't respond to sighup.

    Have you tested your suggested way on OpenSUSE and SLES10?

    I appreciate you want to have as little distro-specific code in the Zimbra deployment scripts as possible, but as a longstanding SuSE shop our experience has been that one of SuSE's core strengths is scripts. The rc<service> scripts and all the SuSEconfig scripts are just the more common ones.

    Seems to me restarting SuSE services the "SuSE way" provides a solid safety net whose benefits outweigh the costs of trying to develop/test/maintain/retest a distro-neutral methodology.

    That this bug is still here on the fourth point release of Zimbra 5 to me says this kind of code doesn't get unit tested all that much, so if Zimbra elected to do things the "SuSE way" that would cut down on the testing requirements, again, at the "cost" of a little more distro-specific code.

    Just my 2 cents...
    </soapbox>

    All the best,
    Mark
    Last edited by LMStone; 04-10-2008 at 06:14 PM.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 28
    Last Post: 05-21-2008, 12:04 PM
  2. zmmailboxdctl is stopped frequently..
    By tamilnandhu in forum Installation
    Replies: 13
    Last Post: 04-12-2008, 08:59 AM
  3. logger stopped by itself
    By zzzzsg in forum Administrators
    Replies: 23
    Last Post: 08-15-2007, 03:55 PM
  4. Upgrade Trouble woooo
    By RobertW in forum Installation
    Replies: 3
    Last Post: 06-15-2006, 05:24 PM
  5. The mailbox and mta dies in FC4 GA version
    By meikka in forum Installation
    Replies: 72
    Last Post: 03-16-2006, 05:30 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
  •