[Bug 826479] New: boot.log scrambled by error messages
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c0 Summary: boot.log scrambled by error messages Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: stephan.barth@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=545376) --> (http://bugzilla.novell.com/attachment.cgi?id=545376) Example boot log file Boot was failing with latest Factory because of wrong "root" device. I was able to boot with "root=/dev/sda2". However, an error message with a progress bar fills up /var/log/boot.log and makes it quite useless: [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Tell Plymouth To Write Out Runtime Data. [* ] A start job is running for dev-disk-by\x2did-ata\x2dSAMSUNG_HM321HI_S25PJ9FBA01170\x2dpart1.device^M[** ] A start job is running for dev-disk-by\x2did-ata\x2dSAMSUNG_HM321HI_S25PJ9FBA01170\x2dpart1.device^M etc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c1 FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |tittiatcoke@gmail.com |ovo.novell.com | --- Comment #1 from FeiXiang Zhang <fxzhang@suse.com> 2013-07-08 07:11:10 UTC --- please help to have a look at this. I am not sure whether it is right to assign it to you. Feel free to reassign it whenever necessary. thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tittiatcoke@gmail.com |bnc-team-screening@forge.pr | |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c2 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tittiatcoke@gmail.com --- Comment #2 from Raymond Wooninck <tittiatcoke@gmail.com> 2014-02-07 09:05:48 UTC --- This is not Plymouth. Grub will assign disks based on the UUID, which is shown above. If this is not wanted, then a number of changes have to be made including editing /etc/fstab, etc. Question is more why the "root" device was wrong according to the user. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de AssignedTo|systemd-maintainers@suse.de |kigurame@opensuse.org --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2014-02-12 09:08:54 UTC --- This *is* Plymouth: werner/plymouth> grep boot.log * plymouth.changes:- own %{_localstatedir}/log/boot.log plymouth.changes: and %{_localstatedir}/spool/plymouth/boot.log (as %ghost s) plymouth.spec:including a boot log viewing application. plymouth.spec:touch %{buildroot}%{_localstatedir}/log/boot.log plymouth.spec:touch %{buildroot}%{_localstatedir}/spool/plymouth/boot.log plymouth.spec:%ghost %{_localstatedir}/log/boot.log plymouth.spec:%ghost %{_localstatedir}/spool/plymouth/boot.log .. Simply remove the rotator by a filter as it has been done by blogd This is alos valid for SLES12. To compare this, see libconsole.c of blogd sources, function parselog() the part where the carriage return aka \r is removed before the log is written. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=826479 https://bugzilla.novell.com/show_bug.cgi?id=826479#c4 --- Comment #4 from Dr. Werner Fink <werner@suse.com> 2014-02-12 09:13:48 UTC --- Note that systemd writes out its messages for systems console that includes escape sequences including colo(u)ring as well as carriage return to be able to write out a rotator by overriding the same line several times. It is up on plymouth to remove those sequences and this can be done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com