Bug 20969

Summary:	cannot redirect sensord output to local4
Product:	Mageia	Reporter:	Christian C <bugzzzz>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	lm_sensors-3.3.5-3.mga5	CVE:
Status comment:

Description Christian C 2017-05-29 17:32:09 CEST

Description of problem:
In order to avoid cluttering /var/log/messages with periodical messages from sensord, I have configured /etc/syslog.conf (according to the sensord man page) as follows :

*.info;...;local4.none;local4.warn  /var/log/messages
local4.info                        -/var/log/sensors
local4.alert                        /dev/console
local4.alert                        *

Unfortunatly, this configuration generates errors in /var/log/messages :

May 29 16:53:30 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11019" x-info="http://www.rsyslog.com"] start
May 29 16:53:30 localhost rsyslogd-3000: unknown priority name ".."
May 29 16:53:30 localhost rsyslogd-2184: action '*' treated as ':omusrmsg:*' - please change syntax, '*' will not be supported in the future [try http://www.rsyslog.com/e/2184 ]
May 29 16:53:30 localhost rsyslogd-2207: error during parsing file /etc/syslog.conf, on or before line 38: warnings occured in file '/etc/syslog.conf' around line 38 [try http://www.rsyslog.com/e/2207 ]
May 29 16:53:30 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11019" x-info="http://www.rsyslog.com"] start
May 29 16:53:30 localhost rsyslogd-3000: unknown priority name ".."
May 29 16:53:30 localhost rsyslogd-2184: action '*' treated as ':omusrmsg:*' - please change syntax, '*' will not be supported in the future [try http://www.rsyslog.com/e/2184 ]
May 29 16:53:30 localhost rsyslogd-2207: error during parsing file /etc/syslog.conf, on or before line 38: warnings occured in file '/etc/syslog.conf' around line 38 [try http://www.rsyslog.com/e/2207 ]

I had to correct /etc/syslog.conf as follows to get a ?correct? rsyslog restart :

May 29 17:07:56 localhost rsyslogd-3000: unknown priority name ".."
May 29 17:07:56 localhost drakxservices[7162]: running: /bin/mountpoint -q /sys/fs/cgroup/systemd
May 29 17:07:56 localhost drakxservices[7162]: running: /bin/systemctl --quiet is-active rsyslog.service
May 29 17:07:56 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11785" x-info="http://www.rsyslog.com"] start
May 29 17:07:56 localhost rsyslogd-3000: unknown priority name ".."
May 29 17:07:56 localhost drakxservices[7162]: running: /bin/mountpoint -q /sys/fs/cgroup/systemd
May 29 17:07:56 localhost drakxservices[7162]: running: /bin/systemctl --quiet is-active rsyslog.service
May 29 17:07:59 localhost drakxservices[7162]: GP_LANG="UTF-8" service rsyslog restart
May 29 17:07:59 localhost drakxservices[7162]: GP_LANG="UTF-8" service rsyslog restart
May 29 17:07:59 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11785" x-info="http://www.rsyslog.com"] exiting on signal 15.
May 29 17:07:59 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11785" x-info="http://www.rsyslog.com"] exiting on signal 15.
May 29 17:07:59 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11801" x-info="http://www.rsyslog.com"] start
May 29 17:07:59 localhost rsyslogd-3000: unknown priority name ".."
May 29 17:07:59 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="11801" x-info="http://www.rsyslog.com"] start
May 29 17:07:59 localhost rsyslogd-3000: unknown priority name ".."
May 29 17:07:59 localhost drakxservices[7162]: running: /bin/mountpoint -q /sys/fs/cgroup/systemd
May 29 17:07:59 localhost drakxservices[7162]: running: /bin/mountpoint -q /sys/fs/cgroup/systemd
May 29 17:07:59 localhost drakxservices[7162]: running: /bin/systemctl --quiet is-active rsyslog.service
May 29 17:07:59 localhost drakxservices[7162]: running: /bin/systemctl --quiet is-active rsyslog.service
May 29 17:18:17 localhost sensord: Chip: acpitz-virtual-0
May 29 17:18:17 localhost sensord: Chip: acpitz-virtual-0
May 29 17:18:21 localhost sensord: Adapter: Virtual device
May 29 17:18:21 localhost sensord:   temp1: 59.0 C
May 29 17:18:21 localhost sensord:   temp2: 54.0 C
May 29 17:18:21 localhost sensord:   temp3: 59.0 C
May 29 17:18:21 localhost sensord: Chip: coretemp-isa-0000
May 29 17:18:21 localhost sensord: Adapter: ISA adapter
May 29 17:18:21 localhost sensord:   Core 0: 54.0 C
May 29 17:18:21 localhost sensord:   Core 1: 54.0 C
May 29 17:18:21 localhost sensord: Chip: dell_smm-virtual-0
May 29 17:18:21 localhost sensord: Adapter: Virtual device
May 29 17:18:21 localhost sensord:   Processor Fan: 3076 RPM
May 29 17:18:21 localhost sensord: Adapter: Virtual device
May 29 17:18:21 localhost sensord:   temp1: 59.0 C
May 29 17:18:21 localhost sensord:   temp2: 54.0 C
May 29 17:18:21 localhost sensord:   temp3: 59.0 C
May 29 17:18:21 localhost sensord: Chip: coretemp-isa-0000
May 29 17:18:21 localhost sensord: Adapter: ISA adapter
May 29 17:18:21 localhost sensord:   Core 0: 54.0 C
May 29 17:18:21 localhost sensord:   Core 1: 54.0 C
May 29 17:18:21 localhost sensord: Chip: dell_smm-virtual-0
May 29 17:18:21 localhost sensord: Adapter: Virtual device
May 29 17:18:21 localhost sensord:   Processor Fan: 3076 RPM
May 29 17:18:21 localhost sensord:   fan2: 3583 RPM
May 29 17:18:21 localhost sensord:   fan2: 3583 RPM
May 29 17:18:21 localhost sensord:   CPU: 54.0 C
May 29 17:18:21 localhost sensord:   CPU: 54.0 C
May 29 17:18:21 localhost sensord:   CPU: 66.0 C
May 29 17:18:21 localhost sensord:   CPU: 66.0 C
May 29 17:18:21 localhost sensord:   Other: 54.0 C
May 29 17:18:21 localhost sensord:   Other: 54.0 C
May 29 17:18:21 localhost sensord:   GPU: 59.0 C
May 29 17:18:21 localhost sensord:   GPU: 59.0 C

I run the sensord.service by :
ExecStart=/usr/sbin/sensord -i $INTERVAL -l $LOG_INTERVAL -f local4

But I still receive the sensord output (info level) in /var/log/messages and a /var/log/sensors is filled with the same contents.

Version-Release number of selected component (if applicable):
rsyslog-8.4.2-6.mga5

How reproducible:


Steps to Reproduce:
1.run rsyslog with the above configuration
2.run sensord with the above configuration
3.

Comment 1 Marja Van Waes 2017-05-29 20:57:21 CEST

Assigning to all packagers collectively, since there is no registered maintainer for this package.

Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Comment 2 Marja Van Waes 2018-09-18 15:53:22 CEST

Hi Christian,


Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

Status: NEW => RESOLVED
Resolution: (none) => OLD