Bug 880025

Summary: error message about "systemd.journald.forward_to_console=true"
Product: [Fedora] Fedora Reporter: Dave Young <ruyang>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: johannbg, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-201-2.fc18.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-16 02:57:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Young 2012-11-26 03:13:39 UTC
Description of problem:

I got below error message when I use systemd.journald.forward_to_console=true, but it indeed works for me, I need it to debug kdump 2nd kernel initrd:

[    1.925699] systemd[1]: Unknown kernel switch systemd.journald.forward_to_console=true. Ignoring.
[    1.937827] systemd[1]: Supported kernel switches:
[    1.945106] systemd[1]: systemd.unit=UNIT                        Default unit to start
[    1.952289] systemd[1]: rd.systemd.unit=UNIT                     Default unit to start when run in initrd
[    1.961361] systemd[1]: systemd.dump_core=0|1                    Dump core on crash
[    1.975002] systemd[1]: systemd.crash_shell=0|1                  Run shell on crash
[    1.981073] systemd[1]: systemd.crash_chvt=N                     Change to VT #N on crash
[    1.987351] systemd[1]: systemd.confirm_spawn=0|1                Confirm every process spawn
[    1.999249] systemd[1]: systemd.show_status=0|1                  Show status updates on the console during bootup
[    2.001181] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[    2.017553] systemd[1]: systemd.log_target=console|kmsg|journal|journal-or-kmsg|syslog|syslog-or-kmsg|null
[    2.028059] systemd[1]:                                          Log target
[    2.036683] systemd[1]: systemd.log_level=LEVEL                  Log level
[    2.042762] systemd[1]: systemd.log_color=0|1                    Highlight important log messages
[    2.049600] systemd[1]: systemd.log_location=0|1                 Include code location in log messages
[    2.059095] systemd[1]: systemd.default_standard_output=null|tty|syslog|syslog+console|kmsg|kmsg+console|journal|journal+console
[    2.077666] systemd[1]:                                          Set default log output for services
[    2.088100] systemd[1]: systemd.default_standard_error=null|tty|syslog|syslog+console|kmsg|kmsg+console|journal|journal+console
[    2.105100] systemd[1]:                                          Set default log error output for services
[    2.118057] systemd[1]: systemd.setenv=ASSIGNMENT                Set an environment variable for all spawned processes
[    2.194262] systemd[1]: systemd 188 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP; fedora)
[    2.210279] systemd[1]: Detected virtualization 'kvm'.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lennart Poettering 2013-03-07 17:41:27 UTC
Fixed in git.

Comment 2 Fedora Update System 2013-04-10 20:11:58 UTC
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1

Comment 3 Fedora Update System 2013-04-11 23:24:52 UTC
Package systemd-201-2.fc18.2:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-04-15 23:59:25 UTC
Package systemd-201-2.fc18.4:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.3
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-04-18 02:36:50 UTC
Package systemd-201-2.fc18.5:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-05-07 13:39:23 UTC
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6

Comment 7 Fedora Update System 2013-05-09 10:01:49 UTC
Package systemd-201-2.fc18.6:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-05-16 02:57:54 UTC
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.