Description of problem: /var/log/messages missing dmesg, crond, kernel,... log infomation Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Clean install of 2 Alpha3 2. apply all updates and reboot 3. cat /var/log/messages 4. dmesg Note none of the dmesg contents in /var/log/messages 5. grep finished /var/log/messages Note no systemd[1]: Startup finished in 2s 244ms 358us (kernel) + 18s 141ms 507us (initrd) + 24s 1ms 237us (userspace) = 44s 387ms 102us. entry wait for 1 minute past hour 5. grep crond /var/log/messages Note no (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly) entry
Hi, thanks for reporting this bug. IIRC it's lore a rsyslog bug ? (the deamon that write in /var/log/message ?
CC: (none) => dmorganecBlocks: (none) => 2120Source RPM: systemd-38-3.mga2.src.rpm => rsyslog
(In reply to comment #1) > Hi, thanks for reporting this bug. > > IIRC it's lore a rsyslog bug ? (the deamon that write in /var/log/message ? I can not argue about it since I have not delved into source code, but my money would be on the application which merged the logs/dmesg just after systemd finished with start up. /var/log/messages does have kernel, crond, ifplugd, udevadm, ... messages after the point where I should have seen systemd[1]: Startup finished in 2s 239ms 194us (kernel) + ....
Yes it's rsyslog then :) so it's ok
Summary: 2_a3: /var/log/messages missing dmesg, crond log systemd finished entries => /var/log/messages missing dmesg, crond log systemd finished entries (rsyslog)
can you test with an updated cauldron ? ( systemd 39 )
(In reply to comment #4) > can you test with an updated cauldron ? ( systemd 39 ) Yep, still broke. Last login: Thu Jan 26 17:07:20 2012 from wb.home.test [root@wb2 ~]# dmesg > dmesg.log [root@wb2 ~]# grep -i dmi: dmesg.log DMI: HP Pavilion 061 ER888AA-ABA A1267C/AMETHYST-M, BIOS 3.48 03/24/2006 [root@wb2 ~]# grep -i dmi: /var/log/messages [root@wb2 ~]# get_src_rpm systemctl Install rpm: systemd-units-39-3.mga2 Source rpm: systemd-39-3.mga2.src.rpm [root@wb2 ~]# get_src_rpm rsyslogd Install rpm: rsyslog-5.8.6-1.mga2 Source rpm: rsyslog-5.8.6-1.mga2.src.rpm get_src_rpm is my script to get rpm info based on argument 1.
(In reply to comment #5) > (In reply to comment #4) > > can you test with an updated cauldron ? ( systemd 39 ) > > Yep, still broke. kernel logging is somewhat better. snipped out date, time, node [root@wb2 ~]# grep vbox /var/log/kernel/* /var/log/kernel/info.log:kernel: vboxdrv: Found 1 processor cores. /var/log/kernel/info.log:kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. /var/log/kernel/info.log:kernel: vboxdrv: Successfully loaded version 4.1.8 (interface 0x00190000). /var/log/kernel/info.log:kernel: vboxpci: IOMMU not found (not registered) [root@wb2 ~]# grep vbox /var/log/messages kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. kernel: vboxpci: IOMMU not found (not registered) vboxdrv[905]: Starting VirtualBox kernel modules [ OK ]
Do you reckon we should have dmesg output in /var/log/messages? Or is it better to have it in /var/log/dmesg as it is now? Should be easy enough to sort out (not really looked but it's just gonna be fiddling with log stuff) either way.
CC: (none) => mageia
(In reply to comment #7) > Do you reckon we should have dmesg output in /var/log/messages? It has been in the past. One stop place for looking for start up problems is nice. Of course the only constant in Linux is change. > Or is it better to have it in /var/log/dmesg as it is now? I run a dmesg > /var/log/dmesg.log in rc.local and there are about 12 lines missing in /var/log/dmesg from things like vboxdvr, r8169 setup for my static etho link and a few netlink leftover bytes messages. Upon boot I noticed not all terminal output is not in a log. > Should be easy enough to sort out (not really looked but it's just gonna be > fiddling with log stuff) either way. Which brings up having to also look in /var/log/boot.log to see what else maybe broke. :( Not a problem for me since I have created a script to search all three. While you are looking into logging: I created a new_boot_logs script to copy /dev/null into all logs and reboot, and noticed a udevd entry in boot.log not in /var/log/messages. Looking at the the first line of boot.log I find udevd[166]: could not find module by name='tulip' Followed by Welcome to Mageia 2 but looking in my special /var/log/dmesg.log there is tulip: Linux Tulip driver version 1.1.15 (Feb 27, 2007) tulip0: MII transceiver #1 config 3100 status 7829 advertising 01e1 and looking in /var/log/messages ifplugd(eth0)[1202]: Using interface eth0/00:A0:CC:21:B8:91 with driver <tulip> (version: 1.1.15) Until this bug report is resolved I had not bothered opening the mis-logged udevd line, especially since I have no other information.
OK, this should be fixed in latest rsyslog + sysvinit-legacy + systemd. Still need to sort out listening from journal directly however (need to test that more).
Status: NEW => RESOLVEDResolution: (none) => FIXED
I just did a clean install of Mageia 3 64bit and there is no /var/log/messages file. There is also no /var/log/kernel. Aren't these supposed to exist by default? If so, I am thinking this issue is not fixed...
CC: (none) => crxssi
(In reply to M D from comment #10) > I just did a clean install of Mageia 3 64bit and there is no > /var/log/messages file. There is also no /var/log/kernel. Aren't these > supposed to exist by default? If so, I am thinking this issue is not > fixed... I manually "urpmi rlogind" and after rebooting both files now exist. I really think rlogind should be installed by default since it appears that otherwise the logging is going nowhere.
(In reply to M D from comment #11) > (In reply to M D from comment #10) > > I just did a clean install of Mageia 3 64bit and there is no > > /var/log/messages file. There is also no /var/log/kernel. Aren't these > > supposed to exist by default? If so, I am thinking this issue is not > > fixed... > > I manually "urpmi rlogind" and after rebooting both files now exist. I > really think rlogind should be installed by default since it appears that > otherwise the logging is going nowhere. Sorry, I meant "rsyslog" (has been a long day for me)
(In reply to M D from comment #11) > (In reply to M D from comment #10) > > I just did a clean install of Mageia 3 64bit and there is no > > /var/log/messages file. There is also no /var/log/kernel. Aren't these > > supposed to exist by default? If so, I am thinking this issue is not > > fixed... > > I manually "urpmi rlogind" and after rebooting both files now exist. I > really think rlogind should be installed by default since it appears that > otherwise the logging is going nowhere. Nope. journald is default logger as of Mageia 3. To see the logs, use journalctl command, for example "journalctl -b" to see all logs since last boot, and so on... see man journalctl for how to use. rsyslog is still provided as an option for those that want old style logging, but it wont be installed by default.
CC: (none) => tmb