[Xorp-users] Some recent xorp.ct improvements. (Ben Greear)
Edwin Schokkenbroek
edwin at spacebugs.nl
Tue Aug 17 13:00:22 PDT 2010
On Aug 17, 2010, at 9:15 PM, Edwin Schokkenbroek wrote:
>
> On Aug 17, 2010, at 8:28 PM, Edwin Schokkenbroek wrote:
>
>>
>> On Aug 17, 2010, at 6:14 PM, Ben Greear wrote:
>>
>>> On 08/17/2010 08:10 AM, Edwin Schokkenbroek wrote:
>>>>
>>>> On Aug 17, 2010, at 5:03 PM, Ben Greear wrote:
>>>>
>>>>> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote:
>>>>>> Hello Ben,
>>>>>>
>>>>>> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources:
>>>>>>
>>>>>> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot
>>>>>> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536.
>>>>>> Abort trap: 6 (core dumped)
>>>>>
>>>>> Thanks for testing. I must have messed up the endian-ness stuff I did last night.
>>>>>
>>>>> Can you check to see if you have<endian.h> on your compile system?
>>>
>>> Can you try the latest xorp.ct please? I think I have a fix in place
>>> now.
>>
>> Compiled the latest source and I was able to start xorp_rtrmgr again :-) BGP and OSPF seems to work fine to. Thanks !
>>
>> Edwin
>>
>
> Maybe I was to enthusiast I tested with a wrong version .. sorry about that. What I noticed is now that I use the latest compiled version, that I receive messages like:
>
> [ 2010/08/17 21:01:01 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused
> [ 2010/08/17 21:01:01 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused
> Waiting for xorp_rtrmgr...
> [ 2010/08/17 21:01:10 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused
> [ 2010/08/17 21:01:10 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused
>
>
> Which tells me the xorp_rtrmgr is not started (or failed to start) for some reason.
>
> I start the xorp_rtrmgr from a script, and when I start the xorp_rtrmgr manual (from the command line) with the same config file .. the xorp_rtrmgr just starts. When I use the xorp version builds from the ports of FreeBSD (and earlier builds of xorp.ct) it just works .. as in I can start xorp_rtrmgr from my script.
>
> Don't know what is causing this. I'm searching at this moment. Hopefully a log file will tell me what is going on....
>
> Edwin
>
>
Hmm not sure what is going on ... If I look in the log file I see the following messages:
[ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address
[ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder may already be running.
Some extra information:
> beastie# jexec R10 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R10/boot/config.boot -P /xorp_rtrmgr.pid -d[ 2010/08/17 21:54:31.401294 ERROR xorp_rtrmgr:3783 LIBCOMM libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address
> [ 2010/08/17 21:54:31.403459 ERROR xorp_rtrmgr:3783 RTRMGR rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder may already be running.
> beastie#
When activating a shell in the jail R10:
beastie# jexec R10 bash
[root at R10 /]# ps ax
PID TT STAT TIME COMMAND
3800 2 SJ 0:00.02 bash
3801 2 R+J 0:00.00 ps ax
[root at R10 /]#
root at R10 /]# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
epair1b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:00:00:00:07:0b
inet 10.1.100.2 netmask 0xfffffffc broadcast 10.1.100.3
inet6 fe80::ff:fe00:70b%epair1b prefixlen 64 scopeid 0x2
epair4b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:00:00:00:07:0b
inet 10.1.100.14 netmask 0xfffffffc broadcast 10.1.100.15
inet6 fe80::ff:fe00:70b%epair4b prefixlen 64 scopeid 0x3
ebr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:16:3e:a0:b9:ef
inet6 fe80::30df:7d55:41bc:941%ebr0 prefixlen 64 scopeid 0x4
inet 10.1.3.10 netmask 0xffffff00 broadcast 10.1.3.255
ebr1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
When I start Xorp (build from the ports) :
beastie# jexec R10 /usr/local/bin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R10/boot/config.boot -P /xorp_rtrmgr.pid -d
[ 2010/08/17 21:57:14 INFO xorp_rtrmgr:3803 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, bgp, ospf4
[ 2010/08/17 21:57:14 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea)
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI enabled
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI started
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI enabled
[ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI started
[ 2010/08/17 21:57:16 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: rtrmgr ()
[ 2010/08/17 21:57:23 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea)
[ 2010/08/17 21:57:27 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
[ 2010/08/17 21:57:31 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib)
[ 2010/08/17 21:57:33 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: policy (policy/xorp_policy)
[ 2010/08/17 21:57:35 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: bgp (bgp/xorp_bgp)
[ 2010/08/17 21:57:39 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: ospf4 (ospf/xorp_ospfv2)
[ 2010/08/17 21:57:41 INFO xorp_rtrmgr:3803 RTRMGR +2233 task.cc run_task ] No more tasks to run
In the jail xorp_rtrmgr is running :
beastie# jexec R10 bash
[root at R10 /]# ps ax
PID TT STAT TIME COMMAND
3809 ?? SsJ 0:00.16 /usr/local/bin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R
3804 2 SJ 0:01.21 xorp_fea
3805 2 SJ 0:00.30 xorp_rib
3806 2 SJ 0:00.09 xorp_policy
3807 2 SJ 0:00.53 xorp_bgp
3808 2 SJ 0:00.34 xorp_ospfv2
3810 2 SJ 0:00.06 bash
3811 2 R+J 0:00.00 ps ax
Edwin
>
>
>
>
>
>
>
>
>
>>>
>>> I need to get my BSD system in build-bot, and then will see if I can get
>>> BSD to use <sys/endian.h> so we don't depend on the scons CheckEndian logic,
>>> which is broken for cross-compiles.
>>>
>>> Thanks,
>>> Ben
>>>
>>> --
>>> Ben Greear <greearb at candelatech.com>
>>> Candela Technologies Inc http://www.candelatech.com
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100817/c32a49fd/attachment-0001.html
More information about the Xorp-users
mailing list