Hello,
I don’t know the root of this problem, but I seem to have a module that has either been switched or replaced that is generating a load of error messages in /var/log/nav/cricket/normal.log. The error messages look like this, but I see no information about which device is generating these errors while being polled:
[12-Feb-2009 14:58:39*] Failed to map instance for 4_47. Instance is now set to nothing. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92. Use of uninitialized value in join or string at /usr/share/cricket/lib/snmp.pm line 92.
How can I troubleshoot the root of these error messages if I can't see them in my cricket error log?
------------------------------------------------------ Vidar Stokkenes Networking Consulant Dep. for networking og telecommunications HN IKT - Tromsø
Phone: (+47) 76 16 61 87 or (+47) 77 66 99 55 Cell: 95 87 99 42 e-mail: vidar.stokkenes@hn-ikt.no
Before printing, think about the environment
Hi,
Stokkenes Vidar wrote:
This is Cricket not finding a way to gather data for interface 4_47.
This is seen when a box is down (or the information in cricket-config is incorrect - ip, community etc.), and thus does not reply to snmp-queries.
Another scenario is wrong ifindex for the target "4_47" in the cricket-config/.../<switch>/targets file.
Hard to solve as it mostly occurs because of errors in NAV's database, except of course the netbox is down. To make the logfile more informative you can set $gLogFullPath=1 in cricket-conf.pl. Then you will get e.g. "Switches/Cat4000/core/FastEthernet0_1" instead of just "FastEthernet0_1" in your logs. Perhaps you can track it down easier then.
This is Cricket trying to write debug-information but not having information to do so. Nothing that helps you unfortunately.