We have been working on installing and configuring 3.1.1 release of Zimbra and have noticed that the /etc/init.d/zimbra script calls the zimbra/bin/zmcontrol script that starts up only the mail related services. It doesn't seem to load mysql, apache or tomcat.
Am I missing something or is this left up to the administrator to add the appropriate startup scripts?
Let me mention that when we did the install (on a clean box) Zimbra was working perfectly. Once we rebooted the box, the above mentioned services don't start. Looking through the zmcontrol script, I don't reference to these services either.
TIA!
John
zmcontrol doesn't start mysql, apache or tomcat
zmcontrol doesn't start mysql, apache or tomcat
Hi John,
zmcontrol start
starts:
Postfix
mysql
LDAP
DSpam (or SPAM assassin)
Tomcat
All of these are Zimbra's own flavor of the particular program.
Make sure you are not starting any version of the above listed programs on your machine.
What does a zmcontrol status return?
zmcontrol start
starts:
Postfix
mysql
LDAP
DSpam (or SPAM assassin)
Tomcat
All of these are Zimbra's own flavor of the particular program.
Make sure you are not starting any version of the above listed programs on your machine.
What does a zmcontrol status return?
zmcontrol doesn't start mysql, apache or tomcat
zmcontrol does an LDAP query to see which services need to be started on a server. If the server entry does not contain the appropriate services then neither zmcontrol or /etc/init.d/zimbra will attempt to start them. All the services you speak of invovle the mailstore, you can use zmprov to see if LDAP knows what is installed and enabled.
zmprov gs mail.example.com | grep -i service ---- i think that will work.
zmprov gs mail.example.com | grep -i service ---- i think that will work.
zmcontrol doesn't start mysql, apache or tomcat
Hi - I tried the command and it appears that mysql, tomcat and apache don't appear to be in the ldap database. Here are the results of the command.
zimbraServiceEnabled: antivirus
zimbraServiceEnabled: antispam
zimbraServiceEnabled: logger
zimbraServiceEnabled: mailbox
zimbraServiceEnabled: mta
zimbraServiceEnabled: snmp
zimbraServiceEnabled: ldap
zimbraServiceEnabled: spell
zimbraServiceHostname: myserver_name.example.com
zimbraServiceInstalled: antivirus
zimbraServiceInstalled: antispam
zimbraServiceInstalled: logger
zimbraServiceInstalled: imapproxy
zimbraServiceInstalled: mailbox
zimbraServiceInstalled: mta
zimbraServiceInstalled: snmp
zimbraServiceInstalled: ldap
zimbraServiceInstalled: spell
Is there any way to add the missing services to LDAP ?
TIA
zimbraServiceEnabled: antivirus
zimbraServiceEnabled: antispam
zimbraServiceEnabled: logger
zimbraServiceEnabled: mailbox
zimbraServiceEnabled: mta
zimbraServiceEnabled: snmp
zimbraServiceEnabled: ldap
zimbraServiceEnabled: spell
zimbraServiceHostname: myserver_name.example.com
zimbraServiceInstalled: antivirus
zimbraServiceInstalled: antispam
zimbraServiceInstalled: logger
zimbraServiceInstalled: imapproxy
zimbraServiceInstalled: mailbox
zimbraServiceInstalled: mta
zimbraServiceInstalled: snmp
zimbraServiceInstalled: ldap
zimbraServiceInstalled: spell
Is there any way to add the missing services to LDAP ?
TIA
zmcontrol doesn't start mysql, apache or tomcat
The services are actually there they are apart of the mailbox service. If the mailbox starts then tomcat has started mysql has started and apache has started.
zmcontrol doesn't start mysql, apache or tomcat
Here is the > zmcontrol status
Host my_host.example.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
As you can see, all of these services start up but the database, tomcat and apache don't. When I do a 'ps -elf' I can see that httpd, java and tomcat are not running.
To get things working, we had to directly cat the zimbra commands:
tomcat start
zmapachectl start
mysql.server start
We added calls to those scripts in our /etc/init.d/rc3.d directory appropriately.
One note that I wanted to add was that when we attempted to do the install, there was one problem when we were trying to do the initial install. There is a test in the utilfunc.sh to check the /etc/hosts file to make sure that we have the hostname format correct. We tried for at least 1-2 hours toying with the variations but finally had to comment out that one test. Never could figure out why it was failing.
The section of the script (line 229) has:
if ! cat /etc/hosts |
perl -ne 'if (/^s*d+.d+.d+.d+s+(S+)/ && !/^s*127.0.0.1/) { my @foo = split (/./,$1); if ($#foo == "0") {exit 11;} }'; then
cat<
ERROR: Installation can not proceeed. Please fix your /etc/hosts file
to contain:
Where is the ip address of the host,
is the FULLY QUALIFIED host name, and
is the (optional) hostname-only portion
EOF
# exit 1
fi
We commented out the 'exit 1' and the remainder of the script worked.
Our /etc/hosts last configuration was:
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost.localdomain localhost
10.98.3.80 corona.example.com corona
hostname of the server is 'corona'
Host my_host.example.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
As you can see, all of these services start up but the database, tomcat and apache don't. When I do a 'ps -elf' I can see that httpd, java and tomcat are not running.
To get things working, we had to directly cat the zimbra commands:
tomcat start
zmapachectl start
mysql.server start
We added calls to those scripts in our /etc/init.d/rc3.d directory appropriately.
One note that I wanted to add was that when we attempted to do the install, there was one problem when we were trying to do the initial install. There is a test in the utilfunc.sh to check the /etc/hosts file to make sure that we have the hostname format correct. We tried for at least 1-2 hours toying with the variations but finally had to comment out that one test. Never could figure out why it was failing.
The section of the script (line 229) has:
if ! cat /etc/hosts |
perl -ne 'if (/^s*d+.d+.d+.d+s+(S+)/ && !/^s*127.0.0.1/) { my @foo = split (/./,$1); if ($#foo == "0") {exit 11;} }'; then
cat<
ERROR: Installation can not proceeed. Please fix your /etc/hosts file
to contain:
Where is the ip address of the host,
is the FULLY QUALIFIED host name, and
is the (optional) hostname-only portion
EOF
# exit 1
fi
We commented out the 'exit 1' and the remainder of the script worked.
Our /etc/hosts last configuration was:
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost.localdomain localhost
10.98.3.80 corona.example.com corona
hostname of the server is 'corona'