| 2023-01-25 06:52:57 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2023-01-25 06:53:05 |
Christian Ehrhardt |
bug watch added |
|
https://github.com/collectd/collectd/issues/3963 |
|
| 2023-01-25 06:53:05 |
Christian Ehrhardt |
bug task added |
|
wormly-collectd |
|
| 2023-01-25 06:53:24 |
Christian Ehrhardt |
bug |
|
|
added subscriber Jussi Mäkinen |
| 2023-01-25 07:01:33 |
Christian Ehrhardt |
description |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro:
$ apt install collectd
Change default config to:
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
$ rm -rf /var/lib/collectd/rrd/*
Check the service output:
$ journalctl -f -u collectd
$ systemctl restart collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios. |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro:
$ apt install collectd
Change default config to:
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
# restart once to enable caching
$ systemctl restart collectd
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios. |
|
| 2023-01-25 07:03:29 |
Christian Ehrhardt |
description |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro:
$ apt install collectd
Change default config to:
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
# restart once to enable caching
$ systemctl restart collectd
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios. |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro:
$ apt install collectd
Change default config to:
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
# restart once to enable caching
$ systemctl restart collectd
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios.
Sadly this is racy, in 1 of 10 cases I got:
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd) failed: /var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd: illegal attempt to update using time 1674629134 when last update time is 1674629143 (minimum one second step)
In the others I got only the more expected (and IMHO ok):
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd) failed: opening '/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd': No such file or directory |
|
| 2023-01-25 07:14:17 |
Christian Ehrhardt |
description |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro:
$ apt install collectd
Change default config to:
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
# restart once to enable caching
$ systemctl restart collectd
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios.
Sadly this is racy, in 1 of 10 cases I got:
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd) failed: /var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd: illegal attempt to update using time 1674629134 when last update time is 1674629143 (minimum one second step)
In the others I got only the more expected (and IMHO ok):
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd) failed: opening '/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd': No such file or directory |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro (not a 100% hit rate yet):
# Install packages
$ apt install collectd collectd-utils rrdtool
Change default config to (not sure if all are required):
$ vim /etc/collectd/collectd.conf
...
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
...
a) as reported upstream
# Enable new config and clean old data
$ systemctl stop collectd
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl start collectd
b) as I've found it on my system
# restart once to enable the new config
$ systemctl restart collectd
# let it collect some data
$ sleep 120s
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Then check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios.
Sadly this is racy, in 1 of 10 cases I got:
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd) failed: /var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd: illegal attempt to update using time 1674629134 when last update time is 1674629143 (minimum one second step)
In the others I got only the more expected (and IMHO ok):
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd) failed: opening '/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd': No such file or directory |
|
| 2023-01-25 07:18:13 |
Christian Ehrhardt |
description |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro (not a 100% hit rate yet):
# Install packages
$ apt install collectd collectd-utils rrdtool
Change default config to (not sure if all are required):
$ vim /etc/collectd/collectd.conf
...
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
...
a) as reported upstream
# Enable new config and clean old data
$ systemctl stop collectd
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl start collectd
b) as I've found it on my system
# restart once to enable the new config
$ systemctl restart collectd
# let it collect some data
$ sleep 120s
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Then check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios.
Sadly this is racy, in 1 of 10 cases I got:
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd) failed: /var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd: illegal attempt to update using time 1674629134 when last update time is 1674629143 (minimum one second step)
In the others I got only the more expected (and IMHO ok):
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd) failed: opening '/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd': No such file or directory |
This is a spin off from bug 1971093, not a regression as we had no collectd at all, but waiting on Upstream to respond.
We will link the upstream case and chime in there, hoping to get some insight.
Issue: https://github.com/collectd/collectd/issues/3963
Repro (not a 100% hit rate yet):
# Install packages
$ apt install collectd collectd-utils rrdtool
Change default config to (not sure if all are required):
$ vim /etc/collectd/collectd.conf
...
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
CacheTimeout 10
CacheFlush 900
RandomTimeout 5
WritesPerSecond 50
...
a) as reported upstream
# Enable new config and clean old data
$ systemctl stop collectd
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl start collectd
b) as I've found it on my system
# restart once to enable the new config
$ systemctl restart collectd
# let it collect some data
$ sleep 120s
# remove files, restart again
$ rm -rf /var/lib/collectd/rrd/*
$ systemctl restart collectd
Then check the service output:
$ journalctl -u collectd
Notes:
- I can only see that
a) while stopping the service
b) after deleting DataDir
Others (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/comments/33) have reported to see it more than once. I'm unsure if failing with a warning on deleted data is too much of a real problem. We need to find if this can also occur in other more critical scenarios.
Sadly this is racy, in 1 of 10 cases I got:
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd) failed: /var/lib/collectd/rrd/j.lxd/disk-loop8/disk_time.rrd: illegal attempt to update using time 1674629134 when last update time is 1674629143 (minimum one second step)
In the others I got only the more expected (and IMHO ok):
rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd) failed: opening '/var/lib/collectd/rrd/j.lxd/battery-0/capacity.rrd': No such file or directory |
|
| 2023-01-25 07:21:05 |
Christian Ehrhardt |
bug watch added |
|
https://github.com/collectd/collectd/issues/230 |
|
| 2023-01-25 07:21:05 |
Christian Ehrhardt |
bug watch added |
|
https://github.com/collectd/collectd/issues/781 |
|
| 2023-01-25 07:21:10 |
Christian Ehrhardt |
collectd (Ubuntu): status |
New |
Incomplete |
|
| 2023-01-25 08:48:12 |
Bug Watch Updater |
wormly-collectd: status |
Unknown |
New |
|
