Huge Problem, CPanel Works - Mailbox Doesn't

[CalmingStorm]

Basically, out of the blue we lost Access to our Zimbra server.

We're running 7.1.4, I was told upgrading to 7.2 would not solve this issue - we can bring up the login page intermittently, however it will time out if we enter credentials and try to login, giving a ""???remote.TIMEOUT???"" message.

Admin Panel works fine, all features are functional, everythings great....

This happened after our internet went down, though I do not think that has anything to do with it.

I've restarted the server, restarted the services - I'm not sure what else to do, this is for the company I work for and a lot of other people use this software, I'm the one who set it up/installed, though.

[justdave]

Anything useful in the logs? Are you using zimbra-proxy or just a straight-up mailbox server?

Logs are in /opt/zimbra/log and /var/log. Often if something isn't starting up correctly it'll log errors when it tries to.

[CalmingStorm]

Straight up mail server - I upgraded to 7.2.0, no change. If I freshly restart all of the services - it works for 30 seconds. Admin panel is always up, still.

Nothing useful in the logs, at least that I can see.

[CalmingStorm]

I found the following in var/log/zimbra, also - my mailbox.log in /opt/zimbra/log gets to be around 200-400 MB A Day, I deleted it yesterday to gather some more refined information about the problem - and it's already back to 300 megs.

The log is basically filled with our 100+ subscribed calendars pulling information.

Could this be bringing down the mail server?

May  4 10:04:39 zimbra postfix/postqueue[30365]: fatal: Queue report unavailable - mail system is down
May  4 10:05:09 zimbra postfix/postqueue[30387]: fatal: Queue report unavailable - mail system is down
May  4 10:05:26 zimbra slapd[874]: slap_queue_csn: queing 0x7f0949ffc420 20120504140526.137508Z#000000#000#000000
May  4 10:05:26 zimbra slapd[874]: slap_graduate_commit_csn: removing 0x86b53b0 20120504140526.137508Z#000000#000#000000

[justdave]

Sounds like postfix isn't running. I would try to do (as the zimbra user) "postfix stop" followed by "postfix start" and then check the logs and see if you can find the entries right about the time you tried to restart it. There's probably something different there that tells why it isn't starting that only shows up right during the startup attempt.