<div dir="ltr">Hi Larry, I might start by configuring abrt to process these events by enabling exception handling in unpackaged software. According to the latest docs [1], this is done in /etc/abrt/abrt-action-save-package-data.conf by setting 'ProcessUnpackaged = yes'. Disclaimer: I'm not familiar with how abrt handles such events, what information can be saved, or even if this is safe to set system-wide. I would consult the docs or the source before doing this on a production system myself - this is a lmgtfy answer in which I did the search for you, sorry for the lack of authoritative info :) This isn't what you asked and may be overly pedantic (apologies if so), but I would personally not rely only on abrt to catch and report on failures of custom Python applications. Python has very good built-in exception handling capabilities. Custom exception classes are a good way to capture useful data like tracebacks (see traceback and cgitb modules). When combined with the logging module, one can easily relay such failures through syslog or another logging vehicle. Abrt has its place, and if the Python interpreter has died without executing exception handling then this paragraph is moot. A good set of examples are at [2]. Eli [1] <a href="http://abrt.readthedocs.org/en/latest/conf.html#abrt-specific-configuration">http://abrt.readthedocs.org/en/latest/conf.html#abrt-specific-configuration</a> [2] <a href="https://doughellmann.com/blog/2009/06/19/python-exception-handling-techniques/">https://doughellmann.com/blog/2009/06/19/python-exception-handling-techniques/</a> (From abrt docs)<div> """ ProcessUnpackaged = yes/no This directive tells ABRT whether to process crashes in executables that do not belong to any package. The default setting is no. """ </div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Apr 6, 2016 at 1:51 PM, Larry Martell <<a href="mailto:larry.martell@gmail.com" target="_blank">larry.martell@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have a python script that periodically terminates with no output - no errors, no exceptions, nothing. Looking in the logs I see this: python: detected unhandled Python exception in '/home/prod_user/python/make_workitem_list.py' abrt-server: Executable '/home/prod_user/python/make_workitem_list.py' doesn't belong to any package and ProcessUnpackaged is set to 'no' abrt-server: 'post-create' on '/var/spool/abrt/Python-<a href="tel:2016-04-06-08" value="+12016040608">2016-04-06-08</a>:12:25-26141' exited with 1 abrt-server: Deleting problem directory '/var/spool/abrt/Python-<a href="tel:2016-04-06-08" value="+12016040608">2016-04-06-08</a>:12:25-26141' I see what I think is just the default abrt files in /etc/libreport and events.d. What can I do get abrt to give me more info on this crash? _______________________________________________ rhelv6-list mailing list <a href="mailto:rhelv6-list@redhat.com">rhelv6-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/rhelv6-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rhelv6-list</a> </blockquote></div> </div></div>