Raspberry Pi 3 Model B Rev 1.2 - fully updated ASL3 stock.
Once it is gone I cannot ping or SSH. Has heatsinks and was in use for a few years with ASL2 without this behavior. Curious if anyone else has experienced this thx.
Clifford
I have multiple 3Bs running 24x7 that are just fine. Can you please provide more details and/or logging information?
1 Like
Thx. Would I gather those logs before the issue occurs or reboot then gather logs? Oh actually I am going to try hooking up HDMI next time it goes non-responsive and see what I get then go from there.
Ok- non-responsive- HDMI showed waiting at login- logged in- still no ping- opened asl-menu and saw message stating no ethernet interface found- thx- 3 most recent pics are for this Pi3 issue
That’s a good screenshot. You’re hitting a memory leak in Cockpit that’s a known issue in Debian 12 (not an ASL3 issue). Just close your Cockpit web interfaces when you’re not using them. If you leave a Cockpit window open, especially the Console tab, for a long period of time, there’s a unbounded memory growth bug.
1 Like
So are you saying that is the cause of Pi3 non-responsiveness? And Pi3 runs different OS than Pi4? Thank you for looking and assisting. (I leave Cockpit open on both Pi4 and aside from memory usage growing they are always responsive and fully operational) N/M I just looked at Cockpit and see both Pi3 and Pi4 are running same OS.
Well, I’m saying that based on your screenshot of the process cockpit-bridge process consuming 69.5% of available memory is a dead giveaway you’re running into that particular known issue. The growth is linear. Your Pi 3 only has 1Gb of RAM; how much does your Pi 4?
And, as I asked, if you close all cockpit browser windows, does it stop the crashing?
As I mentioned only latest 3 pics are for this issue of the Pi3 becoming non-responsive- those others may be relevant but were taken for the memory issue you see and a different thread I started here on the forums. I will leave the Pi3 w Cockpit closed and report back- I missed that suggestion. Thx.
No crashes on Pi3 with cockpit closed. Pi4 are 2GB and 4GB models and neither ever crash with cockpit opened indefinitely.
Yeah so that’s definitely the cockpit memory bug. We’re contemplating forcing the Pi Appliances to use debian backports to get a new version of Cockpit where that issue is fixed.
Thanks. Never heard of a backport- looked it up- nice to be able to update parts of the OS I guess by users creating backports.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.