Fedora 10 and sysklogd - no syslogd running

[Pat McClung]

A few days ago I upgraded (via Fedora 10 DVD) from Fedora 9 to Fedora 10 on my old Athlon XP 2700 i686 w/ NFORCE 2 chipset.

In addition to the familiar horrors (e.g., no X11 screen with fglrx driver) I found that I had no syslogd or klogd running. Looking at the sysklogd service, I found that it was disabled, nor could I enable it from the Service Configuration Panel.

I looked at the sysklogd init in /etc/rc.d/init.d, and it looks ok, but nothing in dmesg or boot.log or anaconda.log as to whether it ran (correctly or not).

I put the commands
syslogd
and
klogd

into /etc/rc.d/rc.local, and now it comes up with klogd and syslogd running, and I have /var/log/messages, but no file rollover, etc.

Any ideas what's wrong with the sysklogd init?

Pat

[vallimar]

sysklogd was replaced with rsyslog.
File rollover is handled by logrotate.

[Pat McClung]

Well, yeah.
Removing sysklogd looks a little scary to me.
First of all, the Fedora 10 installer installed sysklogd, not rsyslog.

[root@apollo pat]# yum list installed sysklogd
Installed Packages
sysklogd.i386 1.5-3.fc10 installed

If I try
yum remove sysklogd
it is going to remove 255 other packages as dependencies.

================================================== ==============================
Package Arch Version Repository
Size
================================================== ==============================
Removing:
sysklogd i386 1.5-3.fc10 installed 116 k
Removing for dependencies:
BackupPC noarch 3.1.0-3.fc10 installed 2.2 M
NetworkManager i386 1:0.7.0-0.12.svn4326.fc10 installed 2.9 M
NetworkManager-gnome i386 1:0.7.0-0.12.svn4326.fc10 installed 889 k
NetworkManager-openvpn i386 1:0.7.0-16.svn4326.fc10 installed 433 k
NetworkManager-vpnc i386 1:0.7.0-0.11.svn4326.fc10 installed 315 k
PackageKit i386 0.3.9-4.fc10 installed 1.0 M
PackageKit-glib i386 0.3.9-4.fc10 installed 301 k
PackageKit-udev-helper i386 0.3.9-4.fc10 installed 118 k
PackageKit-yum i386 0.3.9-4.fc10 installed 316 k
PackageKit-yum-plugin i386 0.3.9-4.fc10 installed 120 k
PolicyKit-gnome i386 0.9-3.fc10 installed 398 k
RealPlayer i586 10.1.0.3590-20071011 installed 12 M
akmods noarch 0.3.3-2.fc10 installed 26 k

etc. etc. etc.

xorg-x11-xfs i386 1:1.0.5-3.fc10 installed 116 k
xsane i386 0.995-5.fc10 installed 4.9 M
xsane-gimp i386 0.995-5.fc10 installed 633 k
xulrunner i386 1.9.0.4-1.fc10 installed 22 M
xulrunner-devel i386 1.9.0.4-1.fc10 installed 35 M
yelp i386 2.24.0-3.fc10 installed 3.2 M
yum-updatesd noarch 1:0.9-1.fc9 installed 54 k
zvbi i386 0.2.30-1.fc9 installed 1.1 M

Transaction Summary
================================================== ==============================
Install 0 Package(s)
Update 0 Package(s)
Remove 255 Package(s)

Is this ok [y/N]: N

Don't think so!!!!!

I could try

rpm -e --nodeps sysklogd-1.5.3.fc10.i386.rpm
yum install rsyslog

Think I oughta try that? (gulp!)

(logrotate is also installed but it doesn't work)

[root@apollo pat]# yum list installed |grep rotate
logrotate.i386 3.7.7-1.fc10 installed

[vallimar]

I thought rsyslog had an obsoletes line for sysklogd but checking just now, it doesn't.
So, in that case try to install rsyslog first, then you should be able to do a regular
yum remove sysklogd, as the programs are looking for a generic "syslog" provides
and not a specific package.

It was likely installed by F10, because thats what you had for F9 and you did an upgrade.
Fresh installs should only do rsyslog (or mine did anyways).

Rsyslog can run in compatible mode with syslog configuration files, but unless you had
anything custom, you should just use the rsyslog.conf one so you don't have to do extra
tinkering.

Lastly, you could just stick with the older syslogd and klogd and try to manually activate
them from the commandline "chkconfig syslogd on", "chkconfig klog on" assuming it has
proper entries in /etc/rc.d/init.d/.

[Pat McClung]

Tried to
yum install rsyslog ...
but it fails with a conflict with sysklogd.
removed sysklogd with rpm -e --nodeps
and installed rsyslog ... with yum
on restart, rsyslogd now running and logging works great.
Thanks to all.
Pat

[vallimar]

Great! Glad it's working.
I did check for conflicts, but the version marked in the file was less than yours so I thought it would install in parallel, but you got the right workaround anyways.