January 2, 2018
Syslog Server on Raspian

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.

Dec 22 13:06:00 domo kernel: [2032196.597521] w1_master_driver w1_bus_master1: Family 0 for 00.211900000000.23 is not registered. Dec 22 13:06:53 domo kernel: [2032249.917713] w1_master_driver w1_bus_master1: Family 0 for 00.a11900000000.af is not registered. Dec 22 13:06:53 domo rsyslogd-2007: action 'action 17' suspended, next retry is Tue Jan 2 13:08:23 2018 [try http://www.rsyslog.com/e/2007 ] Dec 22 13:07:31 domo kernel: [2032287.837859] w1_master_driver w1_bus_master1: Family 0 for 00.611900000000.65 is not registered. Dec 22 13:08:22 domo kernel: [2032338.598619] w1_master_driver w1_bus_master1: Family 0 for 00.e11900000000.e9 is not registered. Dec 22 13:08:46 domo rsyslogd-2007: action 'action 17' suspended, next retry is Tue Jan 2 13:10:16 2018 [try http://www.rsyslog.com/e/2007 ] Dec 22 13:09:25 domo kernel: [2032401.600268] w1_master_driver w1_bus_master1: Family 0 for 00.111900000000.9d is not registered.

While 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 entry in /etc/rsyslog.conf which I did by transforming the entry into a comment with the "#" comment symbol.

pi@domo:~ $ sudo nano /etc/rsyslog.conf
... # The named pipe /dev/xconsole is for the `xconsole' utility. To use it, # you must invoke `xconsole' with the `-file' option: # # $ xconsole -file /dev/xconsole [...] # # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. I removed it completely! # #daemon.*;mail.*;# news.err;# *.=debug;*.=info;# *.=notice;*.=warn |/dev/xconsole

Then I restarted the server.

pi@domo:~ $ sudo systemctl restart rsyslog

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

dtoverlay=w1-gpio, gpiopin=24
line in /boot/config.txt that 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.

Syslog Server on Raspian