Package: collectd
Version: 4.4.2-3
Severity: normal

A system I have collectd installed on, and sending to a remote collectd
server via the network plugin, was taken offline, and was rebooted in
that state. An excerpt of the log after the reboot:

Aug 18 08:12:36 beaver NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (I
P Configure Start) started...
Aug 18 08:12:37 beaver dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67
 interval 10
Aug 18 08:12:37 beaver collectd[2613]: getaddrinfo (kitenet.net, 25826): Name 
or service not known
Aug 18 08:12:37 beaver collectd[2616]: getaddrinfo (kitenet.net, 25826): Name 
or service not known
Aug 18 08:12:37 beaver collectd[2616]: cpufreq plugin: Found 2 CPUs
Aug 18 08:12:37 beaver collectd[2616]: plugin_dispatch_values: No write 
callback has been registered. Please load at least one plugin that provides a 
write function.
Aug 18 08:12:37 beaver collectd[2616]: plugin_dispatch_values: No write 
callback has been registered. Please load at least one plugin that provides a 
write function.
Aug 18 08:12:37 beaver collectd[2616]: plugin_dispatch_values: No write 
callback has been registered. Please load at least one plugin that provides a 
write function.
Aug 18 08:12:37 beaver collectd[2616]: plugin_dispatch_values: No write 
callback has been registered. Please load at least one plugin that provides a 
write function.
Aug 18 08:12:37 beaver collectd[2616]: plugin_dispatch_values: No write 
callback has been registered. Please load at least one plugin that provides a 
write function.

collectd continued to log the same line, several dozen times in a row,
every 10 seconds while the network was down. This resulted in some 500 mb
of log files being written to disk. With a longer network downtime and a
smaller disk, this would fill the disk. I suggest collectd be fixed to
log only once.

Further, once the network came back up, collectd did not notice and
continued to fail. Looks like the network plugin failed once at the
beginning, and did not retry connecting? Surely it should retry
occasionally?

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to