Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Server Status

  1. #11
    Join Date
    May 2009
    Posts
    33
    Rep Power
    6

    Default

    Hi Bill

    I checked as suggested and everything is zimbra:zimbra including the containing folder so that bug is resolved.

    Regards
    Simon

  2. #12
    Join Date
    Jun 2010
    Posts
    198
    Rep Power
    5

    Default

    can you please check if the zimbraLogHostname is set correct and run the binary as root

    /opt/zimbra/libexec/zmsyslogsetup

    it does the trick for me.

  3. #13
    Join Date
    May 2009
    Posts
    33
    Rep Power
    6

    Default

    Hi

    So the hostname appears to be correct but I think we might be getting somewhere. After I ran zmsyslogsetup I went to look in the /etc/rsyslog.conf file and saw this near the bottom:

    daemon.*;mail.*;\
    news.err;\
    *.=debug;*.=info;\
    *.=notice;*.=warn |/dev/xconsole
    local0.* @mailsuth.saao.ac.za
    local1.* @mailsuth.saao.ac.za
    auth.* @mailsuth.saao.ac.za
    local0.* -/var/log/zimbra.log
    local1.* -/var/log/zimbra-stats.log
    auth.* -/var/log/zimbra.log
    mail.* @mailsuth.saao.ac.za
    mail.* -/var/log/zimbra.log

    We have 2 servers - one mailcape and the other mailsuth. Mailsuth has working stats. Mailcape does not. And now I see mailcape is not included in this config file.

    So now to figure out why.

    S

  4. #14
    Join Date
    Jun 2010
    Posts
    198
    Rep Power
    5

    Default

    Quote Originally Posted by simonfishley View Post

    We have 2 servers - one mailcape and the other mailsuth. Mailsuth has working stats. Mailcape does not. And now I see mailcape is not included in this config file.

    S
    Which server has the logger service running? Set the zimbraLogHostname to the hostname of the logger server in both the servers, then run the binary again.

  5. #15
    Join Date
    May 2009
    Posts
    33
    Rep Power
    6

    Default

    Hi again

    Well in actual fact we have logger running on both servers. Could that possibly be the problem? Do we not need logger on both servers?

    S

  6. #16
    Join Date
    May 2010
    Posts
    272
    Rep Power
    5

    Default

    Have the same thing on a single server
    logdirectory is zimbra:zimbra
    also executed zmsyslogsetup as root no change

    the status is fine after a reboot but after a while its stuck on not running

  7. #17
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,374
    Rep Power
    11

    Default

    Quote Originally Posted by simonfishley View Post
    Hi again

    Well in actual fact we have logger running on both servers. Could that possibly be the problem? Do we not need logger on both servers?

    S
    That would do it; Zimbra logger should be running on only one host, and that host's syslog daemon should be configured to accept syslog connections from others.

    In turn, the remaining servers should be forwarding their data to the syslog (Zimbra logger) server.

    On our SLES boxes, we add the following to /etc/syslog-ng/syslog-ng.conf at the bottom. I'll let you sort out from which server this came... :-)


    Code:
    # Begin Zimbra Syslog Section
    #
    # Line below commented out as it doesn't work; use SUSE's already-defined above source (src) instead.
    #source zimbra_src { internal(); unix-stream("/dev/log" keep-alive(yes) max-connections(20)); }; # zimbra
    # Next four lines mandatory for all Zimbra servers.
    filter zimbra_local0 { facility(local0); }; # zimbra
    filter zimbra_local1 { facility(local1); }; # zimbra
    filter zimbra_auth { facility(auth); }; # zimbra
    filter zimbra_mail { facility(mail); }; # zimbra
    # Next four lines used on remote hosts; comment out on the logger server.
    #destination zimbra_mail { udp("172.16.1.22" port(514) ); }; # zimbra
    #destination zimbra_local1 { udp("172.16.1.22" port(514) ); }; # zimbra
    #destination zimbra_local0 { udp("172.16.1.22" port(514) ); }; # zimbra
    #destination zimbra_auth { udp("172.16.1.22" port(514) ); }; # zimbra
    # Next four lines used only on the logger host; comment out on remote hosts.
    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
    # Next four lines mandatory for all Zimbra servers.
    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
    # End Zimbra Syslog Section
    Hope that helps,
    Mark

Similar Threads

  1. Replies: 2
    Last Post: 04-12-2010, 11:29 AM
  2. [SOLVED] Cannot receive incoming mail but can send.
    By windependence in forum Administrators
    Replies: 2
    Last Post: 03-23-2010, 03:43 AM
  3. Corrupt User Account
    By FaithX in forum Administrators
    Replies: 4
    Last Post: 01-20-2009, 01:56 PM
  4. could not send email on zcs 4.5.6
    By bylong in forum Installation
    Replies: 9
    Last Post: 08-20-2007, 10:02 AM
  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
  •