From: Michael Tremer <michael.tremer@ipfire.org>
To: Robin Roevens <robin.roevens@disroot.org>
Cc: development@lists.ipfire.org
Subject: Re: Collectd openvpn plugin: failed to get data from: /var/run/ovpnserver.log
Date: Mon, 21 Jul 2025 10:20:19 +0100 [thread overview]
Message-ID: <B8C5AF7B-E133-45F7-98EA-C792A545DADB@ipfire.org> (raw)
In-Reply-To: <20250719211856.160291-1-robin.roevens@disroot.org>
Hello Robin,
Good catch. Your patch is what we needed.
Thank you. I just merged it into next.
-Michael
> On 19 Jul 2025, at 22:10, Robin Roevens <robin.roevens@disroot.org> wrote:
>
> Hi all
>
> I noticed this error in the systemlog of my ipfire core 197 test
> machine:
> ---
> Jul 19 23:44:05 ipfire-test collectd[2452]: openvpn plugin: failed to get data from: /var/run/ovpnserver.log
> Jul 19 23:44:05 ipfire-test collectd[2452]: read-function of plugin `openvpn/ovpnserver.log' failed. Will suspend it for 240.000 seconds.
> ---
>
> I think this is fixed by changing collectd.vpn config using the new /var/run/openvpn-rw.log, so I created a patch for that.
> I don't know if there is functionality in collectd to use the new helper
> binary /usr/local/bin/openvpnctrl output instead of the file? If that is
> the case, that is then probably a better solution than my patch.
>
> Regards
> Robin
>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
>
prev parent reply other threads:[~2025-07-21 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 21:10 Robin Roevens
2025-07-19 21:10 ` [PATCH] collectd: Openvpn-2.6: fix statusfile name Robin Roevens
2025-07-21 9:20 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B8C5AF7B-E133-45F7-98EA-C792A545DADB@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=robin.roevens@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox