Web Authen IssueAfter Reboot

[PFC-PEDER]

We are about 45 days into our 60 day trial and everything worked fine til today. I rebooted the server and now nobody can login via the web interface anymore. I can't login as an email user, or as an admin and I have no idea where to look to figure out what the issue is. The web page comes up and I login and get "The username or password is incorrect. Verify that CAPS LOCK is not on, and then retype the current username and password" when I try as a user. I know the username and password are correct and caps lock is not on. It is just not authenticating. I tried rebooting again to see if that helped, but it still is not working.

LDAP is running:

root@ubuntubert:/home/peder# ps auxww | grep zimbra | grep slapd
zimbra 4022 0.0 0.3 25956 4076 ? Ssl 12:38 0:00 /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h
ldap://ubuntubert.packetfoundry.net:389 -f /opt/zimbra/conf/slapd.conf

root@ubuntubert:/home/peder# su zimbra
zimbra@ubuntubert:/home/peder$ ldap status
slapd running pid: 4022


SASL is running:

zimbra@ubuntubert:/home/peder$ ps ax | grep sasl
4841 ? Ss 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
4842 ? S 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
4843 ? S 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
4844 ? S 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
4845 ? S 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
6380 pts/0 S+ 0:00 grep sasl


I am getting the following in mailbox.log:

2007-08-06 12:53:04,554 INFO [http-80-Processor99] [ua=ZimbraWebClient - FF2.0 (Win)/undefined;ip=192.168.1.100;] SoapEngine - handler exception
com.zimbra.cs.account.AccountServiceException: authentication failed for peder@testtesttest.com
at com.zimbra.cs.account.AccountServiceException.AUTH _FAILED(AccountServiceException.java:87)
at com.zimbra.cs.service.account.Auth.handle(Auth.jav a:111)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:270)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:168)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:90)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)



I see that it says "auth failure", but it doesn't really help as to where the failure occurs. Any ideas? Again, this worked fine for probably 40+ days and when I rebooted the server, evidently something didn't come up right and it won't let anybody login for email or admin.


Peder

[PFC-PEDER]

As a followup to my own post, it appears that it is rejecting all email with a 550 reply as well. So it appears that it can't do database lookups maybe? MySQL is running:

root@ubuntubert:/home/peder# ps ax | grep mysql
4114 ? S 0:00 /bin/sh /opt/zimbra/logger/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.logger.cnf --ledir=/opt/zimbra/logger/mysql/libexec
4165 ? Sl 0:32 /opt/zimbra/logger/mysql/libexec/mysqld --defaults-file=/opt/zimbra/conf/my.logger.cnf --basedir=/opt/zimbra/logger/mysql --datadir=/opt/zimbra/logger/db/data --pid-file=/opt/zimbra/logger/db/mysql.pid --skip-external-locking --port=7307 --socket=/opt/zimbra/logger/db/mysql.sock
4273 ? S 0:00 /bin/sh /opt/zimbra/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.cnf --ledir=/opt/zimbra/mysql/libexec
4365 ? Sl 0:02 /opt/zimbra/mysql/libexec/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datadir=/opt/zimbra/db/data --pid-file=/opt/zimbra/db/mysql.pid --skip-external-locking --port=7306 --socket=/opt/zimbra/db/mysql.sock


Again, I'm not sure where to look for what is causing the issue. Everything worked til I rebooted.....