#784968 colord: Logs many snmp-related errors to syslog

Package:
colord
Source:
colord
Description:
system service to manage device colour profiles -- system daemon
Submitter:
Matijs van Zuijlen
Date:
2018-12-02 20:21:05 UTC
Severity:
normal
#784968#5
Date:
2015-05-11 10:17:09 UTC
From:
To:
When inserting or removing USB devices, colord logs a lot of messages similar
to those below to syslog. Some investigation suggests that it is caused
indirectly by the resolution of #782598. I could install
snmp-mibs-downloader as suggested here[0], but I don't think I should
need to install any non-free files to resolve this.

May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskAvailHigh ::= { dskEntry 14 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskAvailLow ::= { dskEntry 13 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskTotalHigh ::= { dskEntry 12 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskTotalLow ::= { dskEntry 11 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskPercentNode ::= { dskEntry 10 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskPercent ::= { dskEntry 9 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskUsed ::= { dskEntry 8 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskAvail ::= { dskEntry 7 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskTotal ::= { dskEntry 6 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskMinPercent ::= { dskEntry 5 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskMinimum ::= { dskEntry 4 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskDevice ::= { dskEntry 3 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskPath ::= { dskEntry 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: dskIndex ::= { dskEntry 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-DISKIO-MIB: diskIOTable ::= { ucdDiskIOMIB 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLoggingGroup ::= { nsConfigGroups 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsDebugGroup ::= { nsConfigGroups 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: snmperrErrMessage ::= { snmperrs 101 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: snmperrErrorFlag ::= { snmperrs 100 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: snmperrNames ::= { snmperrs 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: snmperrIndex ::= { snmperrs 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsTransactionTable ::= { nsTransactions 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLogStatus ::= { nsLoggingEntry 5 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLogMaxLevel ::= { nsLoggingEntry 4 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLogType ::= { nsLoggingEntry 3 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLogToken ::= { nsLoggingEntry 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsLogLevel ::= { nsLoggingEntry 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendResult ::= { nsExtendOutput1Entry 4 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutNumLines ::= { nsExtendOutput1Entry 3 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutputFull ::= { nsExtendOutput1Entry 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutput1Line ::= { nsExtendOutput1Entry 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendOutLine ::= { nsExtendOutput2Entry 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-EXTEND-MIB: nsExtendLineIndex ::= { nsExtendOutput2Entry 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyStart ::= { netSnmpNotifications 1 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyShutdown ::= { netSnmpNotifications 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyRestart ::= { netSnmpNotifications 3 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laErrMessage ::= { laEntry 101 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laConfig ::= { laEntry 4 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laLoad ::= { laEntry 3 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laNames ::= { laEntry 2 }
May 11 11:56:52 walnut colord[997]: Cannot adopt OID in UCD-SNMP-MIB: laIndex ::= { laEntry 1 }

[0]: http://serverfault.com/questions/440285/why-does-snmp-fail-to-use-its-own-mibs
#784968#10
Date:
2018-12-02 20:17:30 UTC
From:
To:
Filing bugs against colord is currently disabled at
<https://bugs.freedesktop.org/enter_bug.cgi?product=colord>
and it's not listed either in freedesktop's gitlab instance at <https://gitlab.freedesktop.org>.

So for people desperate to get these warnings off their journals, you can limit the daemon's
logging level to errors only. Use 'systemctl edit colord' to create an override for colord:


[Service]
# colord spams the system log with 'Cannot adopt OID in ...' messages
# whenever a disk is plugged-in or out. see debian bug #784968
LogLevelMax=err