Red Hat Bugzilla – 1311100 – [abrt] abrt-addon-vmcore: abrt-harvest-vmcore:104:write_to_file:IOError: [Errno 2] No such file or directory: '/var/tmp/abrt/vmcore-127.0.0.1-2013.09.07-13:42:25.new/uuid'
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.
[abrt] abrt-addon-vmcore: abrt-harvest-vmcore:104:write_to_file:IOError: [Errno 2] No such file or directory: '/var/tmp/abrt/vmcore-127.0.0.1-2013.09.07-13:42:25.new/uuid'
+++ This bug was initially created as a clone of Bug #1077241 +++
Version-Release number of selected component:
abrt-addon-vmcore-2.1.12-2.fc20
Additional info:
reporter: libreport-2.1.12
cmdline: /usr/bin/python /usr/sbin/abrt-harvest-vmcore
executable: /usr/sbin/abrt-harvest-vmcore
kernel: 3.13.3-200.fc20.x86_64
runlevel: N 5
type: Python
uid: 0
Truncated backtrace:
abrt-harvest-vmcore:104:write_to_file:IOError: [Errno 2] No such file or directory: '/var/tmp/abrt/vmcore-127.0.0.1-2013.09.07-13:42:25.new/uuid'
Traceback (most recent call last):
File "/usr/sbin/abrt-harvest-vmcore", line 290, in <module>
harvest_vmcore()
File "/usr/sbin/abrt-harvest-vmcore", line 276, in harvest_vmcore
create_abrtd_info(destdirnew)
File "/usr/sbin/abrt-harvest-vmcore", line 164, in create_abrtd_info
write_to_file(os.path.join(dest, 'uuid'), hashobj.hexdigest())
File "/usr/sbin/abrt-harvest-vmcore", line 104, in write_to_file
with open(path, 'w') as wfile:
IOError: [Errno 2] No such file or directory: '/var/tmp/abrt/vmcore-127.0.0.1-2013.09.07-13:42:25.new/uuid'
Local variables in innermost frame:
content: '9e3b539426b2a0bc19e54f67ec033240d75a4eee'
path: '/var/tmp/abrt/vmcore-127.0.0.1-2013.09.07-13:42:25.new/uuid'
--- Additional comment from Milan Bouchet-Valat on 2014-03-17 15:56:10 CET ---
--- Additional comment from Milan Bouchet-Valat on 2014-03-17 15:56:13 CET ---
--- Additional comment from Milan Bouchet-Valat on 2014-08-10 19:42:23 CEST ---
Seen once again with up-to-date F20. This is annoying since I cannot report kernel crashes using abrt-vmcore.
--- Additional comment from Jakub Filak on 2014-11-27 12:52:37 CET ---
Thank you for the report! I opened a pull request for this bug report:
https://github.com/abrt/abrt/pull/883
--- Additional comment from Milan Bouchet-Valat on 2014-11-27 14:09:41 CET ---
Thanks! But does that fix the problem, or just the handling of the error, i.e. does that mean that reporting kernel crashed will work?
--- Additional comment from Jakub Filak on 2014-11-27 15:05:38 CET ---
(In reply to Milan Bouchet-Valat from comment #5)
> Thanks! But does that fix the problem, or just the handling of the error,
> i.e. does that mean that reporting kernel crashed will work?
Yes, the patch only makes sure that the service will remain working if something removed the destination problem directory (I can't imagine how is that possible, perhaps something remounted /var or a temporary data cleaner did that). In such a case, the service will skip the currently processed vmcore and will continue with the next one.
I verified that the processing of vmcores works as expected under normal circumstances.
--- Additional comment from Milan Bouchet-Valat on 2014-11-27 15:26:15 CET ---
OK, I'll see whether harvesting vmcores now works on F21.
--- Additional comment from Fedora Update System on 2015-02-16 14:56:04 CET ---
abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20
--- Additional comment from Fedora Update System on 2015-02-17 09:10:10 CET ---
Package abrt-2.2.2-2.fc20, libreport-2.2.3-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.2.2-2.fc20 libreport-2.2.3-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-2191/abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2015-04-28 14:59:22 CEST ---
abrt-2.2.2-2.fc20, libreport-2.2.3-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
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.
https://rhn.redhat.com/errata/RHBA-2016-2307.html