-->September 6th, 2025<--
Thank you to GolfCharlie and Claude Code for fixing the code to work with the newly changed FAA API! They have saved a lot of time. A new image has been created and will be uploaded today and available later tonight. If you don't want or need the image, you can visit https://github.com/markyharris/livesectional and incorporate the changes into your board now.
--->September 5th, 2025<--
There has been another change to the FAA API which has again broke the map. We are currently working on this. Check back for fix. If you have the fix please post it. - Mark
Currently running LiveSectional v4.503 on a RasPi Zero 2 Rev 1.0 and regularly have random freezes of everything, either locking my map up with the last pulled METAR data/lights, or with nothing lit up due to it happening while my map is in sleep mode. I enabled debug logging with the hopes of catching something as other posts have suggested here, but when I reboot the pi and pull off all available log files (I've only ever seen logfile.log and logfile.log.1), they are full of 21,000+ lines of logs only from the most recent reboot (i.e., nothing that persisted from the previous running environment when the "freeze" occured).
Worth noting, when the freeze occurs, there is no connectivity via web or SSH (the pi doesn't even return a ping). My next step would be to potentially hook up a monitor and see what the console shows (if anything) when a crash happens - but I would like to avoid that if at all possible. Any thoughts/suggestions/comments would be greatly appreciated, and apologies if I somehow missed a post on this exact scenario (I've searched a good bit so far). Thanks in advance!
Hi, sorry for the issues. I believe I ran into something similar with a Zero and it was due to the fact that the log files were taking up so much space that the RPi couldn't access the SD card properly. I turned off the logging to test it and it seemed to work. However, you may need to delete the current log files to loosen up the space.
Another thought, there is a feature where you can expand the memory of the SD card to give the RPi access to all the memory. It's under the utilities menu.
Try these and let us know. If this doesn't help, then it may be necessary to get the info from the command line to properly debug. - Mark
Thank you, Mark, for your reply. I expanded the usable memory and also lowered the logging level - hopefully that will help! It makes total sense that the Pi Zero would run out of memory to handle 21k+ logging.
So far, it has been running for ~18 hours, which is the longest stretch I've seen yet. I'm cautiously optimistic, but worst case, I'll just swap the Pi Zero out for a big brother model.
