Hi Guys, I am trying to use 2 instances of Dovecot on the same server so I can have a Director managing my connections, everything appears to be working, but I can not use doveadm to control my 2nd instance, but doveconf seems to work fine. [user at server logs]$ doveconf -i Director | grep logs debug_log_path = /home/user/apps/logs/director/director_debug.log info_log_path = /home/user/apps/logs/director/director_info.log log_path = /home/user/apps/logs/director/director.log info_log_path = /home/user/apps/logs/director/director_lmtp.log [user at server logs]$ doveadm -i Director log find Debug: /home/user/apps/logs/dovecot_debug.log Info: /home/user/apps/logs/dovecot_info.log Warning: /home/user/apps/logs/dovecot.log Error: /home/user/apps/logs/dovecot.log Fatal: /home/user/apps/logs/dovecot.log I have stopped and started both my instances so the config running is what is in the config file, but when I use -i Director with doveadm it uses the other instances config. [user at server logs]$ doveadm instance list path name last used running /home/user/apps/dovecot/var/run/dovecot Dovecot 2013-09-26 00:39:14 yes /home/user/apps/dovecot/var/run/director Director 2013-09-26 00:32:31 yes Any ideas, or does anyone have any experience with the Dovecot instance feature? Chris
On Thu, Sep 26, 2013 at 12:45:01AM -0400, Chris Lasater wrote:> I am trying to use 2 instances of Dovecot on the same server so I > can have a Director managing my connections, everything appears to > be working, but I can not use doveadm to control my 2nd instance, > but doveconf seems to work fine.I have noticed the same thing. It seems that doveadm ignores -i. "dovecot" works with -c /path/to/other/dovecot.conf, but it too ignores -i. We got the idea to try -i <instance_name> from http://wiki2.dovecot.org/Tools/Doveadm/Instance , but "doveadm help" itself does not show a -i.> I have stopped and started both my instances so the config running > is what is in the config file, but when I use -i Director with > doveadm it uses the other instances config.And this is a big problem for trying to use "doveadm director" commands when the director instance uses the nonstandard paths. I haven't found a way to do that yet! "-c /path/to/other/dovecot.conf" didn't work. http://wiki2.dovecot.org/Tools/Doveadm/Director Currently on 2.2.5, about to switch to 2.2.6 EE. It seemed like it worked back in 2.0.9 before upgrading. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
While testing some more I found out something else. I have an alias set for doveadm so it was running with sudo and that ended up being part of the issue. If doveadm is run as a regular user then the problem goes away [user at server ~]$ doveadm -i Director log find Debug: /home/user/apps/logs/director/director_debug.log Info: /home/user/apps/logs/director/director_info.log Warning: /home/user/apps/logs/director/director.log Error: /home/user/apps/logs/director/director.log Fatal: /home/user/apps/logs/director/director.log [user at server ~]$ sudo doveadm -i Director log find Debug: /home/user/apps/logs/dovecot_debug.log Info: /home/user/apps/logs/dovecot_info.log Warning: /home/user/apps/logs/dovecot.log Error: /home/user/apps/logs/dovecot.log Fatal: /home/user/apps/logs/dovecot.log Also if I run "sudo doveadm stop" to stop the main instance, I now have the ability to use the -i Director using sudo. Unfortunately this makes it difficult to manage two instances. Does anyone have an idea of getting this to work with sudo? Chris
Hi, this bug should have been fixed by Timo in some 2.1.x release. The issue should be in the list archives too. Which version are you using? BTW: I'm still using doveadm -c /etc/dovecot-director/dovecot- director.conf director status to address the director instance. Regards Daniel