On Mon, 2011-05-16 at 11:12 -0500, Steven Stern wrote: > After a crash today, I decided to look at /var/log/messages, but it as > empty: > > -rw-------. 1 root root 0 May 15 03:15 messages > -rw-------. 1 root root 2486698 Apr 24 03:03 messages-20110424 > -rw-------. 1 root root 15123560 May 1 03:50 messages-20110501 > -rw-------. 1 root root 792295 May 8 03:31 messages-20110508 > -rw-------. 1 root root 855351 May 14 16:07 messages-20110515 > > I restarted rsyslog and it's now chock full of stuff: > > service rsyslog status > rsyslog.service - System Logging Service > Loaded: loaded (/lib/systemd/system/rsyslog.service) > Active: inactive (dead) > CGroup: name=systemd:/system/rsyslog.service > > Does this indicate it's not enabled on boot? > > [root@sds-desk log]# service rsyslog restart > Restarting rsyslog (via systemctl): [ OK ] > > [root@sds-desk log]# ll messages > -rw-------. 1 root root 106935 May 16 11:05 messages > > Now, it seems to be enabled: > > [root@sds-desk log]# service rsyslog status > rsyslog.service - System Logging Service > Loaded: loaded (/lib/systemd/system/rsyslog.service) > Active: active (running) since Mon, 16 May 2011 11:05:25 -0500; 6min ago > Process: 2387 ExecStartPre=/bin/systemctl stop > systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) > Main PID: 2390 (rsyslogd) > CGroup: name=systemd:/system/rsyslog.service > â 2390 /sbin/rsyslogd -n -c 5 > > > It shows up in system-config-services, but everything related to > enable/disable is grayed out (even running it as root). > > Is this a glitch? What's the expected behavior of rsyslogd? Did you upgrade your system from F14? If so, depending on when you upgraded, you may be seeing https://bugzilla.redhat.com/show_bug.cgi?id=699198 The current proposed workaround is to run: $ systemctl enable rsyslog.service Thanks, James
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
