Still having some trouble with director. I have copied the var/run/dovecot 
director along with the /etc/dovecot directory. So I know have 
/var/run/dovecot-director and dovecot-backend along with /etc/dovecot-director 
and /etc/dovecot-backend. The base_dir in these corresponds with the named 
directory in /var/run. The issue I have now is that only one instance will run 
the other outputs a bunch of errors:

root@mail1:~# service dovecot-backend start
[....] Starting IMAP/POP3 mail server: dovecot-backendError: 
service(managesieve-login): listen(*, 4190) failed: Address already in use
Error: service(pop3-login): listen(*, 110) failed: Address already in use
Error: service(pop3-login): listen(*, 995) failed: Address already in use
Error: service(lmtp): Socket already exists: 
/var/spool/postfix/private/dovecot-lmtp
Error: service(lmtp): listen(*, 24) failed: Address already in use
Error: service(imap-login): listen(*, 143) failed: Address already in use
Error: service(imap-login): listen(*, 993) failed: Address already in use
Error: service(auth): Socket already exists: 
/var/spool/postfix/private/dovecot-auth
Fatal: Failed to start listeners

i have edited the 10-master.conf file in the backend directory to use different 
port numbers but still receive the following output above.


On Sep 23, 2014, at 3:07 PM, Chris Lasater <vorg...@gmail.com> wrote:

> The configuration and run/base_dir directories can be where ever you like.  
> The locations Eduardo stated are the most appropriate for dovecot installed 
> with an RPM.  Mine were compiled and set in the home directory, so they are 
> in a slightly different location.  As long as you use the -c to point to the 
> correct configuration file you should be good.
>    For mine I kept my dovecot config file in the default location and put the 
> director one elsewhere and created an alias, so that I can start the director 
> by just typing director.  This might make things easier for you to manage, 
> then you can just stop it by running "doveadm -i <instance_name> stop"
> 
> alias director="sudo -E PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} 
> /home/user/dovecot/sbin/dovecot -c 
> /home/user/dovecot/etc/dovecot/director.conf"
> 
> 
> On 09/23/2014 05:00 PM, jjhoffart wrote:
>>> Thanks for the replies,
>>>     I am still fairly new to dovecot and still learning. This is a quick 
>>> run down of my setup: 3 servers running iRedMail (this is a package that 
>>> installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS 
>>> backend. The same 3 servers are also sitting behind a load balancer. What I 
>>> want to do is use these three servers as directors and mail servers. So 
>>> from the replies I have gotten I understand that I need to create 2 config 
>>> files 1 for director and 1 for dovecot. Now my next question is do these 
>>> config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is 
>>> creating the second config file as simple as copying and renaming the 
>>> dovecot.conf file?
>>> 
>>> On Sep 23, 2014, at 2:26 PM, Eduardo Ramos <edua...@freedominterface.org> 
>>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> In fact you don't NEED a director. You can use two dovecot servers sharing 
>>>> a NFS storage with a normal (backend) implementation. It's good to see 
>>>> that page: http://wiki2.dovecot.org/NFS for some good recomendations.
>>>> 
>>>> You must have a base_dir for each instance of dovecot you want to run, and 
>>>> a dovecot.conf as well. One could be director and other backend. I suggest 
>>>> you have two separated configuration directories, /etc/dovecot-director 
>>>> and /etc/dovecot-backend. Each with the respective configuration. Start 
>>>> dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is 
>>>> the same.
>>>> 
>>>> In order to help more, provide us more details about your environment and 
>>>> doulbts.
>>>> 
>>>> On 09/23/2014 03:57 PM, jjhoffart wrote:
>>>>> Hello,
>>>>>   I am currently trying to setup a cluster of mail servers. I currently 
>>>>> have two servers I am trying to cluster together. These servers will also 
>>>>> have a shared NFS backend. I have read on the site that I will need to 
>>>>> configure director since I am using NFS. I have read through all of the 
>>>>> documentation on director but still need a little guidance to get things 
>>>>> up and running. One of the questions I have is about the base_dir on the 
>>>>> Multiple Invocations section of the wiki. It states that I will need to 
>>>>> change the bas_dir to the new run directory, not sure what needs to 
>>>>> happen here, can anyone help me out?

Reply via email to