Cron job to clear lighttpd cache?


#1

Twice now I’ve run into trouble with my pi-hole server failing to deliver graphic data in the browser. The first time I largely ‘gave up’ and just re-installed. The second time I did some digging and determined it was the lighttpd server compression cache. Some of the js pages weren’t getting compressed or sent properly. The side-effect was the browsers (chrome, ie, edge and firefox) all failing to show any graphs. Just the spinning arrow icons.

If I disabled the compression config lines in /etc/lighttpd/lighttpd.conf the problem goes away. If I manually delete the contents of /var/cache/lighttpd/compress it also solves the problem.

I’ve no idea how or why lighttpd suddenly decided to fail on just those files. I don’t have enough logging data to tell me anything useful.

So I’m wondering if it might be useful to have either an automatic cron job or have it part of pi-hole’s web UI to purge this data?


#3

It would be better to contact lighttpd’s developers to figure out the cause of the problem instead of adding a band-aid solution.


#4

Well, considering it’s installation was wrapped into the install process for pi-hole, it would seem like a reasonable place to start. Especially since pi-hole is already providing the UI and framework to accommodate something like this.

But hey, whatever, it’s not a hill to die on. Anyone else running into oddball lack of graphics problems, check your lighttpd cache directories.