Bug#860296: lirc is spamming syslog with messages

[David Fries]

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)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5
ii  libc62.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  libportaudio219.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
ii  python3-gi3.22.0-2
pn  python3-yaml  

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
ii  lirc-x   0.9.4c-9
ii  setserial2.17-50

-- Configuration Files:
/etc/lirc/lircd.conf [Errno 2] No such file or directory: '/etc/lirc/lircd.conf'

-- no debconf information

Bug#860296: [Pkg-lirc-maint] Bug#860296: lirc is spamming syslog with messages

[Jörg Frings-Fürst]

Hi,


Am Sonntag, den 20.08.2017, 15:52 +0200 schrieb Alec Leamas:
> 
> On 20/08/17 12:22, Jörg Frings-Fürst wrote:
> > Hello Alec,
> > >   > Lirc is installed as a dependency.
> > > 
[...]

> > This is absolutely unnecessary*, consumes resources, costs money and
> > reduces lifetime of the hard disks.
> 
> 
> Indeed. But sweeping this under the carpet by decreasing the log 
> interval isn't really the proper solution here. IMHO user should disable 
> the service or just remove the package. Having lircd  running without 
> any ir hardware attached just makes no sense.
> 
> > And why must every messages have to be logged twice?
> 
> Because in a scenario when the user really tries to setup lircd, lircd 
> keeps logging until a device is attached (i. e., hotplugged).
> 
> Of course, the log interval could be increased. But the basic problem is 
> that a lot of users seems to have lircd running without any purpose. We 
> need to address this, perhaps by having the service disabled/stopped by 
> default, dunno.
> 

No, I disagree your statement. The main problem is not the user. The
problem is that lirc logs not found hardware. IMHO is enough to log it
once on start and one! on every change. That also enough for testing
the setup.

For the twice log I have open a new bug report.

> 
> Cheers!
> 
> --alec
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


signature.asc
Description: This is a digitally signed message part

Bug#860296: [Pkg-lirc-maint] Bug#860296: lirc is spamming syslog with messages

[Alec Leamas]

On 20/08/17 12:22, Jörg Frings-Fürst wrote:

Hello Alec,



  > Lirc is installed as a dependency.

This is IMHO the basic problem. lirc should really never be installed as
a dependency (lirc-lib is another story). Installing lirc means
installing the server/service which as of now means running some
thousands lines of old code handling all sorts of user input as root.
This should only be done if you really need the server i. e., have IR
hardware attached. If not used, the server should be disabled or the
lirc package just removed.



No, the basic problem is lircd every second log 2 lines. Roundabout
thats 222 * 60 * 60 * 24 * 30 = 575.424.000 bytes / month . And only
why lircd found no hardware.

This is absolutely unnecessary*, consumes resources, costs money and
reduces lifetime of the hard disks.



Indeed. But sweeping this under the carpet by decreasing the log 
interval isn't really the proper solution here. IMHO user should disable 
the service or just remove the package. Having lircd  running without 
any ir hardware attached just makes no sense.



And why must every messages have to be logged twice?


Because in a scenario when the user really tries to setup lircd, lircd 
keeps logging until a device is attached (i. e., hotplugged).


Of course, the log interval could be increased. But the basic problem is 
that a lot of users seems to have lircd running without any purpose. We 
need to address this, perhaps by having the service disabled/stopped by 
default, dunno.



Cheers!

--alec

Bug#860296: lirc is spamming syslog with messages

[Jörg Frings-Fürst]

Hello Alec,

On Fri, 11 Aug 2017 10:00:27 +0200 Alec Leamas  wrote:
> On Wed, 09 Aug 2017 12:43:19 +0200 
> =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?=  wrote:
> 
>  >
>  > the same here.
>  >
>  > Lirc is installed as a dependency.
> 
> This is IMHO the basic problem. lirc should really never be installed as 
> a dependency (lirc-lib is another story). Installing lirc means 
> installing the server/service which as of now means running some 
> thousands lines of old code handling all sorts of user input as root. 
> This should only be done if you really need the server i. e., have IR 
> hardware attached. If not used, the server should be disabled or the 
> lirc package just removed.
> 

No, the basic problem is lircd every second log 2 lines. Roundabout
thats 222 * 60 * 60 * 24 * 30 = 575.424.000 bytes / month . And only
why lircd found no hardware.

This is absolutely unnecessary*, consumes resources, costs money and
reduces lifetime of the hard disks.

And why must every messages have to be logged twice?

>  > My suggestion would be to test for the requested devices at startup 
> once and
>  > then use the device hotplug to load the driver and to activate lirc.
> 
> This is not really possible since all sorts of hardware can be used for 
> IR reception. This includes generic USB devices such as FTDI chips and 
> e. g., serial ports where noit hotplugging isn't available.
> 
> As of now, lircd is using systemd socket activation and is started when 
> the fist client tries to connect. Untortunately, any application with 
> lirc support will try to connect and thus starts the server.
>

I think thats the requested functionality. But once again: Spamming the log
are unnecessary.

 
> 
> Cheers!
> 
> --alec
> 
> 

CU
Jörg


* This is as nonsensical as if cups would log every second that it has 
  found no printer.
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  330dfaa3e4985d5c45f5730bd2c21693c2c5e04e

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


signature.asc
Description: This is a digitally signed message part

Bug#860296: lirc is spamming syslog with messages

[Alec Leamas]

On Wed, 09 Aug 2017 12:43:19 +0200 
=?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?=  wrote:


>
> the same here.
>
> Lirc is installed as a dependency.

This is IMHO the basic problem. lirc should really never be installed as 
a dependency (lirc-lib is another story). Installing lirc means 
installing the server/service which as of now means running some 
thousands lines of old code handling all sorts of user input as root. 
This should only be done if you really need the server i. e., have IR 
hardware attached. If not used, the server should be disabled or the 
lirc package just removed.


> My suggestion would be to test for the requested devices at startup 
once and

> then use the device hotplug to load the driver and to activate lirc.

This is not really possible since all sorts of hardware can be used for 
IR reception. This includes generic USB devices such as FTDI chips and 
e. g., serial ports where noit hotplugging isn't available.


As of now, lircd is using systemd socket activation and is started when 
the fist client tries to connect. Untortunately, any application with 
lirc support will try to connect and thus starts the server.



Cheers!

--alec

Bug#860296: lirc is spamming syslog with messages

[Jörg Frings-Fürst]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

the same here.

Lirc is installed as a dependency.

Because of spamming the partition overflows and the disks are not going to me
to sleep mode.

So I think the severity important isn't enough, serious is better for this bug.

My suggestion would be to test for the requested devices at startup once and
then use the device hotplug to load the driver and to activate lirc.

CU
Jörg



- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lirc depends on:
ii  init-system-helpers  1.49
ii  libasound2   1.1.3-5
ii  libc62.24-12
ii  libftdi1-2   1.3-2+b3
ii  libgcc1  1:7.1.0-10
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   7.1.0-10
ii  libsystemd0  234-2
ii  libudev1 234-2
ii  libusb-0.1-4 2:0.1.12-31
ii  libusb-1.0-0 2:1.0.21-2
ii  lsb-base 9.20161125
ii  python3  3.5.3-3

Versions of packages lirc recommends:
pn  gir1.2-vte
ii  python3-gi3.22.0-2+b1
ii  python3-yaml  3.12-1+b1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlmK50cACgkQCfifPIyh
0l3lnQ/7Bz39Ub1qzcpgN2jne0yaJImBCw2napgX8Z9MI67wsoHvX+QDPWp5A4fA
pdN42+IZlFPH9zmlZ17GlkrsRrmkWcNDRbOzad1/fiU1af1C46qKIRLrlqeBFWzO
sD49xUNc5VRkVTWjwnoOth/uZX4wgiqqc0YFC4Ov5mKFeipDwT2xX7fuTyT9jsOQ
YJ+MBxCMYIPouRNI02lOiHLBVGn6p5+FHC6qTkNLjP4vhaZj9C5awbrXnXl2aAw2
iUhJiGqZfQsg1nPhuFiDlX60TgGsKG3XWSGupJVGtVf9fzzjWk1hOCV6NzPPb0Nr
0GUrrFiKhfieGGKNCjlqc9Fhv9waDhdQuNKfPpargq0ptM8NgK7iHyXvcqoNnCGo
3o1YCHRyC2H8s9tcgcAUFcM6FCLQej1tbfWBc/w45G1hGR4R2cNEDHT0m5E2j3P/
A0VSOA774XaD9Lo/Vo0CDNPiq0lNtj7Gz4n2W3dYCp5hTKXHm+CLCjpSEychCf4D
5WzEGdAvBkulZfj0fd7KyxzaNrLDtPDnyqmnGN3N+rfvcmCIbsNcxP4TOybn61hw
hrpWTlJ/86dSyLGDfguS82K46/jw5UGPSqhpYTKQyW2THHwzxBa142sWZyw7rKNt
QBUpA5fnilFTW0f+xlOmT2SoWnWQgddyqlsJ5v741fBLSh1QXk0=
=msGQ
-END PGP SIGNATURE-

Bug#860296: lirc is spamming syslog with messages

[Ayke van Laethem]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

Dear Maintainer,

Unfortunately I can't reproduce the uirw issue I reported (eating up
disk space), but I now have the exact same problem as reported above.

I noticed that by default the services lircd-uinput, irexec and lircmd
are running. Stopping all three makes sure that lirc doesn't have
connected clients preventing the error. I wonder why all these services
are running by default, consuming system resources (and logging a
message once per second).

Semi-related: here is a patch that should make the error somewhat more
descriptive (actually fixing a bug in LIRC):
https://sourceforge.net/u/avl555/lirc/ci/7b25283ef0393035d82cb0a10fe7331fc4629c44/

Bug#860296: lirc is spamming syslog with messages

[Ayke van Laethem]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

Dear Maintainer,

I believe this is a real bug. The problem is not that it logs the error
(which it should), the problem is that it *keeps* logging the error
without any form of throttling quickly filling the whole syslog:

$ ls -l /var/log/syslog
-rw-r- 1 root adm 4,2G jul 28 16:33 /var/log/syslog

Sample from syslog:
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument

This became a problem during the upgrade from jessie to stretch. During
a large part of the upgrade my whole root disk was filled with useless
log messages (0 bytes free storage), so I'm actually surprised it
finished upgrading without issues. Upgrading is a critical operation so
I would consider this an important bug.

The configuration files attached here *should* be enough to reproduce
the issue. I am willing to provide the original configuration files that
I used.

In my opinion, lirc should be fixed to not retry this often or fail the
first time - there's no use in retrying with an invalid configuration.

A workaround is disabling lirc in stretch:

systemctl disable lirc


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5
ii  libc62.24-11+deb9u1
ii  libftdi1-2   1.3-2+b2
ii  libgcc1  1:6.3.0-18
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25+deb9u1
ii  libudev1 232-25+deb9u1
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
ii  python3-gi3.22.0-2
ii  python3-yaml  3.12-1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

-- Configuration Files:
/etc/lirc/hardware.conf changed:
LIRCD_ARGS=""
LOAD_MODULES=false
DRIVER="uirt2"
DEVICE="/dev/ttyACM0"
MODULES=""
LIRCD_CONF=""
LIRCMD_CONF=""

/etc/lirc/lircd.conf changed:
begin remote
  name  philips
  bits   32
  eps30
  aeps  100
  one 0 0
  zero0 0
  post_data_bits  16
  post_data  0x0
  gap  114685
  toggle_bit_mask 0xF5108D99
  begin codes
  KEY_LEFT 0x97309DDB
  KEY_LEFT 0x6E3215BE
  KEY_RIGHT0x6FA99F00
  KEY_UP   0xA79C13E5
  KEY_DOWN 0xFB6351AD
  KEY_FORWARD  0x2200
  KEY_REWIND   0x1408
  KEY_PLAYPAUSE0x1500
  KEY_MENU 0xFEF2B8BF
  KEY_INFO 0x0F00
  KEY_INFO 0x0F08
  KEY_MUTE 0x0D08
  KEY_VOLUMEUP 0x1000
  KEY_VOLUMEDOWN   0x1108
  end codes
end remote


-- no debconf information

Bug#860296: lirc is spamming syslog with messages

[Dominik George]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Same issue here.

lirc got installed as a dependency, and I really think it should not
cause such issues if it is.

- -- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5
ii  libc62.24-10
ii  libftdi1-2   1.3-2+b2
ii  libgcc1  1:6.3.0-17
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   6.3.0-17
ii  libsystemd0  232-23
ii  libudev1 232-23
ii  libusb-0.1-4 2:0.1.12-31
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
ii  python3-gi3.22.0-2
ii  python3-yaml  3.12-1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlkaJ78xGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pZo1Q//cde60dUWozj4O7TGMvAQyV6aZ5/M
OEHGF2bUERbE2oeiWvzreaSBl9fUrUTMTX/aCUb8po/ojSQTFQh0qBtIF18re8Rx
cK4t8ClVh/cPwliGQe5jO2NJXkoWi1J0HqxV7+nSUu1NNACXumaufXYVB+NH4jgr
BDWRVutrLlLs4pXk+QYmQcvD4+krYsh+fvNxWnBvUyDrh/yO7Wlo5WHnj5/1mijg
DNOp+mgqxCz13DgGchuuYkDyIOlXdmdzYtcsiQ2fvpUcBJ4wsZsLopnDDf/aMrri
xALQZyXX2ML5rD6XaXkgzUfxKGik72mxV0e5UcdQG8QxyboufgTSz2aaISEztoLb
cQyCvmKaAGux3fMJDfEwSRmqfXyU1Zo1j2mFe4hnLqDY2NrRshd9DIO0oRqV0LPb
wjD0bHM9wdH06LhkRTSDqtJkQSJTBmmJ8D7uBt8MAP6h81mIw1D35cLs3NwR34SR
Y1Z56D07YOvy5n7Ml0snEX36MWWd/GJ0td7fd/HzZSV/yEDW9EPdZ5n99rTbBSkp
PJcc1/4j3ShSvLNejCsVRAu0g1Thenv96eIRlHGdGq7hDZXnWTqsp0QFRJdYz7i0
3FQg1oD8kXRKG02n3XwlFwLyNo/pPH0veP8FxVlZO+887jFupaFB+XQJgv3le7mp
gzlzclMqHRyxhWU=
=pG+E
-END PGP SIGNATURE-

Bug#860296: [Pkg-lirc-maint] Bug#860296: lirc is spamming syslog with messages

[Alec Leamas]

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.


Hi, thanks for reporting!

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

Bug#860296: lirc is spamming syslog with messages

[Paul Menzel]

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]*
> 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.

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

signature.asc
Description: This is a digitally signed message part

Bug#860296: lirc is spamming syslog with messages

[Hans-J. Ullrich]

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)