[rhelv6-list] abrt

Larry Martell larry.martell at gmail.com
Wed Apr 6 18:45:16 UTC 2016


On Wed, Apr 6, 2016 at 2:40 PM, Eli Heady <eli.heady at gmail.com> wrote:
> 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].

Thanks. I do have exception handlers and I am capturing stdout and
stderr, and there's nothing.

>
> Eli
>
> [1]
> http://abrt.readthedocs.org/en/latest/conf.html#abrt-specific-configuration
> [2]
> https://doughellmann.com/blog/2009/06/19/python-exception-handling-techniques/
>
>
> (From abrt docs)
>
> """
>
> 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.
>
> """
>
>
>
> On Wed, Apr 6, 2016 at 1:51 PM, Larry Martell <larry.martell at gmail.com>
> wrote:
>>
>> 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-2016-04-06-08:12:25-26141' exited with 1
>> abrt-server: Deleting problem directory
>> '/var/spool/abrt/Python-2016-04-06-08: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
>> rhelv6-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rhelv6-list
>
>




More information about the rhelv6-list mailing list