Bug 678294 - /var/log/dracut.log is missing
Summary: /var/log/dracut.log is missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dracut
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Harald Hoyer
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 670159
TreeView+ depends on / blocked
 
Reported: 2011-02-17 13:40 UTC by Alexander Todorov
Modified: 2015-09-28 02:29 UTC (History)
3 users (show)

Fixed In Version: dracut-004-40.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 11:54:19 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0523 0 normal SHIPPED_LIVE dracut bug fix and enhancement update 2011-05-18 17:44:57 UTC

Description Alexander Todorov 2011-02-17 13:40:47 UTC
Description of problem:

# rpm -ql dracut | grep dracut.log
/var/log/dracut.log

# ls -l /var/log/dracut.log
ls: cannot access /var/log/dracut.log: No such file or directory

Version-Release number of selected component (if applicable):
dracut-004-38.el6.noarch

How reproducible:
Always


As a result dracut will not write its log to this file because it doesn't exist. If root does `touch /var/log/dracut.log' then dracut successfully writes to this file.

Also related to bug #676018.

Comment 1 Alexander Todorov 2011-02-17 14:12:31 UTC
While trying to test bug #676018. Harald instructed me to create $HOME/dracut.log before testing. 

dracut should automatically create its log files if they are not present:
/var/log/dracut.log and $HOME/dracut.log if invoked with -l.

Comment 3 Pavel Holica 2011-04-07 11:16:48 UTC
Reproduced on RHEL6.0 GA x86_64 Server.

Verified on RHEL6.1-20110330.2 x86_64 Server.
dracut-004-46.el6.noarch

Comment 6 errata-xmlrpc 2011-05-19 11:54:19 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0523.html


Note You need to log in before you can comment on or make changes to this bug.