F/collectd: Available write targets:: [none]

Software SW bugs discussion
1

Executing “logread -f” on a Turris Omnia running TurrisOS 5.1.1
there are many messages like

mmm dd HH:MM:SS DEVICENAME collectd[PID]: Available write targets:: [none]

repeated every 5 seconds.

/etc/init.d/collectd stop
doesn’t stop this, but
/etc/init.d/follectd stop
does (resulting in messages like
foris-controller[PID]: WARNING:foris_controller_backends.collectd:Socket error occured ‘[Errno 2] No such file or directory’)
but that’s certainly not an option.

/etc/follectd.conf contains e.g.
LoadPlugin network
LoadPlugin unixsock
which should also be (read&)write targets according to
https://collectd.org/wiki/index.php/Table_of_Plugins
Is there another Plugin, like syslog, needed?

/etc/collectd.conf contains e.g.
LoadPlugin rrdtool
which should also be a write target.

How can I get rid of these messages?

Thanks,
Martin

2

Take a look at this issue:

Package foris-controller-collectd-module is highly experimental and I am thinking why do you have it installed.

3

Sorry, I didn’t notice https://gitlab.nic.cz/turris/turris-os-packages/-/issues/623
(even if it’s now 3 months old) and can’t remember how this package was installed (probably I thought once this is needed for something else).
Now I deinstalled the foris-controller-collectd-module
and executed “/etc/init.d/follectd stop” to get rid of the messages.
Should follectd be better deinstalled as well?

Thanks,
Martin