zabbix mibs errors

[mulbzh]

Hello,

when i start zabbix server, i have a lot of mibs errors in log, do you think it is normal ?

44918:20160920:093632.192 Starting Zabbix Server. Zabbix 3.0.4 (revision 61185) .
44918:20160920:093632.192 ****** Enabled features ******
44918:20160920:093632.192 SNMP monitoring: YES
44918:20160920:093632.192 IPMI monitoring: YES
44918:20160920:093632.192 Web monitoring: YES
44918:20160920:093632.192 VMware monitoring: YES
44918:20160920:093632.192 SMTP authentication: YES
44918:20160920:093632.192 Jabber notifications: YES
44918:20160920:093632.193 Ez Texting notifications: YES
44918:20160920:093632.193 ODBC: YES
44918:20160920:093632.193 SSH2 support: YES
44918:20160920:093632.193 IPv6 support: YES
44918:20160920:093632.193 TLS support: YES
44918:20160920:093632.193 ******************************
44918:20160920:093632.193 using configuration file: /etc/zabbix/zabbix_server.c onf
44918:20160920:093632.231 current database version (mandatory/optional): 030000 00/03000000
44918:20160920:093632.231 required mandatory version: 03000000
44918:20160920:093632.461 server #0 started [main process]
44921:20160920:093632.464 server #3 started [poller #1]
44920:20160920:093632.464 server #2 started [db watchdog #1]
44922:20160920:093632.465 server #4 started [poller #2]
44923:20160920:093632.470 server #5 started [poller #3]
44919:20160920:093632.474 server #1 started [configuration syncer #1]
44924:20160920:093632.474 server #6 started [poller #4]
44926:20160920:093632.475 server #8 started [unreachable poller #1]
44925:20160920:093632.476 server #7 started [poller #5]
44927:20160920:093632.478 server #9 started [trapper #1]
44928:20160920:093632.480 server #10 started [trapper #2]
44929:20160920:093632.483 server #11 started [trapper #3]
44930:20160920:093632.494 server #12 started [trapper #4]
44932:20160920:093632.496 server #14 started [icmp pinger #1]
44931:20160920:093632.496 server #13 started [trapper #5]
44933:20160920:093632.498 server #15 started [alerter #1]
44934:20160920:093632.500 server #16 started [housekeeper #1]
44935:20160920:093632.502 server #17 started [timer #1]
44938:20160920:093632.512 server #20 started [history syncer #1]
44941:20160920:093632.516 server #23 started [history syncer #4]
44939:20160920:093632.517 server #21 started [history syncer #2]
44940:20160920:093632.517 server #22 started [history syncer #3]
44936:20160920:093632.519 server #18 started [http poller #1]
44947:20160920:093632.556 server #25 started [proxy poller #1]
44948:20160920:093632.584 server #26 started [self-monitoring #1]
44946:20160920:093632.584 server #24 started [escalator #1]
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "::=" (RFC5644): At line 493 in /usr/share/mibs/iana/IANA-IPPM-METRICS- REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
Expected "{" (EOF): At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REGIST RY-MIB
Bad object identifier: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METRICS-REG ISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in /usr/share/mibs/iana/IANA-IPPM-METR ICS-REGISTRY-MIB
44937:20160920:093635.241 server #19 started [discoverer #1]
44918:20160920:093641.625 Got signal [signal:15(SIGTERM),sender_pid:45005,sende r_uid:0,reason:0]. Exiting ...
44918:20160920:093643.627 syncing history data...
44918:20160920:093643.627 syncing history data done
44918:20160920:093643.627 syncing trends data...
44918:20160920:093643.679 syncing trends data done
44918:20160920:093643.680 Zabbix Server stopped. Zabbix 3.0.4 (revision 61185).

thanks

[mulbzh]

ok, i have just uncomment /etc/snmp/snmp.conf mibs like this :

# As the snmp packages come without MIB files due to license reasons, loading
# of MIBs is disabled by default. If you added the MIBs you can reenable
# loading them by commenting out the following line.
#mibs :

[kloczek]

It is not zabbix error.
Parsing MIBs is done by net-snmp libraries. As long as you've registered MIB incorrectly or there are some MIB errors you will be able to see such error logs.