-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dovecot input plugin] tcp read i/o timeout since telegraf 1.18.3 -> 1.19.0 update #9415
Comments
Thanks for filing this issue. I'm trying to reproduce this in a lxd container running centos 7. I've got dovecot running, but adding your snippet to the dovecot.conf doesn't result in anything listening on port 24242 for me. Is there any other configuration required, to enable the stats output from dovecot? |
Hi @popey, thanks for looking into it. Which version of dovecot are you running? |
I'm using dovecot 2.2.36. I just did a clean container and used yum to install it. |
ok, in dovecot 2.3 the
|
Thanks for the tips. Ok, confirmed that telegraf 1.19.0 gives:-
With telegraf 1.18.3 I get:
So this looks like a regression in 1.19. Thanks again for reporting it. |
Relevant telegraf.conf:
Relevant dovecot.conf:
System info:
OS: CentOS Linux release 7.9.2009 (Core)
Uname: Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Telegraf: telegraf-1.19.0-1.x86_64
Dovecot: dovecot23-2.3.11.3-1.gf.el7.x86_64 and dovecot23-pigeonhole-2.3.11.3-1.gf.el7.x86_64
All latest updates are installed on the OS
Steps to reproduce:
Expected behavior:
Version 1.19.0 to act like 1.18.3.
In version 1.18.3 the dovecot stats were read via 127.0.0.1:24242 without any error.
Actual behavior:
Since version 1.19.0 the error (see logs below) appears.
There was no other config/update than the update from telegraf 1.18.3 -> 1.19.0.
A tcp connection to 127.0.0.1:24242 is still possible, as before
Additional info:
Just a note: As per #9223 (telegraf version 1.19.0) there were changes around this plugin made.
The text was updated successfully, but these errors were encountered: