MonitorWare Knowledge Base

Still no joy. I folowed your advice on the debugging documents.

When I tried to get the debugging output the response is......

Segmentation fault

nothing else.

Looks like I've really botched things up here with rsyslog unfortunately.
The errors and issues seem to be compounding.
Close to considering a total system wipe and re-install..... bummer

I'm inclined to fault rsyslog at this point as I had no other troubles before now and I got it working for about an hour
when suddenly it stopped ALL logging and frankly, I can't see where I did anything else to my system (which had been running fine
for months) is now suddenly very broken.

I'm going to first try uninstalling rsyslog and going back to "syslogd" and see if that restores logging functionality.
After that if no joy, I'll low level format and start over. About a 2 week rebuild job. Several days of backing up critical data first.

A bit dissappointed with rsyslog at the moment to put it mildly

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

you are really putting it mildly. If I were you, I'd say I am sufficiently p**d

Unfortunately, I have no idea what the reason for this issue is on your system. It kind of looks like some library locations are mixed up. This sometimes happens if ./configure is not provided with the right --libdir, --bindir, ... etc for a given system. Other than that, I have no idea. But rsyslog does not modify anything on a system (other than its own components), so it is hard to envision why anything else should be broken. But as I said... I understand your frustration, just can't do much against it

Rainer