FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a machine running Fedora 19 which has been offline for several months. I need to do some work on it involving installing new software, so I put the machine online and ran YUM (using YUMEX) to apply updates.
After a while, Yumex froze. It claims to be "Running RPM Transaction", "Updating dracut-029-1.fc18.2.x86_64"
I can see that it has recently reported "cannot create regular file '/var/tmp/abrt/ccpp-2013-01-30-12:40:23-8123/count': No such file or directory" and a couple more similar messages. The most recent messages are hidden by the "Processing pending actions" dialog window.
What can I safely do with the system to recover it?
While I was not watching closely, the "transaction completed" and Yumex asked if I wanted to exit the Yum Extender. However, it won't take "No" for an answer. Neither will it take "Yes". So the system is still frozen, but in a different place.
Eventually, screensave kicked in and wouldn't wake up so I had no choice but to power off. On re-booting, the system had survived. So, not so much 'solved' as 'gone away'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.