Ben Greear wrote: > I'm crawling through xorp logs trying to clean or explain xorp errors. > > Any idea what this indicates? > > [ 2009/10/02 11:21:53 WARNING xorp_rtrmgr:28398 XrlFinderTarget > obj/x86_64-linux-public17/xrl/targets/finder_base.cc:715 > handle_finder_event_notifier_0_1_register_class_event_interest ] Handling > method for finder_event_notifier/0.1/register_class_event_interest failed: > XrlCmdError > 102 Command failed failed to add watch > [ 2009/10/02 11:21:53 ERROR xorp_rtrmgr:28398 RTRMGR > rtrmgr/xrl_rtrmgr_interface.cc:334 finder_register_done ] Failed to register > with finder about XRL > xorpsh-28454-i7-dqc-1 (err: Command failed) >
This could just be xorpsh startup racing with the Router Manager finishing its initial configuration tree pass. > [ 2009/10/02 11:21:53 INFO xorp_rtrmgr:28398 RTRMGR > rtrmgr/module_manager.cc:101 execute ] Executing module: igmp > (mld6igmp/xorp_igmp) > [ 2009/10/02 11:21:53 WARNING xorp_rtrmgr:28398 XrlFinderTarget > obj/x86_64-linux-public17/xrl/targets/finder_base.cc:453 > handle_finder_0_2_resolve_xrl ] > Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command > failed Target "IGMP" does not exist or is not enabled. > [ 2009/10/02 11:21:53 WARNING xorp_rtrmgr:28398 RTRMGR rtrmgr/task.cc:212 > xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 > max_retries: 30 > > > Is this a real error, or just complaints because everything hasn't properly > started yet? > This could be the same situation with the igmp child process. I've seen similar log verbiage when there are debug hooks active in the system. _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
