Description of problem: /var/log/boot/log does not contain copy of boot screen messages. It only has something like Dec 2 12:05:04 localhost NET[2379]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Set system to boot runlevel 3 2. After boot, cat /var/log/boot.log Kernel command line: BOOT_IMAGE=cauldron_alpha1 root=LABEL=cauldron irqpoll nokmsboot init=/bin/systemd hpet=force vga=788 I would have expected something like this snippet: Started SYSV: start/stop fancontrol. Starting LSB: Kernel NFS server support... Starting LSB: Synchronizes system time using the Network Time Protocol (NTP)... Starting /etc/rc.local Compatibility... Started LSB: Kernel NFS server support. rc.local: privoxy restart [ OK ] Starting privoxy (via systemctl): Started LSB: Web proxy with advanced filtering capabilities. [ OK ] Started /etc/rc.local Compatibility. Starting Wait for Plymouth Boot Screen to Quit... Starting Terminate Plymouth Boot Screen... Nov 29 22:40:18 wb NET[3278]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
Blocks: (none) => 2120Assignee: bugsquad => dmorganec
Solution: Another clean install, apply updates https://bugs.mageia.org/show_bug.cgi?id=3577#c12 has a bit more explanation.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Problem is back. Created a VirtualBox guest, Steps to reproduce: 1. Clean install 2. During install, pick Automatic instead of static in network setup screen. 3. cat /var/log/boot.log 4. note no systemd boot output 5. Apply all updates 6. reboot 7. cat /var/log/boot.log 8. note no systemd boot output
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Care to try with a early alpha 2? https://wiki.mageia.org/mw-en/index.php?title=Mageia_2_alpha2
CC: (none) => davidwhodgins
(In reply to comment #3) > Care to try with a early alpha 2? > https://wiki.mageia.org/mw-en/index.php?title=Mageia_2_alpha2 A bit of research on that page suggests kernel.org would have alpha2. Do not see it there. Just did an update alpha1 this morning. shorewall will not run because of a missing version argument somewhere. :( Found out I no longer know iptable commands to open firewall to get net access. :-( Have rebooted more than 30 times, lost track of number of clean installs on hardware (2 64 bit systems) virtualbox (2 guests 32/64), did not know today is Monday. I think I'll take a break from testing. I have 70+ tv programs to watch in my mythtv database. I need a break. :)
Another clean install, updates applied, reboot. /var/log/boot.log contains data.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
clean install alpha3. /var/log/boot.log does not have systemd boot messages
Summary: 2_alpha1: /var/log/boot/log does not contain copy of boot screen messages. => 2_alpha3: /var/log/boot/log does not contain copy of boot screen messages.Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Summary: 2_alpha3: /var/log/boot/log does not contain copy of boot screen messages. => 2_alpha3: /var/log/boot.log does not contain copy of boot screen messages.
Guessing failure is caused by bootlogd not being executed or whatever replaced it in systemd. sysvinit-2.87-11.mga2.src.rpm contains /sbin/bootlogd
Source RPM: systemd-37-13.mga2.src.rpm => systemd-37-18.mga2.src.rpm
Temporary workaround is to set FQDN hostname in /etc/hostname. That will not be good for nodes with dynamic hostname allocation.
Source RPM: systemd-37-18.mga2.src.rpm => systemd-38-8.mga2.src.rpm
clean ftp network install. all reboots so far have a /var/log/boot.log with startup/failure messages.
clean install beta1 iso. urpme --auto-orphans install updates urpme --auto-orphans reboot cat /var/log/boot.log no messages except my dhcpd messages. :(
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Source RPM: systemd-38-8.mga2.src.rpm => systemd-43-1.mga2.src.rpm
what about this bug with systemd 44 ?
systemd-44-2.mga2.src.rpm does resolve the problem.