imapproxy fails to start but imap still working (FC4)

[sm3.142]

Hello,

I've just upgraded from a 3.1.3 setup to 4.1 which turned out to be a fairly painless job. What confuses me no end is that I cannot get the imapproxy service to start, although imap(s) is clearly still working:

$ /opt/zimbra/bin/zmcontrol start
Host gug.nodomain.com
        Starting ldap...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting imapproxy...FAILED
Starting imap4
Starting imap4s
Starting pop3
Starting pop3s
imap4 is not running
imap4s is not running
pop3 is not running
pop3s is not running

        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.

BUT

# lsof -i :993
COMMAND   PID   USER   FD   TYPE DEVICE SIZE NODE NAME
java    26559 zimbra   17u  IPv6 120258       TCP *:imaps (LISTEN)
java    26559 zimbra   35u  IPv6 120371       TCP gug.nodomain.com:imaps->tuna68.nodomain.com:47421 (ESTABLISHED)
java    26559 zimbra   40u  IPv6 121521       TCP gug.nodomain.com:imaps->tuna68.nodomain.com:57138 (ESTABLISHED)

And yes, I can retrieve/save messages via imaps just fine...

Honestly I don't know exactly what the significange of imapproxy is and I can obviously live with the situation as everything is working. However, I'd rather fix it now lest it jumps up and bites me somewhere down the road. I checked the logs in /opt/zimbra/log and also the forums, but couldn't find anything specific about this issue.

It might have something to do with this beeing a fairly 'old' setup that was incrementally upgraded from somewhere around 3.0 beta through the various 3.0 and 3.1 releases. Maybe something fell through the cracks somewhere.

Any hints?

thanks
-stefan

[ikmsupport]

We have the same problem. Any one please help us to find it.

[ikmsupport]

please help us?

[dkarp]

If you're running IMAP on 143/993, I don't think you can run imapproxy on the same box. Wouldn't you get "can't bind to that port" errors?

[demanl]

Originally Posted by dkarp

If you're running IMAP on 143/993, I don't think you can run imapproxy on the same box. Wouldn't you get "can't bind to that port" errors?

Your documentation(Zimbra's) recommends that you DO NOT run imapproxy on the same server as your zimbra webserver and TOMCAT server.....

...I was having a similar problem....imapproxy would not start...and when it did...TOMCAT would soon stop.......and once I reconfigured zimbra via the admin gui to not have any ports assigned to the imap and pop3 proxy.....my problems stopped..and everything seems to be working quite smoothly...meaning...no imapproxy...and tomcat continues to run with no dropouts or stopping....

[sm3.142]

You are right, after I removed the assigned ports for pop/pops/imap/imaps, Zimbra starts cleanly:

$ /opt/zimbra/bin/zmcontrol start
Host gug.nodomain.com
        Starting ldap...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting imapproxy...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.

Uh ok, I admit I haven't read the documentation during the upgrade

thanks
-stefan