As this server is used heavily used, rebooting is not that convenient. Is there a way to force crashdb.conf to be reloaded? I tried restarting apport & whoopsie services with systemctl but not sure if that worked.
There's a recent crash file for thunar that may or may not have been produced from the same issue. Though it oddly doesn't show up on my servers' error page, the url should be https://errors.ubuntu.com/oops/f9a43c4e-5076-11eb-8e16-fa163ee63de6 based on the contents of the .uploaded file. Unfortunately, I'm unable to check as I'm not a member of the appropriate group.
Let me know what you find and if a reboot is absolutely necessary to get the crash file uploaded securely.
As this server is used heavily used, rebooting is not that convenient. Is there a way to force crashdb.conf to be reloaded? I tried restarting apport & whoopsie services with systemctl but not sure if that worked.
There's a recent crash file for thunar that may or may not have been produced from the same issue. Though it oddly doesn't show up on my servers' error page, the url should be https:/ /errors. ubuntu. com/oops/ f9a43c4e- 5076-11eb- 8e16-fa163ee63d e6 based on the contents of the .uploaded file. Unfortunately, I'm unable to check as I'm not a member of the appropriate group.
Let me know what you find and if a reboot is absolutely necessary to get the crash file uploaded securely.
Thanks