Hi Zbyszek,
If you want more files attached to ABRT Bugzilla reports, please add them to systemd-coredump first :)
https://github.com/systemd/systemd/blob/master/src/coredump/coredump.c#L1074 (https://github.com/systemd/systemd/blob/master/src/coredump/coredump.c#L1074)
so ABRT folks can simply list them in their white-list:
https://github.com/abrt/abrt/blob/master/src/plugins/abrt-dump-journal-core. c#L35 (https://github.com/abrt/abrt/blob/master/src/plugins/abrt-dump-journal-core....)
Regards,
Jakub
PS: I forwarded your email to ABRT developers
---------- Původní e-mail ---------- Od: Zbigniew Jędrzejewski-Szmek zbyszek@in.waw.pl Komu: Development discussions related to Fedora <devel@lists.fedoraproject. org> Datum: 7. 4. 2019 11:14:37 Předmět: vanishing abrt logs "Hi,
I was looking at some abrt reports in the bugzilla [1,2,3], and I seems that
the reports contain much less information than in the past. In particular, the "var_log_messages" attachment is always just a few useless lines that a) seems to be cut down just to messages *from* the service, and has no messages *about* the service b) the messages are only from a short time period before the crash
When a service dies, systemd logs quite a bit of useful information [4] about the causes. We also have services like pcp, which log information about resource starvation [5].
This extra information would surely be helpful to diagnose abrt reports. Can we please make the reports contain useful logs again (at least full 'journalctl -u' for the service and all logs timed from around the crash) ?
More information about the machine, for example /proc/meminfo would be great too.
Zbyszek
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1660466 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1691889 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1697032n
[4] $ sudo systemd-run -p WatchdogSec=5 sleep 10 Running as run-re57f9e7da8234592bf74818522ad9644.service... $ journalctl --no-hostname -o short-precise -u run-re57f9e7da8234592bf 74818522ad9644.service -- Logs begin at Tue 2019-02-19 02:28:12 CET, end at Sun 2019-04-07 10:55:09 CEST. -- Apr 07 10:47:02.891163 systemd[1]: Started /usr/bin/sleep 100. Apr 07 10:47:08.071563 systemd[1]: run-re57f9e7da8234592bf74818522ad9644. service: Watchdog timeout (limit 5s)! Apr 07 10:47:08.072333 systemd[1]: run-re57f9e7da8234592bf74818522ad9644. service: Killing process 7704 (sleep) with signal SIGABRT. Apr 07 10:47:08.403477 systemd[1]: run-re57f9e7da8234592bf74818522ad9644. service: Main process exited, code=dumped, status=6/ABRT Apr 07 10:47:08.403608 systemd[1]: run-re57f9e7da8234592bf74818522ad9644. service: Failed with result 'watchdog'. Apr 07 10:47:08.403946 systemd[1]: run-re57f9e7da8234592bf74818522ad9644. service: Consumed 4ms CPU time.
[5] pcp-pmie[3000]: Severe demand for real memory 11.2pgsout/s@krowka _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists. fedoraproject.org "