Bug 702133

Summary: /var/log/messages is empty
Product: [Fedora] Fedora Reporter: Johan Vervloet <bulk>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: genes1122, johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-11 14:29:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.