My BrewPi has been acting up lately. Among other things, the time it takes to export the current beer to CSV has gone way up. This used to be effectively an immediate download but can now take 1+ minutes and sometimes doesn’t even complete.
In fact I have a pretty solid repro case where if I take an otherwise well-behaved BrewPi and ask for a refreshed main graph and then a CSV download prior to the graph being replotted, the Pi’s web page eventually becomes unresponsive and the IP address no longer returning pings on my home network, forcing me to go and do a cold restart of both Spark and Pi. The Pi can run fine for days prior to becoming unresponsive with these steps, so I can’t believe that it ‘going dark’ is 100% coincidental.
The first thing I want to do in addressing this issue is get rid of old JSON data. What is the location of the logged data, and is it just a case of deleting any files written / touched on some specific dates? I’d rather root out specific beers if that’s possible. Some of my logged beers are less important than others.
p.s. the Pi is on a reserved IP address within my LAN, so I don’t have a reason to suspect this is related to IP routing issues
p.p.s. I have tried to remove entire directories from /home/brewpi/data using “rm -r …”, but this doesn’t seem to cause the data to actually go away. By that I mean that I can still see the deleted beer in the dropdown of previous beers, refreshing the browser page doesn’t cause the line item to disappear from the dropdown, and I can still download the relevant CSV data.