Hi Ben, Here the debug log, but they are strange too because with an snmwalk everything is fine.
*debug log *: *Apr 15 22:56:20 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:20.905Z caller=collector.go:393 level=info auth=cisco_v3 target=* *xx.xx.xx.xx* * module=arte_mib msg="Error scraping target" err="error walking target xx.xx.xx.xx: request timeout (after 3 retries)"Apr 15 22:56:20 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:20.905Z caller=collector.go:464 level=debug auth=cisco_v3 target=* *xx.xx.xx.xx* * module=arte_mib msg="Finished scrape" duration_seconds=20.03805335Apr 15 22:56:21 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:21.907Z caller=collector.go:393 level=info auth=cisco_v3 target=* *yy.yy.yy.yy* * module=arte_mib msg="Error scraping target" err="error walking target yy.yy.yy.yy: request timeout (after 3 retries)"Apr 15 22:56:21 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:21.907Z caller=collector.go:464 level=debug auth=cisco_v3 target=* *yy.yy.yy.yy* * module=arte_mib msg="Finished scrape" duration_seconds=20.083473958Apr 15 22:56:22 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:22.869Z caller=collector.go:460 level=debug auth=cisco_v3 target=ww.ww.ww.ww module=arte_mib msg="Starting scrape"Apr 15 22:56:22 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:22.869Z caller=collector.go:214 level=debug auth=cisco_v3 target=* *ww.ww.ww.ww* *module=arte_mib msg="Walking subtree" oid=1.3.6.1.2.1.1Apr 15 22:56:27 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:27.142Z caller=collector.go:393 level=info auth=cisco_v3 target=zz.zz.zz.zz module=arte_mib msg="Error scraping target" err="error walking target ** zz.zz.zz.zz * *: request timeout (after 3 retries)"Apr 15 22:56:27 prometheus01 snmp_exporter[16444]: ts=2024-04-15T20:56:27.142Z caller=collector.go:464 level=debug auth=cisco_v3 target=* *zz.zz.zz.zz* * module=arte_mib msg="Finished scrape" duration_seconds=20.075515731* *snmpwalk :* *SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software [Cupertino], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.9.4, RELEASE SOFTWARE (fc5)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2023 by Cisco Systems, Inc.Compiled Wed 26-Jul-23 10:26 by mcpreSNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.2494DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (235735378) 27 days, 6:49:13.78SNMPv2-MIB::sysContact.0 = STRING:SNMPv2-MIB::sysName.0 = STRING: swro-arte-strg-data-1.net.globecast.comSNMPv2-MIB::sysLocation.0 = STRING: STRGSNMPv2-MIB::sysServices.0 = INTEGER: 6SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00SNMPv2-MIB::sysORID.1 = OID: SNMPv2-SMI::enterprises.9.7.129SNMPv2-MIB::sysORID.2 = OID: SNMPv2-SMI::enterprises.9.7.115SNMPv2-MIB::sysORID.3 = OID: SNMPv2-SMI::enterprises.9.7.265SNMPv2-MIB::sysORID.4 = OID: SNMPv2-SMI::enterprises.9.7.112SNMPv2-MIB::sysORID.5 = OID: SNMPv2-SMI::enterprises.9.7.106SNMPv2-MIB::sysORID.6 = OID: SNMPv2-SMI::enterprises.9.7.582* ... The snmpwalk response is instantaneous, I don't think it's a scrape_interval and timeout problem. In fact, I've even increased the interval to 1 minute and it doesn't change a thing. I also use tcpdump to see the communication between my equipments and prometheus and everything seems fine : *[~]# tcpdump -i ens192 port 161* *22:43:47.138346 IP prometheus01.com <http://prometheus01.com/>.44170 > swro-arte-strg-data-2.net.com <http://swro-arte-strg-data-2.net.com/>.snmp: F=r U="" E= C="" GetRequest(14)22:43:47.154121 IP swro-arte-strg-data-2.net.com <http://swro-arte-strg-data-2.net.com/>.snmp > prometheus01.com <http://prometheus01.com/>.44170: F= U="" E=_80_00_00_09_03_00_68_e5_9e_a4_00_00 C="" Report(33) S:snmpUsmMIB.usmMIBObjects.usmStats.usmStatsUnknownEngineIDs.0=71669222:43:47.204598 IP prometheus01.com <http://prometheus01.com/>.44170 > swro-arte-strg-data-2.net.com <http://swro-arte-strg-data-2.net.com/>.snmp: F=apr U="supserver" [!scoped PDU]9d_5d_4e_0c_1f_26_92_e6_a6_65_0c_3a_04_b0_8e_f7_66_7d_18_97_3f_5d_84_e2_04....* *......80 packets captured85 packets received by filter0 packets dropped by kernel* Le lundi 15 avril 2024 à 22:41:24 UTC+2, Ben Kochie a écrit : > If you use `snmp_exporter --log.level=debug`, what do the logs say? > > On Mon, Apr 15, 2024 at 10:38 PM Nicolas <[email protected]> wrote: > >> Hello, >> I have a strange error and I hope you can help me, or maybe there is a >> problem with the snmp_exporter generator in the latest version. >> >> I'm using snmp_exporter version 0.25.0 and prometheus >> My generator.yml file looks like this: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *auths: cisco_v3: security_level: authPriv username: secret_name >> password: secret auth_protocol: SHA priv_protocol: AES >> priv_password: secret version: 3modules: arte_mib: walk: - >> 1.3.6.1.2.1.1' - 1.3.6.1.2.1.2.2 - 1.3.6.1.2.1.31.1.1 - >> 1.3.6.1.4.1.9.9.109.1.1.1.1.8 - 1.3.6.1.4.1.9.9.13.1.4 - >> 1.3.6.1.4.1.9.9.13.1.5 - 1.3.6.1.4.1.9.9.48.1.1.1.5 - >> 1.3.6.1.4.1.9.9.48.1.1.1.6 - 1.3.6.1.4.1.9.9.68.1.2.2.1.2* >> >> I generate my snmp.yml file without error: >> >> >> >> *ts=2024-04-15T20:29:38.537Z caller=net_snmp.go:175 level=info >> msg="Loading MIBs" from=/usr/share/snmp/mibs/ts=2024-04-15T20:29:38.577Z >> caller=main.go:53 level=info msg="Generating config for module" >> module=arte_mibts=2024-04-15T20:29:38.580Z caller=main.go:68 level=info >> msg="Generated metrics" module=arte_mib >> metrics=64ts=2024-04-15T20:29:38.585Z caller=main.go:93 level=info >> msg="Config written" >> file=/etc/prometheus/snmp_generator/snmp_exporter-0.25.0/generator/snmp.yml* >> >> And when I push it in my prometheus (conf like this) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> * - job_name: 'arte_snmp' scrape_interval: 1m scrape_timeout: 50s >> file_sd_configs: - files: - >> '/etc/prometheus/targets/arte.json' metrics_path: /snmp params: >> auth: [cisco_v3] module: [arte_mib] relabel_configs: - >> source_labels: [__address__] target_label: instance - >> source_labels: [__address__] target_label: __param_target - >> source_labels: [module] target_label: __param_module - >> target_label: __address__ replacement: 127.0.0.1:9116 >> <http://127.0.0.1:9116> * >> I get a server returned HTTP status 500 Internal Server Error >> [image: 500.PNG] >> >> >> Note that if, for example, I use the if_mib module and take the snmp.yml >> provided in the snmp_exporter, I get no error and my servers appear to be >> UP. >> >> Thanks for your help >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Prometheus Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/prometheus-users/711dd213-92de-4abb-911c-883c0e4535edn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/prometheus-users/711dd213-92de-4abb-911c-883c0e4535edn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/5ebb0504-c2ea-4fd8-bfa6-a118a8e85306n%40googlegroups.com.
