On 18/08/2019 20.24, James Knott wrote:
On 2019-08-18 02:22 PM, Adam Majer wrote:
I'm sorry, but this is well beyond anything I'm familiar with. Just make sure that systemd-coredump is installed.
It's installed.
It is normally installed, but actually dumping core is disabled. "Dump core" refers to an automatic procedure that copies all the memory used by a program to a file, so that developers can study that copy after the crash. Only once I have seen it used. The file can be huge, and bugzilla will not take it. Another useful thing is a backtrace, which needs the -debug rpms be installed of the application that crashes and all the libraries it uses. I'm not sure if this requirement is needed for coredumps. Run this command as root first: Telcontar:~ # coredumpctl No coredumps found. Telcontar:~ # If you get that result, forget it, your crashes do not produce them. If you get something like this (different names): TIME PID UID GID SIG COREFILE EXE ... Fri 2019-08-02 11:04:59 CEST 4205 1000 100 11 none /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Sat 2019-08-10 10:52:04 CEST 925 1000 100 11 missing /usr/lib64/kodi/kodi-x11 Thu 2019-08-15 18:09:16 CEST 6165 1000 100 11 none Kodi_MovistarTV Fri 2019-08-16 01:18:55 CEST 9135 1000 100 11 present /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr we can continue. For example, I can use: coredumpctl info 9143 which gives information about that process crash: ... Thu 2019-08-15 18:09:16 CEST 6165 1000 100 11 none Kodi_MovistarTV Fri 2019-08-16 01:18:55 CEST 9135 1000 100 11 present /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Isengard:~ # coredumpctl info 9135 PID: 9135 (Kodi_MovistarTV) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Fri 2019-08-16 01:18:55 CEST (3 days ago) Command Line: ./Kodi_MovistarTV_Server.pvr -d:/home/cer/Fusion Executable: /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (cer) Boot ID: a7c4b7e16b264f379b931544ca66c0ee Machine ID: af5da4da5956dc08183725bc583a0cd5 Hostname: Isengard Storage: /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000 Message: Process 9135 (Kodi_MovistarTV) of user 1000 dumped core. Isengard:~ # The next step would be this: Isengard:~ # coredumpctl dump 9135 --output somefile PID: 9135 (Kodi_MovistarTV) UID: 1000 (cer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Fri 2019-08-16 01:18:55 CEST (3 days ago) Command Line: ./Kodi_MovistarTV_Server.pvr -d:/home/cer/Fusion Executable: /home/cer/MovistarTV.Server.2.0.21-stab-leia/Kodi_MovistarTV_Server.pvr Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (cer) Boot ID: a7c4b7e16b264f379b931544ca66c0ee Machine ID: af5da4da5956dc08183725bc583a0cd5 Hostname: Isengard Storage: /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000 Message: Process 9135 (Kodi_MovistarTV) of user 1000 dumped core. Failed to decompress /var/lib/systemd/coredump/core.Kodi_MovistarTV.1000.a7c4b7e16b264f379b931544ca66c0ee.9135.1565911135000000: Protocol not supported Isengard:~ # Does not work this time, but it tells us where they are stored: /var/lib/systemd/coredump/ So, go on, do those steps and we'll see. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)