Phoenix, that's no problem. Thanks for the feedback.
I'm concerned something isn't right with my installation. I checked the status of the services before doing anything and got the following output:
Quote:
domainname:/ zimbra$ zmcontrol status
Host domainname.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running
domainname:/ zimbra$
|
Then I followed the third step commands from the ZmSetServerName wiki (as I didn't have anything to backup!) and got the following output:
Quote:
domainname:/ zimbra$ zmcontrol stop
Host domainname.com
Stopping stats...Done
Stopping mta...Done
Stopping spell...Done
Stopping snmp...Done
Stopping antivirus...Done
Stopping antispam...Done
Stopping imapproxy...Done
Stopping mailbox...Done
Stopping logger...Done
Stopping ldap...Done
domainname:/ zimbra$ /opt/zimbra/libexec/zmsetservername mail.domainname.com
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException domainname.com:389)
Host domainname.com
Stopping stats...Done
Stopping mta...Done
Stopping spell...Done
Stopping snmp...Done
Stopping antivirus...Done
Stopping antispam...Done
Stopping imapproxy...Done
Stopping mailbox...Done
Stopping logger...Done
Stopping ldap...Done
Started slapd: pid 27978
ldap_initialize( ldap://domainname.com:389 )
replace zimbraMailHost:
mail.domainname.com
replace zimbraMailTransport:
lmtp:mail.domainname.com:7025
modifying entry "uid=admin,ou=people,dc=domainname,dc=com"
modify complete
replace zimbraMailHost:
mail.domainname.com
replace zimbraMailTransport:
lmtp:mail.domainname.com:7025
modifying entry "uid=wiki,ou=people,dc=domainname,dc=com"
modify complete
replace zimbraMailHost:
mail.domainname.com
replace zimbraMailTransport:
lmtp:mail.domainname.com:7025
modifying entry "uid=spam.lebi8xgc,ou=people,dc=domainname,dc=com"
modify complete
replace zimbraMailHost:
mail.domainname.com
replace zimbraMailTransport:
lmtp:mail.domainname.com:7025
modifying entry "uid=ham.w.meojgo,ou=people,dc=domainname,dc=com"
modify complete
adding new entry "cn=mail.domainname.com,cn=servers,cn=zimbra"
domainname:/
|
I didn't know what the error:
Quote:
|
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException domainname.com:389)
|
but as the ldap service was reinitialized I thought this might have been a temporary glitch. I'm not sure about that now!
I ignored step 4 as I'm trying to configure ZCS 4.5.11.
I assumed the next 3 steps would require root access so ran su - root to process the commands.
Step 5 - Update the DNS server - How do I update the DNS server? I had a look at /etc/named.conf but there is nothing in the config file relating to the domain! So I left it as it was:
Code:
//
// Include keys file
//
include "/etc/rndc.key";
// Declares control channels to be used by the rndc utility.
//
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
//
// Default controls
//
controls {
inet 127.0.0.1 port 54 allow {any;}
keys { "rndc-key"; };
};
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
logging {
category default {
_default_log;
};
channel _default_log {
file "/Library/Logs/named.log";
severity info;
print-time yes;
};
}; Step 6 - Edit /etc/sysconfig/network - The file /etc/sysconfig/network does not exist!
Step 7 - Edit /etc/hosts file with new hostname - I changed the entry as follows:
Code:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
192.168.1.234 mail.domainname.com
Before the change the last line read:
Code:
192.168.1.234 domainname.com
Step 8 - I then rebooted the server.
Upon restart it appeared that none of the services were running as when I tried to run the following command:
Quote:
mail:~ zimbra$ zmprov gacf | grep domainname.com
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
|
So I then checked the status of the server:
Quote:
mail:~ zimbra$ zmcontrol status
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Host mail.tinhorsedesign.com
antispam Stopped
zmmtaconfigctl is not running
zmamavisdctl is not running
antivirus Stopped
zmmtaconfigctl is not running
zmamavisdctl is not running
zmclamdctl is not running
ldap Stopped
logger Stopped
logmysql.server is not running
zmlogswatchctl is not running
mailbox Stopped
zmmtaconfigctl is not running
mysql.server is not running
tomcat is not running
mta Stopped
zmmtaconfigctl is not running
postfix is not running
zmsaslauthdctl is not running
snmp Stopped
swatch is not running
spell Stopped
zmapachectl is not running
stats Stopped
|
So I then tried starting the services again:
Quote:
mail:~ zimbra$ zmcontrol start
Host mail.domainname.com
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...FAILED
ClamAV update process started at Wed Apr 8 02:43:00 2009
SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES
See the FAQ at Clam AntiVirus for an explanation.
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.92 Recommended version: 0.95
DON'T PANIC! Read Clam AntiVirus
main.inc is up to date (version: 50, sigs: 500667, f-level: 38, builder: sven)
daily.inc is up to date (version: 9211, sigs: 38621, f-level: 41, builder: neo)
clamd failed to start
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
mail:~ zimbra$
|
I had a look at the ClamAV faq and there appeared to be nothing relating to updating the program under MacOSX - I have clamxav running on all the MacOSX workstations but that is just with a client GUI autostarting at login - not the same thing.
I tried logging into the zimbraAdmin web management interface but not surprisingly I ended up with the same result - a blank page.
Any thoughts on how I can resolve this/where I go from here?
Thanks for your patience.
Dene