Luci_statistics changes cannot be applied (turning forever)

I tried to get my graphs working. And it turned out that collectd complained about it’s config file not beeing there (was set to /var/collectd/conf.d but this doesn’t exist) so I changed my config file in the collectd settings of the graphs in luci to /etc/collectd.conf which made the “Save & Apply” spinning forever. When I try a /etc/init.d/luci_statistics restart in the console I see hundreds of this messages flying by:

configfile: Not including `/etc/collectd.conf' because the maximum nesting depth has been reached.
configfile: Not including `/etc/collectd.conf' because the maximum nesting depth has been reached.
configfile: Not including `/etc/collectd.conf' because the maximum nesting depth has been reached.
....

So, I did a bit of digging in the service script /etc/init.d/luci_statistics and decided to change the config file path for collectd graphs in luci to /var/etc/collectd.conf with the same effect, then I got the same messages as above just with the new path.

It seems that the graps are working but now every change I make in luci_tries hangs. When I click on “Save & Apply in any luci settings screen” it does two things. It first applies the changes and then says “applying changes” and below “/etc/config/luci_statistics” and the “applying” icon keeps spining forever and the message also stays there.

How can I fix this behaviour to get rid of that never-ending applying of /etc/config/luci_statistics. I think the problem lies in these messages that appear when I try a “/etc/init.d/luci_statistics reload”. Maybe it’s just a matter of setting the correct path for config file. But to be honest I’m really confused an what the right settings would be.

Any help would be greatly appreciated. A luci screenshot with the statistics settings for collectd which shows the correct path would probably solve my problem.

Thanks.

It’s actually even worse. Because luci_statistics not starting correctly after I rebooted my turris luci and foris didn’t start anymore. So I had to disable collectd & luci_statistics for the time beeing until somebody can give me the solution on why I get this messages.

Hi,
did you solved this issue? I just facing it now on 3.5.8.