Was Rock Solid, Now Tomcat will not start.

[dkarp]

In LDAP, on your server object. Settable via zmprov and possibly also from the admin console, as well.

[venaro]

Originally Posted by dkarp

In LDAP, on your server object. Settable via zmprov and possibly also from the admin console, as well.

Sorry, I am not familiar with the zmprov command, and I can not get to my admin console while everything is down like this.

Please break it down for me.

Thanks

[bobby]

it looks like tomcat is the only thing not running. check the output of the following commands (venaro.net is the zmhostname?):

zmhostname
host venaro.net
/sbin/ifconfig -a
cat /etc/hosts
zmprov -l gs venaro.net | grep Bind

[venaro]

Originally Posted by bobby

it looks like tomcat is the only thing not running. check the output of the following commands (venaro.net is the zmhostname?):

zmhostname
host venaro.net
/sbin/ifconfig -a
cat /etc/hosts
zmprov -l gs venaro.net | grep Bind

here are the outputs requested.
the zmprov command puked.



[zimbra@zeplin openldap-data]$ cd ..
[zimbra@zeplin ~]$ zmhostname
venaro.net
[zimbra@zeplin ~]$ /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0E:A6:5A:AC6
inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1005595 errors:0 dropped:0 overruns:0 frame:0
TX packets:1364410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:118321800 (112.8 MiB) TX bytes:1650002640 (1.5 GiB)
Interrupt:185

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1513674 errors:0 dropped:0 overruns:0 frame:0
TX packets:1513674 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:476768212 (454.6 MiB) TX bytes:476768212 (454.6 MiB)

#cat /etc/hosts

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.2.101 venaro.net

zmprov -l gs venaro.net | grep Bind
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException venaro.net:389)
[zimbra@zeplin ~]$

[venaro]

Restrarted zimbra and retried teh zmprov, here is the output:


[zimbra@zeplin ~]$ zmprov -l gs venaro.net | grep Bind
zimbraImapBindOnStartup: TRUE
zimbraImapBindPort: 143
zimbraImapProxyBindPort: 143
zimbraImapSSLBindOnStartup: TRUE
zimbraImapSSLBindPort: 993
zimbraImapSSLProxyBindPort: 993
zimbraLmtpBindOnStartup: FALSE
zimbraLmtpBindPort: 7025
zimbraNotifyBindPort: 7035
zimbraNotifySSLBindPort: 7036
zimbraPop3BindAddress: 192.168.11.3
zimbraPop3BindOnStartup: TRUE
zimbraPop3BindPort: 110
zimbraPop3ProxyBindPort: 110
zimbraPop3SSLBindOnStartup: TRUE
zimbraPop3SSLBindPort: 995
zimbraPop3SSLProxyBindPort: 995
[zimbra@zeplin ~]$ ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException venaro.net:389)
-bash: syntax error near unexpected token `('
[zimbra@zeplin ~]$ [zimbra@zeplin ~]$
-bash: [zimbra@zeplin: command not found
[zimbra@zeplin ~]$

[dkarp]

zmprov -l ms venaro.net -zimbraPop3BindAddress 192.168.11.3

[venaro]

Originally Posted by dkarp

zmprov -l ms venaro.net -zimbraPop3BindAddress 192.168.11.3

Thank you!

A mod of the above command fixed my problem.

# zmprov -l ms venaro.net zimbraPop3BindAddress $current_ip


Thank you to everyone that replied. Everything is working perfectly again.

[zzzzsg]

Hi dkarp

Since you are a Zimbra employee, i want to suggest this -
why should Zimbra's Postfix and Cyrus stop working when Tomcat stops?

Shouldn't the Java application be separated from the MTA and IMAP
so that users can still access their emails using email imap clients like
Thunderbird or Outlook when Tomcat fails?

We have encountered a couple of instances of Tomcat stopping and we couldn't access our mails at all not even using Thunderbird. Increasing the heap size in once instance fixed the problem in one instance. Also, there were many times the logger stoped and the MTA/IMAP was also affected and we had to restart Zimbra.

Postfix/Cyrus should run all the time even if all the other Zimbra services fail.

Thank you.

Gui

Originally Posted by dkarp

My bet is that you've still got zimbraPop3BindAddress set to the old IP. You should also check zimbraPop3SSLBindAddress, zimbraImapBindAddress, and zimbraImapSSLBindAddress.

[dkarp]

Originally Posted by zzzzsg

\why should Zimbra's Postfix and Cyrus stop working when Tomcat stops?

"tomcat" is the Zimbra mail server. postfix delivers mail to it, and tomcat provides the SOAP and IMAP interfaces to users. Take it away and postfix has nowhere to deliver mail to (so the mail is marked as deferred) and there's nowhere for clients to connect to.

The only pieces of Cyrus in the system are used for authenticated SMTP, I believe.