Error configuring unix_listener stats-writer
Hello,
I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { }
unix_listener stats-writer { user = vmail group = vmail mode = 0666 } }
BTW, using imap for mail traffic.
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Kind regards
Peter
On Sun, 17 Feb 2019 10:47:29 +0100, Peter Nabbefeld via dovecot stated:
Hello,
I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { }
unix_listener stats-writer { user = vmail group = vmail mode = 0666 } }
BTW, using imap for mail traffic.
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Kind regards
Peter
"doveconf -n" should do what you want. Post the "entire output" from that command here so we an analyze it.
-- Jerry
On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot@dovecot.org> wrote:
Hello,
I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { }
unix_listener stats-writer { user = vmail group = vmail mode = 0666 } }
BTW, using imap for mail traffic.
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Kind regards
Peter
Hi
The stats-writer config belongs for service stats, not auth.
You can see effective config with 'doveconf -n'.
Aki
Am 17.02.19 um 14:45 schrieb Aki Tuomi:
On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot@dovecot.org> wrote:
Hello,
I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { }
unix_listener stats-writer { user = vmail group = vmail mode = 0666 } }
BTW, using imap for mail traffic.
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Kind regards
Peter Hi
The stats-writer config belongs for service stats, not auth.
Ooops - Thank You!
You can see effective config with 'doveconf -n'. Nope - it even displays less information than "dovecot -a".
Peter
Aki
On 18.2.2019 12.10, Peter Nabbefeld wrote:
Am 17.02.19 um 14:45 schrieb Aki Tuomi:
On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot@dovecot.org> wrote:
Hello,
I've got a very strange problem: When I try to configure the stats-writer socket, I'm told the configuration is a duplicate, though none exists in the configuration files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-master.conf: service auth { unix_listener auth-userdb { }
unix_listener stats-writer { user = vmail group = vmail mode = 0666 } }
BTW, using imap for mail traffic.
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Kind regards
Peter Hi
The stats-writer config belongs for service stats, not auth.
Ooops - Thank You!
You can see effective config with 'doveconf -n'. Nope - it even displays less information than "dovecot -a".
Peter
Aki
doveconf -n shows "what has been set", so it shows the effective configuration. There is no command to see which included file changed what.
Aki
Am 17.02.19 um 18:27 schrieb Sami Ketola:
On 17 Feb 2019, at 11.47, Peter Nabbefeld via dovecot <dovecot@dovecot.org> wrote:
Is there any tool displaying an "effective" config tree (i.e., a tool displaying the resulting configuration from every file, displaying the original file and line number)? "dovecot -a" only displays all configurations, but without source reference, so it's impossible to find out about the details. :-(
Easy way is to use just one config file. That is what I have done for years.
Sami
I'd preferred that, too, but it seems the 'modern' way - and I don't want to get any possible configuration issues on updates, so I won't change this.
Peter
On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld@gmx.de> wrote:
Am 17.02.19 um 18:27 schrieb Sami Ketola:
Easy way is to use just one config file. That is what I have done for years.
Sami
I'd preferred that, too, but it seems the 'modern' way - and I don't want to get any possible configuration issues on updates, so I won't change this.
If your distribution modifies config files on updates then it's time to switch to another distribution.
Sami
Am 18.02.19 um 11:34 schrieb Sami Ketola:
On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld@gmx.de> wrote:
Am 17.02.19 um 18:27 schrieb Sami Ketola:
Easy way is to use just one config file. That is what I have done for years.
Sami
I'd preferred that, too, but it seems the 'modern' way - and I don't want to get any possible configuration issues on updates, so I won't change this.
If your distribution modifies config files on updates then it's time to switch to another distribution.
Sami
Not the config files itself. But IIRC, the "main" config files have been changed in distros when the new style was introduced. Usually the main file wasn't overwritten, but a new file with an extension like "new" had been added.
However, my laptop installation isn't as old, and every application I install already has the new style, and of course it has it pros when You get used to the structure of the config file, but if You're new to some application, You also have to learn about this structure for every new one ...
Peter
On 18 Feb 2019, at 13.12, Peter Nabbefeld via dovecot <dovecot@dovecot.org> wrote:
Am 18.02.19 um 11:34 schrieb Sami Ketola:
On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld@gmx.de> wrote:
Am 17.02.19 um 18:27 schrieb Sami Ketola:
Easy way is to use just one config file. That is what I have done for years.
Sami
I'd preferred that, too, but it seems the 'modern' way - and I don't want to get any possible configuration issues on updates, so I won't change this.
If your distribution modifies config files on updates then it's time to switch to another distribution.
Sami
Not the config files itself. But IIRC, the "main" config files have been changed in distros when the new style was introduced. Usually the main file wasn't overwritten, but a new file with an extension like "new" had been added.
Shame on those distros.
However even if you do use such lousy distro, you can work around it by just having ONE config file in the conf.d folder. That would then be the real config file.
However, my laptop installation isn't as old, and every application I install already has the new style, and of course it has it pros when You get used to the structure of the config file, but if You're new to some application, You also have to learn about this structure for every new one ...
I wish that the split config default would have never been introduced. It's a nightmare.
Sami
participants (4)
-
Aki Tuomi
-
Jerry
-
Peter Nabbefeld
-
Sami Ketola