702133 – /var/log/messages is empty

Bug 702133 - /var/log/messages is empty

Summary: /var/log/messages is empty

Keywords:
Status:	CLOSED NEXTRELEASE
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	systemd
Sub Component:
Version:	15
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	Lennart Poettering
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2011-05-04 20:51 UTC by Johan Vervloet
Modified:	2011-05-11 14:29 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2011-05-11 14:29:45 UTC
Type:	---
Dependent Products:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Johan Vervloet 2011-05-04 20:51:34 UTC

Description of problem:

Nothing is logged any more in /var/log/messages since I upgraded last week to F15 using preupgrade.

Version-Release number of selected component (if applicable):
systemd-25-1.fc15.x86_64


How reproducible:

cat /var/log/messages

  
Actual results:

nothing


Expected results:

the same output as the 'dmesg' command

Additiona

Comment 1 Michal Schmidt 2011-05-05 08:36:53 UTC

Is the syslog running?:
systemctl status rsyslog.service

Comment 2 Johan Vervloet 2011-05-05 09:09:36 UTC

Thank you for the tip!

rsyslog.service - System Logging Service
	  Loaded: loaded (/lib/systemd/system/rsyslog.service)
	  Active: inactive (dead)
	  CGroup: name=systemd:/system/rsyslog.service


So I guess it is not running.

I am able to start it entering

su -c "/etc/init.d/rsyslog start"

So I guess the problem is that rsyslog is not started automatically when booting?

Comment 3 Gene Snider 2011-05-05 21:42:44 UTC

I had the same problem, something is borked during the upgrade.  This will fix the problem permanently:

sudo systemctl enable rsyslog.service

Gene

Comment 4 Johan Vervloet 2011-05-06 09:04:33 UTC

Thanks for the tip!

Comment 5 Lennart Poettering 2011-05-11 14:29:45 UTC

This has recently been fixed in the rsyslog package. Closing.

Note You need to log in before you can comment on or make changes to this bug.