Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
(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.
(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
(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.
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