Results 1 to 5 of 5

Thread: [SOLVED] Can't get a server status

  1. #1
    Join Date
    Mar 2010
    Posts
    3
    Rep Power
    5

    Default [SOLVED] Can't get a server status

    I just completed my install, tested inbound and outbound email (successful) but cannot get a server status. There is a big red X next to my domain. The server statistics are not functioning as well.

    Release 6.0.5_GA_2213.RHEL5_20100202220948 CentOS5 FOSS edition.

    Does anyone have any ideas on where to look to get this functioning properly?

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Welcome to the forums

    A quick search would have hopefully found http://www.zimbra.com/forums/install...-services.html.

  3. #3
    Join Date
    Mar 2010
    Posts
    3
    Rep Power
    5

    Default

    Thanks ... The link you provided pointed me in the right direction. I am running ssh on a non-standard port and I am having logging issues. Will work on it a bit to see what I can find.

  4. #4
    Join Date
    Mar 2010
    Posts
    3
    Rep Power
    5

    Default

    It is running now. Here is what I did:

    1. I opened up port 22 for ssh and firewalled it to only communicate with localhost
    2. The install script did not modify the syslog.conf file to allow logging to the zimbra logs. I ended up installing syslog-ng and ran the scripts from the install process to modify them. It got me close. Here is what it ended up looking like:

    options {
    sync (0);
    time_reopen (10);
    log_fifo_size (1000);
    long_hostnames (off);
    use_dns (no);
    use_fqdn (no);
    create_dirs (no);
    keep_hostname (yes);
    };

    source s_sys {
    file ("/proc/kmsg" log_prefix("kernel: "));
    unix-stream ("/dev/log");
    internal();
    udp(ip(0.0.0.0) port(514));
    };
    source zimbra_src { unix-stream("/dev/log" keep-alive(yes) max-connections(20)); }; # zimbra

    destination d_cons { file("/dev/console"); };
    destination d_mesg { file("/var/log/messages"); };
    destination d_auth { file("/var/log/secure"); };
    destination d_mail { file("/var/log/maillog" sync(10)); };
    destination d_spol { file("/var/log/spooler"); };
    destination d_boot { file("/var/log/boot.log"); };
    destination d_cron { file("/var/log/cron"); };
    destination d_kern { file("/var/log/kern"); };
    destination d_mlal { usertty("*"); };
    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

    filter f_kernel { facility(kern); };
    filter f_default { level(info..emerg) and
    not (facility(mail)
    or facility(authpriv)
    or facility(local0)
    or facility(local1)
    or facility(cron)); };
    filter f_auth { facility(authpriv); };
    filter f_emergency { level(emerg); };
    filter f_news { facility(uucp) or
    (facility(news)
    and level(crit..emerg)); };
    filter f_boot { facility(local7); };
    filter f_cron { facility(cron); };
    filter zimbra_local0 { facility(local0); }; # zimbra
    filter zimbra_local1 { facility(local1); }; # zimbra
    filter zimbra_auth { facility(auth); }; # zimbra
    filter zimbra_mail { facility(mail); }; # zimbra
    filter f_mail { facility(mail); };

    #log { source(s_sys); filter(f_kernel); destination(d_cons); };
    log { source(s_sys); filter(f_kernel); destination(d_kern); };
    log { source(s_sys); filter(f_default); destination(d_mesg); };
    log { source(s_sys); filter(f_auth); destination(d_auth); };
    log { source(s_sys); filter(f_mail); destination(d_mail); };
    log { source(s_sys); filter(f_emergency); destination(d_mlal); };
    log { source(s_sys); filter(f_news); destination(d_spol); };
    log { source(s_sys); filter(f_boot); destination(d_boot); };
    log { source(s_sys); filter(f_cron); destination(d_cron); };
    log { source(zimbra_src); filter(zimbra_mail); destination(zimbra_mail); }; # zimbra
    log { source(zimbra_src); filter(zimbra_local0); destination(zimbra_local0); }; # zimbra
    log { source(zimbra_src); filter(zimbra_local1); destination(zimbra_local1); }; # zimbra
    log { source(zimbra_src); filter(zimbra_auth); destination(zimbra_auth); }; # zimbra
    log { source(s_sys); filter(zimbra_mail); destination(zimbra_mail); }; # zimbra
    log { source(s_sys); filter(zimbra_local0); destination(zimbra_local0); }; # zimbra
    log { source(s_sys); filter(zimbra_local1); destination(zimbra_local1); }; # zimbra
    log { source(s_sys); filter(zimbra_auth); destination(zimbra_auth); }; # zimbra

  5. #5
    Join Date
    Jan 2008
    Location
    Australia
    Posts
    25
    Rep Power
    7

    Default

    I did have the same problem. The solution in my case was to switch from syslog to rsyslog in the service configuration.

Similar Threads

  1. Replies: 2
    Last Post: 04-12-2010, 10:29 AM
  2. [SOLVED] mysql.server not running
    By king0770 in forum Administrators
    Replies: 23
    Last Post: 07-25-2009, 03:07 PM
  3. postfix watchdog timeout
    By useopenid in forum Administrators
    Replies: 2
    Last Post: 06-17-2009, 04:17 PM
  4. Replies: 9
    Last Post: 02-25-2009, 03:39 AM
  5. [SOLVED] Moving Zimbra to a new server
    By krolen in forum Administrators
    Replies: 109
    Last Post: 02-05-2009, 10:38 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
  •