"rrdtool restore" always segfaults on R4S

[spence]

Greetings,

On my

FriendlyElec NanoPi R4S

{
	"kernel": "5.15.167",
	"hostname": "R4S-wrt",
	"system": "ARMv8 Processor rev 4",
	"model": "FriendlyElec NanoPi R4S",
	"board_name": "friendlyarm,nanopi-r4s",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.5",
		"revision": "r24106-10cc5fcd00",
		"target": "rockchip/armv8",
		"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
	}
}

the rrdtool restore command always segfaults. Well, it looks to be with the message.
It works fine on my tp-link EAP-225.
On both, I tested with OpenWrt 2022-03-3 and 2023-05-5.
No entries show up in logread or dmesg.

root@R4S-wrt:~# rrdtool dump /tmp/rrd/OpenWrt/load/load.rrd >/tmp/test.xml
root@R4S-wrt:~# rrdtool restore /tmp/test.xml /tmp/test.rrd
Segmentation fault
root@R4S-wrt:~#
root@R4S-wrt:~# ls -l /tmp/test*
-rw-r--r--    1 root     root             0 Feb 10 13:14 /tmp/test.rrd
-rw-r--r--    1 root     root        594114 Feb 10 13:14 /tmp/test.xml
root@R4S-wrt:~#

I have tested with rrd files from both boxes to the other box and it always and only happens on the R4S.

I originally found this trying to restore an edited .xml from rrdtool dump but I get the same results from an unedited dump file. The edited .xml file restores fine on the EAP-225.

I'm hoping for an easy fix for this but I suspect it might be a real problem on the build for the R4S.
Any Ideas?

Also, if you use luci-app-statistics or collectd on an R4S I would appreciate it if you would test rrdtool restore and report back. I can provide some guidance if it is new to you.

Thanks.

[spence]

Well, it isn't fixed in v23.05.5 but I installed 24.10.0 on my R4S this morning and rrdtool restore works on it.

I'm able to edit the bad data out of of the rrd file so my graphs don't have huge spikes in them anymore. Now to see if I can find a fix for the spikes when the router reboots or I do service collectd restart when testing the config on a new-to-me plugin.