PDA

View Full Version : rsyslog.i686 0:4.4.2-5.fc13 error in scriptlet


kyryder
11th February 2010, 04:06 PM
SOLVED IN POST # 5 (http://forums.fedoraforum.org/showthread.php?p=1329532#post1329532)


Hello,

I received a error when installing rsyslog.i686 0:4.4.2-5.fc13 and now the service will not start.

Anyone else seeing similar errors?

The bad part is when trying to down grade I get: Only Upgrade available on package: rsyslog-4.4.2-5.fc13.i686

Ky

Sagitter
11th February 2010, 09:04 PM
Read here:

http://fedoraforum.org/forum/showthread.php?t=240337

kyryder
11th February 2010, 11:10 PM

Yeah, I guess you could disable rsyslog but I was hoping for a working solution.
Why go through the whole rescue mode thing when you can just:

su -c 'chkconfig rsyslog off'

Still looking for a working solution. ;)
Ky

jvillain
12th February 2010, 12:50 AM
Ya,, that is what I ended up doing as well. I have Lots of other stuff that broke as well so I am guessing it is some thing big like glibc . There were a lot of library upgrades in there. Unfortunately I can't roll back the transaction.

---------- Post added at 04:50 PM CST ---------- Previous post was at 04:04 PM CST ----------

Running rsyslogd -n off the command line comes back with a segmentation fault so it definitely smells like a library miss match. I tried installing sysklogd just to get a working logger but it won't install with rsylogd installed. Removing rsyslogd first would mean uninstalling most of the OS. You used to be able to have rsyslogd and syslogng installed at the same time but syslogng doesn't seem to exist any more.

Grrrrrrrr.

kyryder
12th February 2010, 04:36 AM
Well, I finally got tired of looking for a fix for this and downloaded the new rsyslog package from koji. (http://koji.fedoraproject.org/koji/buildinfo?buildID=155653)

All is working again,
Hope this helps,

Ky

jvillain
12th February 2010, 07:59 AM
That work like a charm for me as well. Thanks for that. Now maybe I can figure out what is going on with the rest of my stuff. Any one doing this don't forget to do a "service rsyslog restart" and a "chkconfig rsyslog on"