Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#860296: lirc is spamming syslog with messages
225 views
Skip to first unread message
Hans-J. Ullrich
Apr 14, 2017, 4:30:02 AM4/14/17
to
Source: lirc
Severity: important
Dear Maintainer,
System is an EEEPC 1005HAG, debian/testing, i386
Sadly I have to tell, the latest version of lirc is spamming syslog with mwessages. To make sure, it is not a problem of an earlier configuration, I deinstalled it completely and reinstalled it new.
The message, which is spamming is the following:
Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
and so on.
Note: Although I have no infrared hardware installed, this issue did not happen with earlier versions.
As a workaround, I had to deinstall the package for now.
It would be nice, if you could take an eye on it.
Thank you very much!
Best
Hans
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Severity: important
Dear Maintainer,
System is an EEEPC 1005HAG, debian/testing, i386
Sadly I have to tell, the latest version of lirc is spamming syslog with mwessages. To make sure, it is not a problem of an earlier configuration, I deinstalled it completely and reinstalled it new.
The message, which is spamming is the following:
Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
and so on.
Note: Although I have no infrared hardware installed, this issue did not happen with earlier versions.
As a workaround, I had to deinstall the package for now.
It would be nice, if you could take an eye on it.
Thank you very much!
Best
Hans
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Paul Menzel
Apr 14, 2017, 8:30:02 AM4/14/17
to
Version: 0.9.4c-9
Dear Debian folks,
Am Freitag, den 14.04.2017, 10:15 +0200 schrieb Hans-J. Ullrich:
> System is an EEEPC 1005HAG, debian/testing, i386
I am using Debian Sid/unstable.
> Sadly I have to tell, the latest version of lirc is spamming syslog
> with mwessages. To make sure, it is not a problem of an earlier
> configuration, I deinstalled it completely and reinstalled it new.
>
> The message, which is spamming is the following:
>
> Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
There is no such directory `/sys/class/rc` here, when no remote control
receiver is installed.
```
$ LANG=C ls -l /sys/class/ | grep rc
drwxr-xr-x 2 root root 0 Apr 14 11:56 powercap
```
> Note: Although I have no infrared hardware installed, this issue did
> not happen with earlier versions.
> As a workaround, I had to deinstall the package for now.
>
> It would be nice, if you could take an eye on it.
That’d would be awesome indeed.
Kind regards,
Paul
Dear Debian folks,
Am Freitag, den 14.04.2017, 10:15 +0200 schrieb Hans-J. Ullrich:
> System is an EEEPC 1005HAG, debian/testing, i386
> Sadly I have to tell, the latest version of lirc is spamming syslog
> with mwessages. To make sure, it is not a problem of an earlier
> configuration, I deinstalled it completely and reinstalled it new.
>
> The message, which is spamming is the following:
>
> Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
> Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
> Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
>
> and so on.
`journalctl -a -f` also shows the constant message flow.
>
> and so on.
There is no such directory `/sys/class/rc` here, when no remote control
receiver is installed.
```
$ LANG=C ls -l /sys/class/ | grep rc
drwxr-xr-x 2 root root 0 Apr 14 11:56 powercap
```
> Note: Although I have no infrared hardware installed, this issue did
> not happen with earlier versions.
> As a workaround, I had to deinstall the package for now.
>
> It would be nice, if you could take an eye on it.
Kind regards,
Paul
Alec Leamas
Apr 15, 2017, 1:00:02 AM4/15/17
to
On 14/04/17 10:15, Hans-J. Ullrich wrote:
>
> Sadly I have to tell, the latest version of lirc is spamming syslog with mwessages. To make sure, it is not a problem of an earlier configuration, I deinstalled it completely and reinstalled it new.
>
> The message, which is spamming is the following:
>
> Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
> rc/rc0/input[0-9]*/event[0-9]*
> Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
> /sys/class/rc/rc0/input[0-9]*/event[0-9]*
> Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
> rc/rc0/input[0-9]*/event[0-9]*
> Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
> /sys/class/rc/rc0/input[0-9]*/event[0-9]*
>
> and so on.
>
> Note: Although I have no infrared hardware installed, this issue did not happen with earlier versions.
> As a workaround, I had to deinstall the package for now.
>
> It would be nice, if you could take an eye on it.
I cannot see that lircd does anything wrong here. The basic message is
that your lirc setup isn't properly configured, which is a simple fact
if you don't have any IR hardware. There are many options in this
situation:
- You could uninstall lirc - and if you don't plan to use it it's
certainly a sensible thing to do.
- You could disable lircd.socket and and lircd.service if you plan to
use it later, leaving package in place.
- You could raise the loglevel in /etc/lirc/lirc_options.conf to mute
the message, if you for some reason want to run lircd despite the
message (but why?).
- Last but not least, you could try to configure lirc. In this case, the
above message is indeed helpful in some situations.
So, my basic understanding is that this issue should be closed as
not-a-bug. I will close it unless there is more input.
Cheers!
--alec
David Fries
Sep 20, 2018, 1:40:02 AM9/20/18
to
Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296
Dear Maintainer,
Just upgraded to stretch and got bit by this as well, it's been
roughly a day and it's logged 149,336 messages to syslog, purging
ASAP.
Would it be accepted if I wrote a patch to write this message once on
startup and again once if it finds a device and that device is closed?
Sep 19 23:47:26 localhost lircd[24438]: lircd-0.9.4c[24438]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Sep 19 23:47:26 localhost lircd-0.9.4c[24438]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15), LANGUAGE=C (charmap=ISO-8859-15)
ii init-system-helpers 1.48
ii libasound2 1.1.3-5
ii libc6 2.24-11+deb9u3
ii libftdi1-2 1.3-2+b2
ii libgcc1 1:6.3.0-18+deb9u1
ii liblirc-client0 0.9.4c-9
ii liblirc0 0.9.4c-9
ii libportaudio2 19.6.0-1
ii libstdc++6 6.3.0-18+deb9u1
ii libsystemd0 232-25+deb9u4
ii libudev1 232-25+deb9u4
ii libusb-0.1-4 2:0.1.12-30
ii libusb-1.0-0 2:1.0.21-1
ii lsb-base 9.20161125
ii python3 3.5.3-1
Versions of packages lirc recommends:
pn gir1.2-vte <none>
ii python3-gi 3.22.0-2
pn python3-yaml <none>
Versions of packages lirc suggests:
pn ir-keytable <none>
pn lirc-compat-remotes <none>
pn lirc-doc <none>
pn lirc-drv-irman <none>
ii lirc-x 0.9.4c-9
ii setserial 2.17-50
-- Configuration Files:
/etc/lirc/lircd.conf [Errno 2] No such file or directory: '/etc/lirc/lircd.conf'
-- no debconf information
Version: 0.9.4c-9
Followup-For: Bug #860296
Dear Maintainer,
Just upgraded to stretch and got bit by this as well, it's been
roughly a day and it's logged 149,336 messages to syslog, purging
ASAP.
Would it be accepted if I wrote a patch to write this message once on
startup and again once if it finds a device and that device is closed?
Sep 19 23:47:26 localhost lircd[24438]: lircd-0.9.4c[24438]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Sep 19 23:47:26 localhost lircd-0.9.4c[24438]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15), LANGUAGE=C (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lirc depends on:
Init: systemd (via /run/systemd/system)
ii init-system-helpers 1.48
ii libasound2 1.1.3-5
ii libc6 2.24-11+deb9u3
ii libftdi1-2 1.3-2+b2
ii libgcc1 1:6.3.0-18+deb9u1
ii liblirc-client0 0.9.4c-9
ii liblirc0 0.9.4c-9
ii libportaudio2 19.6.0-1
ii libstdc++6 6.3.0-18+deb9u1
ii libsystemd0 232-25+deb9u4
ii libudev1 232-25+deb9u4
ii libusb-0.1-4 2:0.1.12-30
ii libusb-1.0-0 2:1.0.21-1
ii lsb-base 9.20161125
ii python3 3.5.3-1
Versions of packages lirc recommends:
pn gir1.2-vte <none>
ii python3-gi 3.22.0-2
pn python3-yaml <none>
Versions of packages lirc suggests:
pn ir-keytable <none>
pn lirc-compat-remotes <none>
pn lirc-doc <none>
pn lirc-drv-irman <none>
ii lirc-x 0.9.4c-9
ii setserial 2.17-50
-- Configuration Files:
/etc/lirc/lircd.conf [Errno 2] No such file or directory: '/etc/lirc/lircd.conf'
-- no debconf information
0 new messages