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.
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"