[SOLVED] Changed MTA config and can't login

[aapthorp]

I just modified the MTA config to turn off TLS and authentication as I wanted to test a basic java client. After that I can no longer access the admin console or connect via IMAP.

zmcontrol status shows the servers running but not stats.

How do I reset the config via the command line?

Thanks

Adrian

P.S. I'm running 5.0 RC1 on Debian 4.0

[mmorse]

zmprov getServer server.domain.com | grep Auth
Should see zimbraMtaAuthEnabled, zimbraMtaAuthHost, zimbraMtaTlsAuthOnly, and zimbraMtaAuthURL might be like:
https:// server.domain.com:443/service/soap/ which should match with your zimbraMailMode
zmprov getServer server.domain.com | grep Mode

For instance:
zmprov modifyServer server.domain.com zimbraMtaAuthEnabled TRUE

[aapthorp]

Hmm, not looking good. When I try that I get

ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

[aapthorp]

Looking at my mailbox.log this appears to be a mysql connection error.

2007-12-06 21:23:52,431 INFO  [main] [] system - Setting mysql connector propert
y: maxActive=10
2007-12-06 21:23:52,432 INFO  [main] [] system - Setting mysql connector propert
y: maxActive=10
2007-12-06 21:23:57,037 FATAL [main] [] system - Config initialization failed
com.zimbra.common.service.ServiceException: system failure: getting database con
nection
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.j
ava:165)
        at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:229)
        at com.zimbra.cs.util.Config.init(Config.java:60)
        at com.zimbra.cs.util.Config.initConfig(Config.java:87)
        at com.zimbra.cs.util.Config.getString(Config.java:99)
        at com.zimbra.cs.db.Versions.checkDBVersion(Versions.java:75)
        at com.zimbra.cs.db.Versions.checkVersions(Versions.java:71)
        at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:86)
        at com.zimbra.soap.SoapServlet.init(SoapServlet.java:107)
        at javax.servlet.GenericServlet.init(GenericServlet.java:241)
        at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.jav
a:433)
        at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:25
6)
:

snip/snip

        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.mortbay.start.Main.invokeMain(Main.java:183)
        at org.mortbay.start.Main.start(Main.java:497)
        at org.mortbay.start.Main.main(Main.java:115)
Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Serve
r connection failure during transaction. Due to underlying exception: 'java.net.
SocketException: java.net.ConnectException: Connection refused'.

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused

STACKTRACE:

java.net.SocketException: java.net.ConnectException: Connection refused
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.ja
va:156)
        at com.mysql.jdbc.MysqlIO.(MysqlIO.java:276)
        at com.mysql.jdbc.Connection.createNewIO(Connection.java:2769)
        at com.mysql.jdbc.Connection.(Connection.java:1531)

I've looked around the forum and see similar problems but no solution. Any pointers appreciated.

I tried running zmmyinit but it also reports connection refused until giving up.

[soxfan]

I believe you are running into a known issue with 5.0 RC1. See this thread for discussion. Basically re-running install.sh fixes the problem. You may want to upgrade to RC2.

[aapthorp]

Thanks, this indeed did seem to be the problem.

Of course I then ran in to the DB Version problem with upgrading from RC1 to RC2 DB Version Mismatch after upgrade from RC1 to RC2

All seems to be fixed now though!