[Xorp-users] xorpsh/resolver issue

[Pavlin Radoslavov]

> It still appears I am getting these errors during make check in the
> CVS repository code. I have also upgraded default gcc 2.9.x to
> 3.3 via ports to see if it was due to a compiler bug.
> 
> [ 2004/11/25 16:40:31 WARNING test_lemming XrlFinderTarget ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
> [ 2004/11/25 16:40:31 WARNING test_lemming XrlFinderTarget ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
> [ 2004/11/25 16:40:31 WARNING test_lemming XrlFinderTarget ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
> [ 2004/11/25 16:40:32 WARNING test_lemming XrlFinderTarget ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
> 
> What does "Xrl target is not enabled" mean? I am willing to go further
> and gather as much information and investigations as I can.

James,

As Bruce mentioned in his email, sometimes those messages are
harmless. E.g., in case of running libxipc/test_lemming I think they
are part of the test so if the return value from the test is 0 then
the test has succeeded.

Further, you may see similar messages during startup of the rtrmgr.
After the rtrmgr starts a XORP process, the rtrmgr uses periodic
XRLs to verify the status of the process. If the process hasn't
started yet, the first 1-2 XRLs may trigger the "Xrl target is not
enabled" warning message.

For example, I used the following simple configuration file on
Fedora Core2:

interfaces {
    interface eth0 {
        default-system-config
    }
}

When I start the rtrmgr, I see the following messages, which are normal:

root@fedora[2] ./xorp_rtrmgr -b ~/xorp/rtrmgr/foo3.boot 
[ 2004/11/27 10:24:35  INFO xorp_rtrmgr:11288 RTRMGR +134 /home/vmware/pavlin/xorp/rtrmgr/master_conf_tree.cc execute ] Changed modules: interfaces
[ 2004/11/27 10:24:35  INFO xorp_rtrmgr:11288 RTRMGR +404 /home/vmware/pavlin/xorp/rtrmgr/module_manager.cc run ] Running module: interfaces (/home/vmware/pavlin/work/xorp/build/fedora/fea/xorp_fea)
[ 2004/11/27 10:24:37  WARNING xorp_rtrmgr:11288 XrlFinderTarget +406 /home/vmware/pavlin/xorp/libxipc/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
[ 2004/11/27 10:24:39  INFO xorp_rtrmgr:11288 RTRMGR +1372 /home/vmware/pavlin/xorp/rtrmgr/task.cc run_task ] No more tasks to run

Also, FYI, I didn't have problem with using configure mode in
xorpsh:

pavlin@fedora[14] ./xorpsh
Welcome to XORP on fedora
Xorp> configure 
Entering configuration mode.
There are no other users in configuration mode.
[edit]
XORP> 


I tried same test on FreeBSD-4.10 and RedHat-7.3, and the
results were similar.

Could you try a similar test on your machine (don't forget to change
eth0 in the config file to the name of one of the configured
interfaces) and then send the rtrmgr log message.
The "configure" problem is probably unrelated and should be tracked
independently.

Thanks,
Pavlin