Hey..
Testing some code (python).
Created a simple test cron to run the app. The app runs from the cmdline as the user, so in the cmd world, env vars, user privs/etc.. are good.
However, from the cron process, I get the following. The logs -- /var/log/messages indicate the abrtd process is deleting the tmp dir.. so I can't see what it's complaining about..
Any thoughts on how to resolve this..
Jul 14 08:45:09 crawl1 abrt: detected unhandled Python exception in '/crawl_tmp/jcccParse_cloud_test.py' Jul 14 08:45:09 crawl1 abrtd: Directory 'pyhook-2016-07-14-08:45:09-14939' creation detected Jul 14 08:45:09 crawl1 abrt-server[14944]: Saved Python crash dump of pid 14939 to /var/spool/abrt/pyhook-2016-07-14-08:45:09-14939 Jul 14 08:45:09 crawl1 abrtd: Executable '/crawl_tmp/jcccParse_cloud_test.py' doesn't belong to any package and ProcessUnpackaged is set to 'no' Jul 14 08:45:09 crawl1 abrtd: 'post-create' on '/var/spool/abrt/pyhook-2016-07-14-08:45:09-14939' exited with 1 Jul 14 08:45:09 crawl1 abrtd: Deleting problem directory '/var/spool/abrt/pyhook-2016-07-14-08:45:09-14939'
Thanks...
On 07/14/2016 08:55 AM, bruce wrote:
Jul 14 08:45:09 crawl1 abrt: detected unhandled Python exception in '/crawl_tmp/jcccParse_cloud_test.py' Jul 14 08:45:09 crawl1 abrtd: Directory 'pyhook-2016-07-14-08:45:09-14939' creation detected Jul 14 08:45:09 crawl1 abrt-server[14944]: Saved Python crash dump of pid 14939 to /var/spool/abrt/pyhook-2016-07-14-08:45:09-14939 Jul 14 08:45:09 crawl1 abrtd: Executable '/crawl_tmp/jcccParse_cloud_test.py' doesn't belong to any package and ProcessUnpackaged is set to 'no' Jul 14 08:45:09 crawl1 abrtd: 'post-create' on '/var/spool/abrt/pyhook-2016-07-14-08:45:09-14939' exited with 1 Jul 14 08:45:09 crawl1 abrtd: Deleting problem directory '/var/spool/abrt/pyhook-2016-07-14-08:45:09-14939'
Your python script is running into an exception for some reason, but abrt doesn't know about your application so clears the data. Try running it with stdout and stderr redirected to a file somewhere. Then you should be able to see what the exception is. You could also try setting ProcessUnpackaged to yes. On my systems, in /etc/abrt/abrt-action-save-package-data.conf, that setting it turned on. Do you have that? Maybe it needs to be set in /etc/abrt/abrt.conf as well.