FW: [Xorp-users] XORP 1.1RC Install under OpenBSD 3.6

Pavlin Radoslavov pavlin@icir.org
Mon, 18 Apr 2005 13:56:05 -0700


> 1.) Ok, I've installed the g++-3.3.2.tgz package as you suggested and
> ran the (gmake clean) and then reran the (./configure), (gmake) and
> (gmake check) and this time it appears to have finished compiling... But
> looking through the logs for the (gmake check) I noticed there were a
> few warnings and errors like;
> 
> [ 2005/04/15 10:22:21 WARNING test_lemming XrlFinderTarget ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Xrl target is not enabled.
> 
> [ 2005/04/15 10:22:21 ERROR test_lemming XRL ] NO FINDER
> [ 2005/04/15 10:22:22 ERROR test_lemming XRL ] NO FINDER
> [ 2005/04/15 10:22:22 ERROR test_lemming XRL ] NO FINDER
> [ 2005/04/15 10:23:17 WARNING test_finder_events FINDER ] ready is 1 not
> zero
> [ 2005/04/15 10:23:22 WARNING test_finder_events FINDER ] ready is 2 not
> zero
> 
> [ 2005/04/15 10:26:18  WARNING test_spt:5097 LIBPROTO +254 spt.cc
> dijkstra ] No origin
> [ 2005/04/15 10:26:18  WARNING test_spt:5097 LIBPROTO +505 spt.cc delta
> ] Node: z not reachable
> 
> [ 2005/04/15 10:27:00  WARNING test_generated:21353 XrlTestTarget +326
> test_base.cc handle_test_1_0_shoot_foot ] Handling method for
> test/1.0/shoot_foot failed: XrlCmdError 102 Command failed no gun to
> shoot foot with.
> 
> [ 2005/04/15 10:34:05 WARNING test_rib_xrls XrlFinderTarget ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Target "fea" does not exist or is not enabled.
> 
> SIGTERM received. Exiting.
> [ 2005/04/15 11:11:31  ERROR xorp_finder:22089 LIBXORP +272 asyncio.cc
> complete_transfer ] Write error 32 - Broken pipe

Those messages are OK during the "gmake check". Some of the tests
try different test scenarios, and some of those scenarios trigger
error conditions on purpose. The test exit value is important, so if
you don't see "FAIL: <test name>" while running "gmake check", then
things should be OK. I looked into your attached "gmake check" log
message, and things seem fine.

> 2.) Once the (gmake check) was complete I then tailed the /etc/passwd
> file to see of the install script added the user and group xorp and then
> noticed that the account wasn't one added, is this an indicator that
> XORP was fully installed/compiled...? I added the user and group account
> using the adduser command...

Yes, the install script doesn't try to add automatically any users
or groups, so you would have to do it by hand.

> 3.) If I run the /xorp_rtrmgr -b config.boot under the
> /xorp/xorp-1.1-RC/rtrmgr/ directory this is the out put from runing this
> command;
> 
> bash-3.00# ./xorp_rtrmgr -b config.boot
> [ 2005/04/18 09:51:08  INFO xorp_rtrmgr:6663 RTRMGR +170
> master_conf_tree.cc execute ] Changed modules: interfaces
> [ 2005/04/18 09:51:08  INFO xorp_rtrmgr:6663 RTRMGR +404
> module_manager.cc run ] Running module: interfaces
> (/xorp/xorp-1.1-RC/fea/xorp_fea)
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.
> [ 2005/04/18 09:51:08  ERROR xorp_fea:26966 FEA +405
> routing_socket_utils.cc rtm_get_to_fte_cfg ] Cannot map a discard route
> back to an FEA soft discard interface.

You can ignore the above error messages, because they are harmless.
Anyway, this should be fixed for the next release.

> [ 2005/04/18 09:51:09 INFO xorp_fea CLI ] CLI enabled
> [ 2005/04/18 09:51:09 INFO xorp_fea CLI ] CLI started
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] MFEA enabled
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] CLI enabled
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] CLI started
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] MFEA enabled
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] CLI enabled
> [ 2005/04/18 09:51:09 INFO xorp_fea MFEA ] CLI started
> [ 2005/04/18 09:51:10  ERROR xorp_fea:26966 FEA +93 ifconfig_set.cc
> push_config ] On faith0: interface not recognized
> [ 2005/04/18 09:51:10 WARNING xorp_fea XrlFeaTarget ] Handling method
> for ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed
> On faith0: interface not recognized
> [ 2005/04/18 09:51:10  ERROR xorp_rtrmgr:6663 RTRMGR +597
> master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command
> failed On faith0: interface not recognized

It looks like you are trying to configure interface faith0 inside
XORP. If you don't need to use that interface by XORP, then I'd
recommend to exclude it from the XORP configuration. This applies
for all other interfaces.
If you really need to use faith0, then please send me your XORP
config file and the output of "ifconfig faith0" and I will have a
look.

> [ 2005/04/18 09:51:10  ERROR xorp_rtrmgr:6663 RTRMGR +182
> master_conf_tree.cc config_done ] Configuration failed: 102 Command
> failed On faith0: interface not recognized
> [ 2005/04/18 09:51:10  INFO xorp_rtrmgr:6663 RTRMGR +1420 task.cc
> run_task ] No more tasks to run
> [ 2005/04/18 09:51:10  INFO xorp_rtrmgr:6663 RTRMGR +216
> module_manager.cc terminate ] Terminating module: interfaces
> [ 2005/04/18 09:51:10  INFO xorp_rtrmgr:6663 RTRMGR +262
> module_manager.cc terminate ] Killing module: interfaces (pid =3D 26966)
> [ 2005/04/18 09:51:10  INFO xorp_rtrmgr:6663 RTRMGR +547
> module_manager.cc killed ] Module killed during shutdown: interfaces
> 
> 4.) If I try to run the ./xorpsh command, this is the out put from that
> command
> 
> bash-3.00# ./xorpsh=20
> [ 2005/04/18 09:55:52  ERROR xorpsh:28069 LIBCOMM +499 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family =3D 2, remote_addr =
> =3D
> 127.0.0.1, remote_port =3D 19999): Connection refused
> [ 2005/04/18 09:55:52  ERROR xorpsh:28069 FINDER +370
> finder_tcp_messenger.cc do_auto_connect ] Failed to connect to
> 127.0.0.1/19999: Connection refused
> [ 2005/04/18 09:55:52  ERROR xorpsh:28069 LIBCOMM +499 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family =3D 2, remote_addr =
> =3D
> 127.0.0.1, remote_port =3D 19999): Connection refused
> [ 2005/04/18 09:55:52  ERROR xorpsh:28069 LIBCOMM +499 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family =3D 2, remote_addr =
> =3D
> 127.0.0.1, remote_port =3D 19999): Connection refused
> [ 2005/04/18 09:55:52  ERROR xorpsh:28069 LIBCOMM +499 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family =3D 2, remote_addr =
> =3D
> 127.0.0.1, remote_port =3D 19999): Connection refused
> [ 2005/04/18 09:55:53  ERROR xorpsh:28069 LIBCOMM +499 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family =3D 2, remote_addr =
> =3D
> 127.0.0.1, remote_port =3D 19999): Connection refused

If the rtrmgr fails, then you cannot use xorpsh.

Regards,
Pavlin