[SOLVED] mailbox/zmmailboxdctl won't start after power failure

[jeffw]

I just had a UPS fail and not keep my zimbra box up during an unscheduled power outage.

zmcontrol status shows:

zimbra@fs1:~$ zmcontrol status
Host fs1.rfc1918.smoe.org
        antispam                Running
        antivirus               Running
        ldap                    Running
        logger                  Running
        mailbox                 Stopped
                zmmailboxdctl is not running
        mta                     Running
        snmp                    Running
        spell                   Running
        stats                   Running

Here's the log from zmmailboxd.out. It's complaining about /opt/zimbra/jetty-6.1.5/etc/jetty.xml . That file looks like it is full of nulls:

zimbra@fs1:~/jetty-6.1.5/etc$ od -ac jetty.xml
0000000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul
\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
*
0035420 nul nul nul
\0 \0 \0
0035423

Any ideas?

CompilerOracle: exclude com/zimbra/cs/session/SessionMap.putAndPrune
0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay
.log) via org.mortbay.log.Slf4jLog
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
1869 WARN  [main] log - FATAL@file:/opt/zimbra/jetty-6.1.5/etc/jetty.xml line:1 
col:1 : org.xml.sax.SAXParseException: Content is not allowed in prolog.
1875 WARN  [main] log - EXCEPTION 
org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un
known Source)
        at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispat
ch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
        at org.mortbay.xml.XmlParser.parse(XmlParser.java:188)
        at org.mortbay.xml.XmlParser.parse(XmlParser.java:204)
        at org.mortbay.xml.XmlConfiguration.<init>(XmlConfiguration.java:101)
        at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:963)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        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)

[jeffw]

also worth noting that there are 3 xml files in that directory filled with nulls:

-r--r----- 1 zimbra zimbra 15123 Dec 8 01:18 jetty.xml
-rw-r----- 1 zimbra zimbra 15123 Dec 8 01:18 jetty.xml.in
-rw-r----- 1 zimbra zimbra 12345 Dec 8 01:18 zimbra.web.xml.in

[jeffw]

I restored those 3 files from a backup and it looks like it's working now.