Sure enough, it did send me an email alerting me about this problem. I used a free website monitoring service called StatusCake. Lo and behold, I saw this error: 'Error establishing a database connection.' My website had been down for 4 hours, luckily in the middle of the night. My conclusion is use this message to alert you that there may be a boot problem but immediately delete the /var/crash/ files and try to fix serious errors you find in /var/log/dmesg, as well as potentially syslog and Xorg.0.One morning, I went on-line to check my WordPress website. Obviously, this message is inspired by old crash files even if they are no longer relevant. This time the "System program problem detected" was not reported. I then deleted all of the /var/crash files and rebooted. No new syslog was produced and the new dmesg and Xorg.0 logs only showed minor warnings. To test whether the problem was in going to X, I deleted /var/log/dmesg, /var/log/syslog, and /var/log/Xorg.0.log and then rebooted the display manager using sudo systemctl restart display-manager. appeared, but dmesg showed a more benign warning about being unable to find a TPM device. Since I couldn't get any information from the crash files, I examined /var/log/dmesg and found two boot errors. I suspect that this is why "Report Problem" is unresponsive. In most cases this was just "Package", and did not reveal anything else. However, in all cases the program complained that something was missing. I installed apport and apport-retrace and applied apport-retrace to the crash files I found in /var/crash. I was getting this message on every boot. It has an example crash report and a method to retrace crashes. How to read and use crash reports? has some interesting answers. You can delete the service with sudo apt purge apport (and install it again with sudo apt install apport)Īnd there is also a desktop method (option "problem reporting": Editing it in reverse will enable it again. If you do not want to see crash reports you can disable it by doing sudo vim /etc/default/apport and changing enabled=1 to enabled=0. You can stop the service with sudo systemctl disable apport (and enable it again with sudo systemctl enable apport) Sudo rm /var/crash/* will delete old crashes and stop informing you about them until some package crashes again. You can pick any of these to remove the crash report up to actually removing the package (would be rather ironic if the error comes from apport itself): Generally crashes are off topic on AU as those are bugs and would need to be reported (through this service ) ). If you can not understand those crash reports most times you can google the error notice (there will always be one in there). Most times it is a core functionality though. If the package it is about is unneeded or benign you could also purge it. The ideal fix would be to check what is inside the reports, and try and find a fix for it. If you want really detailed reports on a crash install GDB: The GNU Project Debugger with sudo apt-get install gdb.ĭepends on what you call "get rid". The link has a detailed description and also has a PDF that describes the crash report data format. Ubuntu releases use this (optional) directory to dump crashes and the package that does that is called apport (and whoopsie). Linux but may be supported by other systems which may comply with the As of the date of this release of the standard, system crash dumps were not supported under var/crash : System crash dumps (optional) The directory you want is /var/crash/ and it will contain several files pointing you to the package it is about and what the crash is. See the crash report that is dumped on your disk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |