[SOLVED] imapproxy asks for sudo password on startup

[CaptainFiesta]

After a complete disaster recovery this is what I get when starting up.

Starting imapproxy...[sudo] password for zimbra:

Everything else starts fine. And yes, I did run the fixperms script!

BTW - The DR was a snap. Just did a fresh install of the same version, recovered /opt/zimbra and ran fixperms.

Any help appreciated.

[phoenix]

If this is a single server then you don't need imapproxy nor should you have it installed. Remove it with these instructions: imapproxy won't start after upgrade

[Rich Graves]

...but they'll still need sudo to work sans password for other things (postfix queue, zmcontrol).

What did your "complete disaster recovery" entail? Zimbra needs a small number of critical changes outside /opt/zimbra. One specific thing you're missing is that /etc/sudoers must include something like:

Defaults    !requiretty
%zimbra   ALL=NOPASSWD:/opt/zimbra/openldap/libexec/slapd
%zimbra   ALL=NOPASSWD:/opt/zimbra/libexec/zmslapd
%zimbra   ALL=NOPASSWD:/opt/zimbra/postfix/sbin/postfix, /opt/zimbra/postfix/sbin/postalias, /opt/zimbra/postfix/sbin/qshape.pl, /opt/zimbra/postfix/sbin/postconf,/opt/zimbra/postfix/sbin/postsuper
%zimbra   ALL=NOPASSWD:/opt/zimbra/libexec/zmqstat,/opt/zimbra/libexec/zmmtastatus
%zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmmailboxdmgr
%zimbra ALL=NOPASSWD:/opt/zimbra/bin/zmcertmgr

[CaptainFiesta]

imapproxy removed and problem solved.

Ok, the DR is an embarrasing story. Let's just say it involved an rm -rf, a moment of panic, a quick Ctrl+C followed by a totally dysfunctional system. The good news is I damaged the system but not the Zimbra data.

The system is a virtual machine so I just booted the most recent clone then mounted the busted system's virtual disk and pulled over /opt/zimbra. Not so luckily the clone was from just before I had performed a 5 to 6 upgrade a few days ago. So I had to redo that whole upgrade first.

I followed these instructions for the recovery.
Open Source Edition Backup Procedure - Zimbra :: Wiki

The system has been running for about a week and other than the imapproxy issue everything else seems to be running fine.

This is just a box for me and my family running under my desk at home so the stakes aren't that high.