-
-
Notifications
You must be signed in to change notification settings - Fork 3
Description
I am running Ubuntu Server 24.04 on a 16GB Raspberry Pi, LEMP server. I am experience some very drastic bugs/issues with this plugin, that crash the entire system, forcing me to unplug and plug the server back in just get it working again.
After changing some plugins configurations, and then using NPP to purge and preload that cache, my entire server starts crashing, nginx becomes unresponsive, ssh access becomes unresponsive and prevents me from logging in from a brand new ssh shell, tons of random BUG messages show on my Pi’s external HDMI Screen (the one connected directly to my pi, but not logged into my pi locally), and essentially, the entire system becomes totally unresponsive. The major problem with this, is that the only way to get it working again is to unplug the Pi. SSH commands become unresponsive. Because of this, I cannot find any crash logs after rebooting. I believe the are prevented from being written to disk, because the BUG crashes the logging system or journalctl itself, preventing it from logging.
Furthermore, I admitadly am a novice at locating/finding/reading error and crash logs. So there is a chance I’m not even logging properly. Since I can’t find the logs, the only thing I can do is take pictures of the Pi’s LCD screen while it crashes, and hope something of importance surfaces.
I am not sure where to start with this SEVERE BUG, but I noticed one thing on my Pi’s LCD Screen that appears every time I start changing the settings on NPP. It is a bug log that reads this:
[ 1063.329924] BUG: scheduling while atomic: grep/18650/0x00000002
[ 1063.333010] BUG: scheduling while atomic: grep/18650/0x00000000
I have no idea what it means. The other logs from the Main LCD screen during this crash are posted in the attached pictures. Here are the imgur pictures of some logs from the main raspberry pi LCD screen that is NOT logged into my user account.
How can I properly find the logs that are crashing the entire server during the use of this plugin, and how can I start debugging and fixing it? Please help locate the proper logs, debug, and solve this!
After you help me actually find the logs, could you alse help me devise a way to push all logs or copy all logs from the Raspberry Pi to an external USB stick? This would give me the ability to see the logs that the server writes while and after it's crashing. Because after the server crashes, thats it. The server no longer works, and I have to revert to a complete system backup flashing a DD of the server to the servers Hard disk.
Please help soon, because in this condition, I cannot even back up the server or use emails on it, because anything I do, will eventually have to be reverted to the working image of the server that hasn't yet triggered the bug, thus losing all of my emails that I sent/recieved after reinitializing the working image. Basically, I cannot use this server for my emails until this bug is fixed, because the server is much too volatile to trust it with my emails right now.
Please help! I


