Hi,
I noticed this after many freezes (due to bug 954181) in the messages:
[ 3.549075] systemd-journald[177]: File
/var/log/journal/4697cb8e07b94ed28925792b701e629f/system.journal corrupted
or uncleanly shut down, renaming and replacing.
But why is it running if i did not enable it nor have i changed the default
syslog?
# cat /etc/fedora-release
Fedora release 19 (Schrödinger’s Cat)
# uname -r
3.9.0-0.rc7.git3.1.fc19.x86_64
# systemctl list-units |grep -i journal
systemd-journald.service loaded active running Journal Service
systemd-journald.socket loaded active running Journal Socket
# systemctl list-units |grep -i syslog
rsyslog.service loaded active running System Logging Service
syslog.socket loaded active running Syslog Socket
# systemctl status systemd-journald.service
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Mon 2013-04-22 17:06:33 ART; 20min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 177 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
└─177 /usr/lib/systemd/systemd-journald
Apr 22 17:06:33 stark.espada systemd-journal[177]: Allowing runtime journal
files to grow to 399.3M.
Apr 22 17:06:33 stark.espada systemd-journal[177]: Journal started
Apr 22 17:06:34 stark.espada systemd-journal[177]: Allowing system journal
files to grow to 4.0G.
Apr 22 17:07:24 stark.espada systemd-journal[177]: Forwarding to syslog
missed 53 messages.
# systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Mon 2013-04-22 17:06:34 ART; 20min ago
Main PID: 333 (rsyslogd)
CGroup: name=systemd:/system/rsyslog.service
└─333 /sbin/rsyslogd -n
# ls -l /var/log/messages*
-rw-------. 1 root root 598516 Apr 22 17:21 /var/log/messages
-rw-------. 1 root root 1982160 Apr 13 15:56 /var/log/messages-20130413
-rw-------. 1 root root 550418 Apr 20 17:04 /var/log/messages-20130420
-rw-------. 1 root root 514731 Apr 21 13:09 /var/log/messages-20130421
# ls -l /var/log/journal/
total 8
drwxr-xr-x+ 2 root root 4096 Apr 22 17:06 4697cb8e07b94ed28925792b701e629f
# ls -l /var/log/journal/4697cb8e07b94ed28925792b701e629f/
total 76360
-rw-r-----+ 1 root systemd-journal 7462912 Apr 5 15:06
system@0004d9a0f39c9cf9-f6c68c6aa8300de3.journal~
-rw-r-----+ 1 root systemd-journal 9494528 Apr 5 17:53
system@0004d9a34756be53-519bcb0f6de7ed66.journal~
-rw-r-----+ 1 root systemd-journal 5353472 Apr 5 18:13
system@0004d9a38d8574e1-0ec56d6bae16b243.journal~
-rw-r-----+ 1 root systemd-journal 8417280 Apr 7 17:04
system@0004d9cad4c2a0ec-be79b785f140e32d.journal~
-rw-r-----+ 1 root systemd-journal 20258816 Apr 21 12:27
system@0004dae096de651e-cace31ff8c7f7724.journal~
-rw-r-----+ 1 root systemd-journal 6901760 Apr 21 15:56
system@0004dae381c7f9ac-122c42176d3ec2af.journal~
-rw-r-----+ 1 root systemd-journal 4919296 Apr 21 16:54
system@0004dae452a0f1bf-da4c74f3ea564679.journal~
-rw-r-----+ 1 root systemd-journal 6795264 Apr 22 17:06
system@0004daf89b05d07b-c306684d77ae2787.journal~
-rw-r-----+ 1 root systemd-journal 4751360 Apr 22 17:24 system.journal
-rw-r-x---+ 1 root systemd-journal 3743744 Apr 5 15:11 user-1000.journal
# ps aux|grep -i journald | grep -v grep
root 177 0.0 0.2 299340 17180 ? Ss 17:06 0:00
/usr/lib/systemd/systemd-journald
# ps aux|grep -i rsyslogd | grep -v grep
root 333 0.0 0.0 254700 1660 ? Ssl 17:06 0:00
/sbin/rsyslogd -n
Do i have both rsyslogd and journald running at the same time?
I re-checked my F17 Box and also both systemd-journald.service and
rsyslog.service are up. But
unlike F19a, there are no /var/log/journal directories nor any .journal
file.
On the F19a Host, when i encounter the freeze event:
/var/log/messages (rsyslogd) shows:
Apr 22 18:01:41 stark kernel: [ 3312.986034] kvm [1866]: vcpu0 unhandled
rdmsr: 0xc001100d
Apr 22 18:01:41 stark kernel: [ 3312.986067] kvm [1866]: vcpu0 unhandled
rdmsr: 0xc0010112
Apr 22 18:01:41 stark kernel: [ 3313.128231] kvm [1866]: vcpu0 unhandled
rdmsr: 0xc0010001
Apr 22 18:03:08 stark rsyslogd: [origin software="rsyslogd"
swVersion="7.2.6" x-pid="348" x-info="http://www.rsyslog.com";] start
journalctl -r (journald) shows:
Apr 22 18:03:03 stark.espada systemd-journal[68]: Allowing runtime journal
files to grow to 399.3M.
-- Reboot --
Apr 22 18:01:45 stark.espada setroubleshoot[1871]: writing database
(/var/lib/setroubleshoot/setroubleshoot_database.xml) mod
Apr 22 18:01:45 stark.espada setroubleshoot[1871]: KeyboardInterrupt in
RunFaultServer
Apr 22 18:01:45 stark.espada setroubleshoot[1871]: received signal=14
Apr 22 18:01:41 stark.espada kernel: kvm [1866]: vcpu0 unhandled rdmsr:
0xc0010001
Apr 22 18:01:41 stark.espada kernel: kvm [1866]: vcpu0 unhandled rdmsr:
0xc0010112
Apr 22 18:01:41 stark.espada kernel: kvm [1866]: vcpu0 unhandled rdmsr:
0xc001100d
The freeze does not leave anything logged (18:01:xx is the freeze). The
journald log has 4 more seconds of log, which are before the freeze.
The default system logger for F19 is rsyslogd or journald?
Thanks in advance.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
