No HTTP and HTTPs Access

[spectra]

Env:
Release 6.0.7_GA_2473.UBUNTU8 UBUNTU8 FOSS edition.

All has been well. 2 days ago, not able to access the application via http or https.

I do have command line access to zimbra.

Is this a case of restarting the web related services ? If so how ?

I have restarted all of zimbra via the command line several times and same thing.

thanks in advance.

[y@w]

Let's start with posting the output of 'zmcontrol status' to make sure everything is up.

If it is all running, you maybe have a port conflict from another web service installed (Apache, perhaps).

[spectra]

Let's start with posting the output of 'zmcontrol status' to make sure everything is up.

If it is all running, you maybe have a port conflict from another web service installed (Apache, perhaps).

mailbox -> stopped
mysql.server is not running

stats -> stopped

these are all running
antivirus
antispam
logger
ldap
mta
spell
snmp

So how to find out what's happening with mysql why its not running

[y@w]

Check out /opt/zimbra/log/mailbox.log. It will likely be near the end of the output, but it may not. If you can't find anything, try:

zmmailboxdctl restart

and tail -f /opt/zimbra/log/mailbox.log to look for any errors from MySQL.

[spectra]

Looks like a bunch of JDBC related errors.
Basically, it's not able to connect to the database.
Should we try restarting the mysql database ? What's the zimbra way of doing that ?

zimbra@mail:~$ zmcontrol status
Host mail.southfieldcomputeroutlet.org
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
mysql.server is not running.
mta Running
snmp Running
spell Running
stats Stopped

So I guess if mysql is not running then the application is dead. Please advise on how to restart mysql or check mysql errors.

Also, let's assume mysql is corrupt someway, what alternatives do I have besides re-installing and rolling with a backup.

thanks

[y@w]

MySQL is restarted as part of mailboxd.

zmmailboxdctl restart

.. will restart it. Watch for errors in the same mailbox.log file during the start.

[spectra]

From the log all I see is JDBC related errors. Basically, not able to connect to database.

zmmailboxdctl stop and zmmailboxdctl start via comand line completes fine. Again, the log shows unable to connect to mysql server.
This approach isn't starting up the mysql server.

Any other ideas ?

Thanks in advance

[y@w]

There has to be more going on in that log file.

You can also try starting mysql directly from its init script at /opt/zimbra/bin/mysql.server

[spectra]

2010-09-10 00:00:07,062 WARN [main] [] misc - Could not establish a connection to the database. Retrying in 5 seconds.
com.zimbra.common.service.ServiceException: system failure: getting database connection
ExceptionId:main:1284091207062:468a56983aa25435
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.j
ava:248)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 328)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 293)
at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.jav a:198)
at com.zimbra.cs.db.DbPool.startup(DbPool.java:189)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:156)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:123)
at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 125)
at javax.servlet.GenericServlet.init(GenericServlet.j ava:241)
at org.mortbay.jetty.servlet.ServletHolder.initServle t(ServletHolder.jav
a:440)
at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:26
3)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:
50)
at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.ja
va:685)


Does this help any ? This is all repeated many times in the log file.
I agree something happened, just trying to determine what.
Thanks inadvance.

[y@w]

No, that's just other parts of Zimbra complaining it can't get to MySQL. One thing that may be helpful is to stop Zimbra entirely and try to just start MySQL.

zmcontrol stop

then

/opt/zimbra/bin/mysql.server start

That may spit something out to the screen, but I'd also tail mailbox.log while it's trying to start. If it's a problem that's occurring after MySQL start, that script may finish and say all is well when it's really not.