similar to: Error configuring unix_listener stats-writer

Displaying 20 results from an estimated 30000 matches similar to: "Error configuring unix_listener stats-writer"

2019 Feb 18
1
Error configuring unix_listener stats-writer
Am 17.02.19 um 14:45 schrieb Aki Tuomi: >> On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot at 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
2019 Feb 18
2
Error configuring unix_listener stats-writer
Am 17.02.19 um 18:27 schrieb Sami Ketola: > > >> On 17 Feb 2019, at 11.47, Peter Nabbefeld via dovecot >> <dovecot at 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)?
2019 Feb 18
1
Error configuring unix_listener stats-writer
Am 18.02.19 um 11:34 schrieb Sami Ketola: > >> On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld at 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,
2019 Feb 17
0
Error configuring unix_listener stats-writer
2019 Feb 18
0
Error configuring unix_listener stats-writer
> On 18 Feb 2019, at 12.15, Peter Nabbefeld <peter.nabbefeld at 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
2019 Feb 17
0
Error configuring unix_listener stats-writer
> On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot <dovecot at 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
2020 Oct 22
2
net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied
Hi, We are getting very occasional messags from dovecot: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux
2020 Oct 23
1
net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied
Hi! You can ignore it, or you can change the socket permissions to 0666. service stats { unix_listener stats-writer { mode = 0666 } } Aki > On 23/10/2020 17:52 mj <lists at merit.unu.edu> wrote: > > > Hi, > > Nobody? > > It happens so rarely, and the system appears to be running fine > otherwise, should I just ignore it? > > Still
2019 Apr 20
3
stats-writer error is back
Afer a reboot (and installation of postfix-3.4.5) I am getting the stat-writer permission denied error again. from doveconf -n service stats { unix_listener stats-reader { user = dovecot } unix_listener stats-writer { user = dovecot } } # ls -ls /var/run/dovecot/stats-writer 0 srw-rw---- 1 dovecot dovecot 0 Apr 20 04:34 /var/run/dovecot/stats-writer Apr 20 04:45:00 mail
2019 Jan 08
1
Permission error on stats writer
I?m running Dovecot 2.3.4 on FreeBSD 11.2 with qmail. In my mail log, I see messages like this on every delivery Jan 8 10:30:02 v1 qmail: 1546961402.314222 delivery 533: success: lda(matt,)Error:_net_connect_unix(/var/run/dovecot/stats-writer)_failed:_Permission_denied/did_0+0+1/ Searching for this error, I found a message on a support forum for a different server that suggested adding this to
2019 Apr 10
3
/var/run/dovecot/stats-writer) failed: Permission denied
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail: > > /var/run/dovecot/stats-writer: > 0 srw-rw---- 1 root dovecot 0 Apr 10 08:47 stats-writer
2018 Aug 11
2
dovecot stats-writer socket permissions
I have seen this thread about being able to run doveadm as a non-root user, but I don't understand the solution even though I have seen other pages give this link as the solution. http://bit.ly/2MC5oq9 What configuration is necessary so that I can set the permissions on /var/run/dovecot/stats-writer socket-file so when dovecot starts my virtual mail account has read/write access? I saw
2020 May 25
3
child killed by signal 6
Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my telnet session might help: a11 fetch 1 all * 1 FETCH (RFC822.SIZE 16750 INTERNALDATE
2019 Apr 10
5
/var/run/dovecot/stats-writer) failed: Permission denied
On 10 Apr 2019, at 09:06, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > Should I add > > service stats { > unix_listener stats-writer { > user = dovecot > } > unix_listener stats-reader { > user = dovecot > } > } > > to my dovecot.conf file? I did this and it appears to have fixed the issue. Also, the failed message strongly
2019 Apr 10
3
/var/run/dovecot/stats-writer) failed: Permission denied
I am getting this error in logs net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) and I looked around the google results and it seems to be related to using service stats, which I am not using. # doveconf -n | grep stat # doveconf -n | head -3 # 2.3.5.1 (7ec6d0ade): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.5 (2483b085) # OS: FreeBSD 11.2-RELEASE-p4
2019 Apr 20
2
stats-writer error is back
On 20 Apr 2019, at 14:05, Larry Rosenman via dovecot <dovecot at dovecot.org> wrote: > service stats { > unix_listener stats-reader { > group = mail Why would I change the group from the group the socket is using? > mode = 0666 That cannot possibly be best practice. I'm not opening up any part of my mail stack to all processes. >> # ls -ls
2019 Nov 01
2
Bug report
Hello, I've got a problem fetching my emails using getmail. First question is, of course, what's causing the problems. I'm going to think that getmail get's an error code from dovecot when trying to connect and just signals the most common error, so it seems to be a problem with dovecot. Sorry but I cannot upload any files with the silly web interface of my provider, so I cannot
2018 Feb 07
1
stats-writer failed: Permission denied
Hi there! Since i compile my own dovecot (not using dovecot from debian), i get this error on each startup dovecot with systemd Feb 07 11:16:35 aldebaran dovecot[7455]: imap: Error: net_connect_unix(/usr/local/var/run/dovecot/stats-writer) failed: Permission denied Feb 07 11:16:35 aldebaran dovecot[7455]: imap: Error: net_connect_unix(/usr/local/var/run/dovecot/stats-writer) failed:
2016 Aug 19
3
Change dovecot hostname
I have noticed that the name of my private server running dovecot appears in email headers rather than the public-friendly name of my server. Is there a method to specify an alternate server name for the dovecot server to use for itself in the dovecot configuration files? I performed a few Google searches and was not able to find the answer to my question. ------- user at server1:~$ dovecot
2019 Oct 02
2
Home Directory Creation
On 10/1/2019 11:42 PM, Aki Tuomi via dovecot wrote: > Can you configure mail_debug=yes, try again, and post the logs? > > Aki Hello Aki, This is the only piece of relevant info I've been getting in the logs, and I'm trying to figure out how I can get more debug data on this: Oct 02 07:34:09 imap(asai2 at triata.globalchange.media)<43553><9fylXO6TtycKCgDu>: Debug: