Server IP : 85.193.89.191 / Your IP : 18.220.187.80 Web Server : Apache System : Linux 956367-cx40159.tmweb.ru 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64 User : bitrix ( 600) PHP Version : 8.1.27 Disable Function : NONE MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /proc/984/root/etc/libreport/events.d/ |
Upload File : |
# Analyze EVENT=post-create analyzer=Kerneloops # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266 # 'dmesg' file is required by check-oops-for-hw-error dmesg >>dmesg # Do not fail the event (->do not delete problem dir) # if check-oops-for-hw-error exits nonzero: { abrt-action-check-oops-for-hw-error || true } && { # run abrt-action-analyze-oops only if check-hw-error didn't create the # required files if test ! -f uuid -a ! -f duphash; then abrt-action-analyze-oops || exit 1 fi } && abrt-action-save-kernel-data # If you want behavior similar to one provided by kerneloops daemon # distributed by kerneloops.org - that is, if you want # oopses to be reported automatically and immediately without # user interaction, uncomment this line: #EVENT=post-create analyzer=Kerneloops reporter-kerneloops # Report #EVENT=report_Kerneloops analyzer=Kerneloops reporter-kerneloops EVENT=report_Bugzilla analyzer=Kerneloops reporter-bugzilla -b \ -F /etc/libreport/plugins/bugzilla_format_kernel.conf # Send micro report EVENT=report_uReport analyzer=Kerneloops /usr/libexec/abrt-action-ureport # Update ABRT database after successful report to bugzilla EVENT=post_report analyzer=Kerneloops reporter-ureport -A -B exit 0 # Automatic/simple GUI-based kernel oopses reporting will do this: EVENT=report-gui analyzer=Kerneloops report-gtk -- "$DUMP_DIR" EVENT=report-cli analyzer=Kerneloops report-cli -- "$DUMP_DIR"