Hide Forgot
Description of problem: Found following msg in /var/log/messages. It's from abrtd after processing crash: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory Dunno whether is it harmful or anything. Version-Release number of selected component (if applicable): abrt-2.0.4-1.el6.x86_64 libreport-2.0.5-1.el6.x86_64 btparser-0.13-1.el6.x86_64
Seems like compatibility problem with old abrt dumps, but if I remember it correctly even the previous abrt had uuid. Can you test it with old abrt?
It started on July 22 when I updated to abrt v2. abrt v1 is OK. [newman@dhcp-25-35 ~]$ sudo grep "abrtd.* or directory" /var/log/messages* /var/log/messages:Jul 27 16:41:42 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 27 17:13:21 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 27 17:30:22 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 27 17:37:06 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-2011-07-27-17:37:04-3736/uuid': No such file or directory /var/log/messages:Jul 27 17:37:06 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 28 12:11:38 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 28 13:17:08 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages:Jul 28 14:14:20 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-2011-07-28-14:13:30-10308/uuid': No such file or directory /var/log/messages:Jul 28 14:14:44 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-2011-07-28-14:13:30-10308/uuid': No such file or directory /var/log/messages-20110725:Jul 22 11:38:07 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages-20110725:Jul 22 11:42:06 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory /var/log/messages-20110725:Jul 22 11:43:24 dhcp-25-35 abrtd: Can't open file '/var/spool/abrt/ccpp-1310991931-5029/uuid': No such file or directory I guess /var/spool/abrt/ccpp-1310991931-5029/ is from abrt v1 and /var/spool/abrt/ccpp-2011-07-28-14:13:30-10308/ from abrt v2 so it happens for both old & new crash dirs.
(In reply to comment #2) > Seems like compatibility problem with old abrt dumps, but if I remember it > correctly even the previous abrt had uuid. Can you test it with old abrt? [root@localhost ~]# ll /var/spool/abrt/ccpp-1312296061-1297/uuid /var/spool/abrt/ccpp-1312296191-1440/uuid ls: cannot access /var/spool/abrt/ccpp-1312296061-1297/uuid: No such file or directory ls: cannot access /var/spool/abrt/ccpp-1312296191-1440/uuid: No such file or directory First was created by root, second by user. Reporting changed that by creating some global_uuid.
Can you please re-check it after installing abrt-2.0.4-2 (and later) it has posttrans script to convert the abrt1 db into abrt2 files and creates even uuid if it's missing.
btw, the script lives in /usr/librexec/abrt1-to-abrt2 in case you want to test it manually
What if abrt-db is not in /var/spool/abrt/ (DBPath option from plugins/SQLite3.conf)? $ sudo /usr/libexec/abrt1-to-abrt2 Traceback (most recent call last): File "/usr/libexec/abrt1-to-abrt2", line 46, in <module> crashes = db.execute("SELECT * FROM abrt_v4") sqlite3.OperationalError: no such table: abrt_v4
(In reply to comment #7) > What if abrt-db is not in /var/spool/abrt/ (DBPath option from > plugins/SQLite3.conf)? > > $ sudo /usr/libexec/abrt1-to-abrt2 > Traceback (most recent call last): > File "/usr/libexec/abrt1-to-abrt2", line 46, in <module> > crashes = db.execute("SELECT * FROM abrt_v4") > sqlite3.OperationalError: no such table: abrt_v4 you're experiencing the 730696, can you please try it with the patch? From which abrt version your abrt-db comes from?
That fixes the issue of empty or missing DB, but what about when the DB is placed somewhere else via DBPath option from ABRTv1? It won't do the conversion since it can't find the DB file where it expects it by default.
DBPath is now parsed from SQLite3.conf.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1598.html