05-25-2014, 07:24 PM
Thanks for referring me to that post. I ran the configuration test indicated in the post to which you referred above. Here are the results:
rsyslogd: version 7.4.4, config validation run (level 1), master config /etc/rsyslog.d/50-default.conf
rsyslogd: End of config validation run. Bye.
I assume the lack of commentary in the report means no errors exist in the rsyslog configuration. Or, it could mean it didn't actually run, since I later discovered I needed to stop rsyslog first--which I didn't do...
The file /etc/rsyslog.conf claims I can find more information at /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html, but there is no such location. However, I did find something at /usr/share/doc/rsyslog/README.Debian; according to that file, setting RSYSLOGD_OPTIONS="" in etc/default/rsyslog to RYSYLOGD_OPTIONS="-c0", will make rsyslog command-line compatible with sysklogd, and automatically load a default set of modules. However, the file points out that the "default in Debian is -c3, i.e. command line arguments like -r or -m 0 have no effect and instead have to be configured via special configuration directives in rsyslog.conf." Because RSYSLOGD_OPTIONS in /etc/default/rsyslog was an empty string, I changed it to the Debian default, "-c3".
Upon reboot, syslog was not working. I changed the setting to "-c0" and rebooted again, but syslog still did not run.
Long story short, I spent several more hours delving yet further into the maze of rsyslog manpages, trying to figure out how to modify the config file so rsyslog would work. Then, it suddenly occurred to me that I was W-A-Y too far into trying to fix something that should just work and that the typical user should not even have to concern himself with. I decided it was time to simply abandon the idea of using Linux Lite. As I closed the numerous terminals and two browsers I'd been using, I suddenly had the urge to look at dmesg to see whether rsyslog even received the instruction to start up; and if so, whether it also had received the instruction to halt, for some reason. Lo and behold, all of the content normally displayed in syslog is showing up in dmesg.
I can't tell if changing the RSYSLOGD_OPTIONS caused this, or it's is the way the developers set rsyslog up--if so, I expect you'd have told me. And I could return the setting to the empty string to find out, but I'm frankly tired of the entire pursuit.
I do, at least, have a log to look at now, which is documenting my iptables output nicely. So, despite that syslog is still not working as expected, I'm done messing around with this issue, and just wanted to report the outcome for the benefit of others.
Thanks for your assistance.
rsyslogd: version 7.4.4, config validation run (level 1), master config /etc/rsyslog.d/50-default.conf
rsyslogd: End of config validation run. Bye.
I assume the lack of commentary in the report means no errors exist in the rsyslog configuration. Or, it could mean it didn't actually run, since I later discovered I needed to stop rsyslog first--which I didn't do...
The file /etc/rsyslog.conf claims I can find more information at /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html, but there is no such location. However, I did find something at /usr/share/doc/rsyslog/README.Debian; according to that file, setting RSYSLOGD_OPTIONS="" in etc/default/rsyslog to RYSYLOGD_OPTIONS="-c0", will make rsyslog command-line compatible with sysklogd, and automatically load a default set of modules. However, the file points out that the "default in Debian is -c3, i.e. command line arguments like -r or -m 0 have no effect and instead have to be configured via special configuration directives in rsyslog.conf." Because RSYSLOGD_OPTIONS in /etc/default/rsyslog was an empty string, I changed it to the Debian default, "-c3".
Upon reboot, syslog was not working. I changed the setting to "-c0" and rebooted again, but syslog still did not run.
Long story short, I spent several more hours delving yet further into the maze of rsyslog manpages, trying to figure out how to modify the config file so rsyslog would work. Then, it suddenly occurred to me that I was W-A-Y too far into trying to fix something that should just work and that the typical user should not even have to concern himself with. I decided it was time to simply abandon the idea of using Linux Lite. As I closed the numerous terminals and two browsers I'd been using, I suddenly had the urge to look at dmesg to see whether rsyslog even received the instruction to start up; and if so, whether it also had received the instruction to halt, for some reason. Lo and behold, all of the content normally displayed in syslog is showing up in dmesg.
I can't tell if changing the RSYSLOGD_OPTIONS caused this, or it's is the way the developers set rsyslog up--if so, I expect you'd have told me. And I could return the setting to the empty string to find out, but I'm frankly tired of the entire pursuit.
I do, at least, have a log to look at now, which is documenting my iptables output nicely. So, despite that syslog is still not working as expected, I'm done messing around with this issue, and just wanted to report the outcome for the benefit of others.
Thanks for your assistance.