RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1022160 - Can't open file '/var/spool/abrt/oops-2013-10-22-11:36:18-767-1/uid': No such file or directory
Summary: Can't open file '/var/spool/abrt/oops-2013-10-22-11:36:18-767-1/uid': No such...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.4
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jakub Filak
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 1056252
TreeView+ depends on / blocked
 
Reported: 2013-10-22 15:52 UTC by Lukáš Zachar
Modified: 2018-12-09 17:14 UTC (History)
6 users (show)

Fixed In Version: abrt-2.0.8-22.el6
Doc Type: Bug Fix
Doc Text:
no docs needed
Clone Of:
Environment:
Last Closed: 2014-10-14 08:05:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
A patch fixing this issue (877 bytes, patch)
2014-06-18 08:40 UTC, Jakub Filak 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1572 0 normal SHIPPED_LIVE abrt bug fix and enhancement update 2014-10-14 01:27:32 UTC

Description Lukáš Zachar 2013-10-22 15:52:54 UTC 
Description of problem:

When kerneloops is processed, following error is always found in /var/log/messages.
abrtd: Can't open file '/var/spool/abrt/oops-2013-10-22-11:20:51-5231-1/uid': No such file or directory

Version-Release number of selected component (if applicable):
abrt-2.0.8-16.el6_4.1.x86_64
abrt-addon-kerneloops-2.0.8-16.el6_4.1.x86_64


How reproducible:
always

Steps to Reproduce:
1. create kernel oops, e.g. by will_oops or writing to /var/log/messages
2. check /var/log/messages
3.

Actual results:
Oct 22 11:20:51 dell-pem610-01 abrtd: Directory 'oops-2013-10-22-11:20:51-5231-1' creation detected
Oct 22 11:20:51 dell-pem610-01 abrt-dump-oops: Reported 1 kernel oopses to Abrt
Oct 22 11:20:51 dell-pem610-01 abrtd: Can't open file '/var/spool/abrt/oops-2013-10-22-11:20:51-5231-1/uid': No such file or directory


Expected results:
No error from abrtd

Additional info:
Comment 4 hsudoh 2014-03-14 04:09:22 UTC 
I encounter the same problem in RHEL6.2 x64 system.
Is this a bug ?
If so, could you provide the fix plan ??
Comment 5 hsudoh 2014-03-14 05:01:37 UTC 
Does this message appear when Network problem occurs ??
Comment 6 Jakub Filak 2014-03-14 08:08:23 UTC 
(In reply to hsudoh from comment #4)
> I encounter the same problem in RHEL6.2 x64 system.
> Is this a bug ?
> If so, could you provide the fix plan ??

This is not a bug. It is just an useless and disturbing debug message. Sorry for frightening you.
Comment 7 Jakub Filak 2014-03-14 08:18:05 UTC 
(In reply to hsudoh from comment #5)
> Does this message appear when Network problem occurs ??

This message appears always when you experience a kernel oops. The kernel oops which produced the message could break Kernel's Network features. So yes, it might be connected to Network problems but as a consequence.

You should see the detected kernel oopses by issuing the following command:

$ abrt-cli list
Comment 8 hsudoh 2014-03-14 10:16:44 UTC 
(In reply to Jakub Filak from comment #7)
> (In reply to hsudoh from comment #5)
> > Does this message appear when Network problem occurs ??
> 
> This message appears always when you experience a kernel oops. The kernel
> oops which produced the message could break Kernel's Network features. So
> yes, it might be connected to Network problems but as a consequence.
> 
> You should see the detected kernel oopses by issuing the following command:
> 
> $ abrt-cli list

Thank you for your information.
This message appeared when our customer was configuring 10G network.
I will investigate customer's network configuration.
Comment 9 Jakub Filak 2014-06-18 08:40:42 UTC 
Created attachment 909879 [details]
A patch fixing this issue
Comment 12 errata-xmlrpc 2014-10-14 08:05:33 UTC 
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-2014-1572.html
Note You need to log in before you can comment on or make changes to this bug.