Been using rsyslog quite nicely since the day 5.8.0 came out. Install all systems the same way: same config and same RPM. Recently installed on newly build CentOS 5.6 box and got this when I fired it up:
Starting system logger: Error during class init for object 'rsyslog runtime' - failing... rsyslogd initializiation failed - global classes could not be initialized. Did you do a "make install"? Suggested action: run rsyslogd with -d -n options to see what exactly fails. rsyslogd run failed with error 1 (see rsyslog.h or try http://www.rsyslog.com/e/-1 to learn what that number means) [ OK ] ps aux does not reveal a running (r)syslog process, but /var/lock/subsys/rsyslog does get created. I assumed that perhaps something broke with 5.8.0 on CentOS 5.6 so I pulled down the latest version - 5.8.3 - built on a similarly configured CentOS 5.6 box and attempted redeployment. Same issue. I followed instructions by running rsyslog -d -n along with sysconfig options to see what the problem is; however, when I launch in the foreground it launches and stays up perfectly. I've tried with both my known working configuration as well as the default config that comes with the system. Because we're talking about the log engine and because the only way it fails is when launched in the background via init, I'm not really sure where to go from here. I suspect a missing dependency, but if that were the case, why would it run in the foreground? Any troubleshooting guidance appreciated. Happy to provide more info upon request. todd _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
