Zimbra not starting
Zimbra not starting
Hello,
we have Zimbra installed on a testing system. When I tried to connect today the website was not available.
Checking on the console of the server I saw that tomcat was not running and the mta service was down.
After stopping the services I tried to start them but it started only ldap.
No, even after a reboot I only get this:
[zimbra@zimbra ~]$ zmcontrol status
Cannot determine services - exiting
[zimbra@zimbra ~]$ zmcontrol start
Host zimbra.systrade.de
Starting ldap...Done.
What could this be?
Thanks
Christian
we have Zimbra installed on a testing system. When I tried to connect today the website was not available.
Checking on the console of the server I saw that tomcat was not running and the mta service was down.
After stopping the services I tried to start them but it started only ldap.
No, even after a reboot I only get this:
[zimbra@zimbra ~]$ zmcontrol status
Cannot determine services - exiting
[zimbra@zimbra ~]$ zmcontrol start
Host zimbra.systrade.de
Starting ldap...Done.
What could this be?
Thanks
Christian
Zimbra not starting
what is in the zimbra.log in /var/log???
Zimbra not starting
This is the output (tail -f /var/log/zimbra.log) when issuing zmcontrol status:
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 fd=8 ACCEPT from IP=10.1.20.61:32871 (IP=0.0.0.0:389)
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 op=0 BIND dn="uid=zimbra,cn=admins,cn=zimbra" method=128
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 op=0 RESULT tag=97 err=49 text=
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 fd=8 closed (connection lost)
And this for zmcontrol start
Jun 19 19:23:33 zimbra zimbramon[9318]: 9318:info: Starting services
Jun 19 19:23:33 zimbra slapd[9359]: @(#) $OpenLDAP: slapd 2.3.21 (Apr 27 2006 13:51:14) $ root@build.liquidsys.com:/home/build/p4/CRAY/ThirdParty/openldap/openldap-2.3.21/servers/slapd
Jun 19 19:23:33 zimbra slapd[9359]: daemon: bind(7) failed errno=98 (Address already in use)
Jun 19 19:23:33 zimbra slapd[9359]: slapd stopped.
Jun 19 19:23:33 zimbra slapd[9359]: connections_destroy: nothing to destroy.
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 fd=8 ACCEPT from IP=10.1.20.61:32874 (IP=0.0.0.0:389)
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 op=0 BIND dn="uid=zimbra,cn=admins,cn=zimbra" method=128
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 op=0 RESULT tag=97 err=49 text=
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 fd=8 closed (connection lost)
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 fd=8 ACCEPT from IP=10.1.20.61:32871 (IP=0.0.0.0:389)
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 op=0 BIND dn="uid=zimbra,cn=admins,cn=zimbra" method=128
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 op=0 RESULT tag=97 err=49 text=
Jun 19 19:22:29 zimbra slapd[4727]: conn=22 fd=8 closed (connection lost)
And this for zmcontrol start
Jun 19 19:23:33 zimbra zimbramon[9318]: 9318:info: Starting services
Jun 19 19:23:33 zimbra slapd[9359]: @(#) $OpenLDAP: slapd 2.3.21 (Apr 27 2006 13:51:14) $ root@build.liquidsys.com:/home/build/p4/CRAY/ThirdParty/openldap/openldap-2.3.21/servers/slapd
Jun 19 19:23:33 zimbra slapd[9359]: daemon: bind(7) failed errno=98 (Address already in use)
Jun 19 19:23:33 zimbra slapd[9359]: slapd stopped.
Jun 19 19:23:33 zimbra slapd[9359]: connections_destroy: nothing to destroy.
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 fd=8 ACCEPT from IP=10.1.20.61:32874 (IP=0.0.0.0:389)
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 op=0 BIND dn="uid=zimbra,cn=admins,cn=zimbra" method=128
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 op=0 RESULT tag=97 err=49 text=
Jun 19 19:23:38 zimbra slapd[4727]: conn=23 fd=8 closed (connection lost)
Zimbra not starting
which installation are you used??
Have you another services running in the server??
maybe you have ports conflicts
Zimbra nerver come up or this just happend randomly??
Have you another services running in the server??
maybe you have ports conflicts
Zimbra nerver come up or this just happend randomly??
Zimbra not starting
[quote user="kowell"]which installation are you used??
Have you another services running in the server??
maybe you have ports conflicts
Zimbra nerver come up or this just happend randomly??[/QUOTE]
I use the Network Edition, no other services running (the standard sendmail deactivated like stated in the docs).
It has been running fine until yesterday, now it acts as described every time.
Christian
Have you another services running in the server??
maybe you have ports conflicts
Zimbra nerver come up or this just happend randomly??[/QUOTE]
I use the Network Edition, no other services running (the standard sendmail deactivated like stated in the docs).
It has been running fine until yesterday, now it acts as described every time.
Christian
Zimbra not starting
A small update:
We searched a bit for the error and it seems to be a ldap problem.
Whenever an ldap connect is tried it returns an "invalid credentials".
ldap cannot be killed as well.
Still hoping for a solution.
Christian
We searched a bit for the error and it seems to be a ldap problem.
Whenever an ldap connect is tried it returns an "invalid credentials".
ldap cannot be killed as well.
Still hoping for a solution.
Christian
-
- Advanced member
- Posts: 140
- Joined: Fri Sep 12, 2014 10:02 pm
Zimbra not starting
I've got the same issue I had a power outage that killed my router, which I replaced but had to re-ip as a result.
The problem is that ZCS will not start other than starting ldap, none of the other services will work. I am running zcs3.1.4GA518 on SUSE10, and until yesterday was very happy running ZCS along side an Apache installation on the same box. ZCS is configured to use https only, which enables the two to run together in harmony.
The worst part is that zimbra.log just complains that "zimbramon[13564]: 13564:info: 2006-08-30 10:08:01, STATUS: : Cannot: determine"
I can access the website without issue, but I'm blind without ZCS. As there are only about 10 users on the box, I'm going to upgrade to ZCS4 even though it is RC1.
Any ideas?
The problem is that ZCS will not start other than starting ldap, none of the other services will work. I am running zcs3.1.4GA518 on SUSE10, and until yesterday was very happy running ZCS along side an Apache installation on the same box. ZCS is configured to use https only, which enables the two to run together in harmony.
The worst part is that zimbra.log just complains that "zimbramon[13564]: 13564:info: 2006-08-30 10:08:01, STATUS: : Cannot: determine"
I can access the website without issue, but I'm blind without ZCS. As there are only about 10 users on the box, I'm going to upgrade to ZCS4 even though it is RC1.
Any ideas?
-
- Advanced member
- Posts: 140
- Joined: Fri Sep 12, 2014 10:02 pm
Zimbra not starting
[quote user="FunkyPenguin"]I'm going to upgrade to ZCS4 even though it is RC1.
[/QUOTE]
Just tried the upgrade and bang! Got this lovely error during the upgrade:
"Wed Aug 30 10:16:17 2006: ldap startup failed with exit code 1
UPGRADE FAILED - exiting"
Help, please
EDIT:
Just tried the upgrade again and got the following error repeated:
"ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mail.forcev.net:389)"
[/QUOTE]
Just tried the upgrade and bang! Got this lovely error during the upgrade:
"Wed Aug 30 10:16:17 2006: ldap startup failed with exit code 1
UPGRADE FAILED - exiting"
Help, please
EDIT:
Just tried the upgrade again and got the following error repeated:
"ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mail.forcev.net:389)"
Zimbra not starting
The obvious question, I'm afraid, do you have a backup of the original /opt/zimbra directory? If you do then you could go through the install & restore routine. If you haven't have you tried the LDP resolution steps in the wiki?
-
- Advanced member
- Posts: 140
- Joined: Fri Sep 12, 2014 10:02 pm
Zimbra not starting
I was hoping your fountain of knowledge would be available Bill
Unfortunately the only backup of /opt/zimbra I have is the nonfunctioning one that I took just before the upgrade (note to self - setup cron job for backup). I'm just about to try the wiki steps now, thanks for the link.
Unfortunately the only backup of /opt/zimbra I have is the nonfunctioning one that I took just before the upgrade (note to self - setup cron job for backup). I'm just about to try the wiki steps now, thanks for the link.