Created attachment 943366 [details] /var/log/messages Description of problem: This server takes an extremely long time to boot. I have attached /var/log/messages. Maybe someone has a clue what is causing this? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It seems that abrtd is going crazy with Oct 2 08:49:52 nbecker7 abrtd: Can't open file '/var/tmp/abrt/pyhook-2013-01-30-19:34:06-6083/type': No such file or directory Oct 2 08:49:53 nbecker7 abrtd: Unlocked '/var/tmp/abrt/ccpp-2013-02-04-07:11:56-2436/.lock' (no or corrupted 'type' file) all over the place. You're also getting a few file related problems as well. That might indicate a HDD/filesystem problem.
Something has deleted files from /var/tmp/abrt/directories and left that directories empty. If you don't mind losing some crash data, you can safely remove /var/tmp/abrt (abrt will recreate it empty). Please, after cleaning up /var/tmp/abrt try to reboot and report the results here.
rm /var/tmp/abrt now boot is much better A different issue: I also had previously rm /var/log/journal/*/*. This is the 2nd system of mine where on boot, rsyslogd went nuts, I suppose trying to process all the stuff in journal files. The journal files do not exactly slow boot, but cause high load for potentially minutes each time the system is booted. I think something should be done to prevent accumulation of junk there from causing slow rot of linux systems.
(In reply to Neal Becker from comment #3) > I think something should be done to prevent accumulation of junk there from > causing slow rot of linux systems. rsyslog should (and does, afaik) just read new messages from the journal. The issue is that sometimes journal access is just slow, especially on rotational media.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.