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.
Bug 1279372 - plumouthd debug messages are not logged to file
Summary: plumouthd debug messages are not logged to file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: plymouth
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-09 10:12 UTC by Jan Stodola
Modified: 2017-12-18 20:36 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-18 20:36:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Stodola 2015-11-09 10:12:59 UTC
Description of problem:
plymouthd executed with the "--debug --debug-file=/tmp/plymouth_debug" options doesn't save debug messages to the specified file.

[root@localhost ~]# rpm -q plymouth
plymouth-0.8.9-0.24.20140113.el7.x86_64
[root@localhost ~]# plymouthd --debug --debug-file=/tmp/plymouth_debug
[main.c:2084]                        initialize_environment:initializing minimal work environment
[main.c:1889]                       get_kernel_command_line:opening /proc/cmdline
[main.c:1898]                       get_kernel_command_line:reading kernel command line
[main.c:1919]                       get_kernel_command_line:Kernel command line is: 'BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet LANG=en_US.UTF-8
'
[main.c:2103]                        initialize_environment:checking if '/dev/tty1' exists
[main.c:1933]                               check_verbosity:checking if tracing should be enabled
[main.c:2009]                               check_verbosity:tracing shouldn't be enabled!
[main.c:2027]                                 check_logging:checking if console messages should be redirected and logged
[main.c:2036]                                 check_logging:logging will be enabled!
[main.c:2117]                        initialize_environment:source built on Oct 26 2015
[root@localhost ~]# ls -l /tmp/plymouth_debug
ls: cannot access /tmp/plymouth_debug: No such file or directory
[root@localhost ~]#

Version-Release number of selected component (if applicable):
plymouth-0.8.9-0.24.20140113.el7

How reproducible:
always

Steps to Reproduce:
1. plymouthd --debug --debug-file=/tmp/plymouth_debug
2. less /tmp/plymouth_debug

Actual results:
/tmp/plymouth_debug doesn't exist

Expected results:
/tmp/plymouth_debug with debug messages exists

Comment 1 Ray Strode [halfline] 2015-11-09 14:27:41 UTC
since plymouth starts in the initrd normally, we don't save the file until plymouth quits.

you can force it to write the debug file as it runs by doing

plymouth.debug=stream:/tmp/plymouth_debug

or more usefully

plymouth.debug=stream:/dev/kmsg

and it will get interlaced with kernel messages and go to the journal.

Comment 2 Jan Stodola 2015-11-09 16:47:57 UTC
Thanks for the hint.
The log file is indeed written when I call
# /usr/bin/plymouth quit

It could be useful to mention this information in the man page.


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