/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 i386
Postfix is 3.4-20190106 (the newest version in ports)
-- Over 3,500 gay marriages and, what, no hellfire? I was promise hellfire. And riots. What gives? -- Mark Morford
On 10 Apr 2019, at 08:36, @lbutlr via dovecot dovecot@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
-- "Back off, man. I'm a scientist."
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 08:36, @lbutlr via dovecot dovecot@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
Edit your 10-master.conf and make sure that the user specified in the details below matches the dovecot user:
service stats { unix_listener stats-writer { user = mailnull } unix_listener stats-reader { user = mailnull }
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot dovecot@dovecot.org wrote:
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot dovecot@dovecot.org wrote: On 10 Apr 2019, at 08:36, @lbutlr via dovecot dovecot@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
Edit your 10-master.conf and make sure that the user specified in the details below matches the dovecot user:
service stats { unix_listener stats-writer { user = mailnull } unix_listener stats-reader { user = mailnull }
Sorry, i am confused. There is no similar clock in 10-master.conf
In fact,. the string "stats" does not appear in that file at all. The commented line
#default_internal_user = dovecot
is in that file, and that is the dovecot user (as seen in the permissions above).
Should I add
service stats { unix_listener stats-writer { user = dovecot } unix_listener stats-reader { user = dovecot } }
to my dovecot.conf file?
-- I want a party where all the women wear new dresses and all the men drink beer. -- Jason Gaes
On Wed, 10 Apr 2019 at 18:06, @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot < dovecot@dovecot.org> wrote:
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot dovecot@dovecot.org wrote: On 10 Apr 2019, at 08:36, @lbutlr via dovecot dovecot@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
Edit your 10-master.conf and make sure that the user specified in the details below matches the dovecot user:
service stats { unix_listener stats-writer { user = mailnull } unix_listener stats-reader { user = mailnull }
Sorry, i am confused. There is no similar clock in 10-master.conf
In fact,. the string "stats" does not appear in that file at all. The commented line
#default_internal_user = dovecot
is in that file, and that is the dovecot user (as seen in the permissions above).
Should I add
service stats { unix_listener stats-writer { user = dovecot } unix_listener stats-reader { user = dovecot } }
to my dovecot.conf file?
Add the two blocks to 10-master.conf, before the last "}"
My dovecot runs as user mailnull. YMMV.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
On 10 Apr 2019, at 09:06, @lbutlr via dovecot dovecot@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 implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
-- I WILL NOT CARVE GODS Bart chalkboard Ep. 8F11
This is what fixed mine
service stats { # unix_listener stats-reader { # group = # mode = 0666 # user = # } unix_listener stats-writer { group = dovecot mode = 0666 user = } }
On Apr 10, 2019, at 09:43, @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 09:06, @lbutlr via dovecot dovecot@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 implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
-- I WILL NOT CARVE GODS Bart chalkboard Ep. 8F11
On 10 Apr 2019, at 10:55, Remo Mattei via dovecot dovecot@dovecot.org wrote:
This is what fixed mine
service stats { # unix_listener stats-reader { # group = # mode = 0666 # user = # } unix_listener stats-writer { group = dovecot mode = 0666 user = } }
Setting permissions to 666 never seems like a great idea.
-- But I been sane a long while now, and change is good.
On Wed, 10 Apr 2019 at 19:44, @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 09:06, @lbutlr via dovecot dovecot@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 implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
I use dovecot-lda for deliveries and would see entries in both Exim (MTA) and Dovecot log files.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
On 10 Apr 2019, at 10:43, @lbutlr via dovecot dovecot@dovecot.org wrote:
lso, the failed message strongly implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
One last thing:
https://wiki.dovecot.org/Upgrading/2.3 does not mention that stats is now required. I ignored the entire block on that page on stats because I'd never used it.
-- 'Nothing works against magic. Except stronger magic. And then the only thing that beats stronger magic is even stronger magic. And the next thing you know...' 'Phooey?' --Sourcery
On 10 April 2019 20:48 @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 10:43, @lbutlr via dovecot dovecot@dovecot.org wrote:
lso, the failed message strongly implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
One last thing:
https://wiki.dovecot.org/Upgrading/2.3 does not mention that stats is now required. I ignored the entire block on that page on stats because I'd never used it.
I guess it's that 'statistics' is kinda built-in now. So it's not like a plugin anymore. But I get your point, maybe we should clarify this better.
Aki
On 10 Apr 2019, at 11:50, Aki Tuomi via dovecot dovecot@dovecot.org wrote:
On 10 April 2019 20:48 @lbutlr via dovecot dovecot@dovecot.org wrote:
On 10 Apr 2019, at 10:43, @lbutlr via dovecot dovecot@dovecot.org wrote:
lso, the failed message strongly implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message is delivered. It might be worth changing the message or still logging the actual message delivery?
One last thing:
https://wiki.dovecot.org/Upgrading/2.3 does not mention that stats is now required. I ignored the entire block on that page on stats because I'd never used it.
I guess it's that 'statistics' is kinda built-in now. So it's not like a plugin anymore. But I get your point, maybe we should clarify this better.
Since it requires a config change, it seems something should be there.
And it looks like the necessary block could be auto-generated based on looking at 10-master.conf?
-- IT'S POTATO, NOT POTATOE Bart chalkboard Ep. 7F01
participants (4)
-
＠lbutlr
-
Aki Tuomi
-
Odhiambo Washington
-
Remo Mattei