From: Kay O. <kob...@we...> - 2008-11-06 22:06:44
|
On Thu, 2008-11-06 at 15:42 -0500, Eric Bouliane wrote: > So i've cleared out capsd.log and ran "tail -f capsd.log" and nothing is > coming up in regards to the new node. I've deleted it and added it and > restarted OpenNMS... I've also looked through the collectd.log and > nothing comes up there either. You can also tell the capsd to take action on a node by clicking on "Rescan" within the nodes page in the webUI. I used this many times. In capsd.log you have to find something equivalent for windows like this: 2008-11-06 21:22:23,638 DEBUG [Capsd Rescan Pool-fiber0] RescanProcessor: updateNode: -------dumping old node-------: from database = true node identifier = 2 distributed poller = localhost creation time = 2008-10-19 22:03:39.73 parent identfier = -1 node type = A snmp system oid = .1.3.6.1.4.1.8072.3.2.10 snmp system name = horst snmp system description = Linux horst 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 snmp system location = Somewhere snmp system contact = Donald Duck label = horst.nirwana.all If these values in their both blocks are empty or "null" snmp via snmp4j wasn't successfully on that node regardless of the many things it has read from that node just before during the scan. This is the case with my windows 2000 server. Kay |