Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-03-2010, 10:34 PM
New Member
 
Posts: 3
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?
Reply With Quote
  #2 (permalink)  
Old 03-04-2010, 01:19 AM
Moderator
 
Posts: 7,911
Default

Welcome to the forums

A quick search would have hopefully found [SOLVED] After install server status shows errors for all services.
__________________
Reply With Quote
  #3 (permalink)  
Old 03-04-2010, 12:24 PM
New Member
 
Posts: 3
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.
Reply With Quote
  #4 (permalink)  
Old 03-04-2010, 04:39 PM
New Member
 
Posts: 3
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
Reply With Quote
  #5 (permalink)  
Old 03-04-2010, 10:42 PM
Active Member
 
Posts: 25
Default

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


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.