This is a short follow up on a previous blog about using a Raspberry Pi
as a system error log server. When trying to trace a problem, I was confronted
with a log that was mostly filled with what turned out to be spurious error messages.
The content of
/var/log/syslog looked something like this.
http://www.rsyslog.com/e/2007 confirmed that others
were getting 'action 17' suspended messages, there was not much information.
However Danny Tuppeny, who styles himself as a "Linux noob", has a solution. Wonder how long it will take me to attain that
level of "newbieness"... if ever? The trick is to get rid of the last
/etc/rsyslog.conf which I did by transforming the entry
into a comment with the "#" comment symbol.
Then I restarted the server.
The other problem is linked with the One Wire interface which I had enabled when I connected a DHT11 temperature sensor to the Raspberry Pi. (see Temperature Sensors on a Raspberry Pi hosting Domoticz). Reading the Trouble with 1wire topic on the Raspberry forum led me to believe that there have been changes in the way One Wire is implemented in Raspbian. So I looked for a recent posting on the subject and found a solution by AB Electronics UK Tech Support . I had to remove the
/boot/config.txtthat I had explicitly added. It is no longer needed because once the Pi was rebooted, I found that the message about the non registered One Wire bus master no longer appeared while the temperature is obtained from the sensor every five minutes.