[Xorp-users] Error writing to routing socket: No such process

Wed Jul 28 12:44:04 PDT 2010

On Jul 28, 2010, at 9:35 PM, Ben Greear wrote:

> On 07/28/2010 12:18 PM, Edwin Schokkenbroek wrote:
>> Hello Ben,
>> 
>> Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier.
>> 
>> 010/07/28 21:07:59  ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR"
>> [ 2010/07/28 21:07:59  ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket.  Path: /var/tmp/xrl.cwKcRV.  Error: Permission denied
>> [ 2010/07/28 21:07:59  ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV
>> 
>> (These messages are going on forever.)
>> 
>> The message is clear, and easy to explain,  xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges.
>> When I change the ownership of the file in /var/tmp I'm able to login.
>> 
>> But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root.
>> 
>> Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started.
> 
> I could add an option to create the /var/tmp/ file as read/write by everyone (or maybe
> just the xorp group), I suppose.

I think a xorp group is the most clean way . read/write everyone could maybe introduce a security issue ?

The dir /var/tmp is already world writeable permissions (on my system): 

drwxrwxrwt  3 beheer  wheel  2048 Jul 28 21:27 /var/tmp/

> 
> One thing I just noticed:  I have 126,000 or so xrl files in /var/tmp/
> on one of my test machines.
> 
> That can't be good :P

Nope....  hopefully the filesystem has enough inodes ;-)
> 
> Aside from the permissions issue, does xorp.ct fix that other bug you reported?

Well I managed to start one xopr_rtmgr in a vimage,  however the other xorp_rtr_mgr seems to hang. 

I recieve a lot of messages : 

Not doing pidfile...
[ 2010/07/28 21:26:48.671719  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/master_conf_tree.cc:234 execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, ospf4
[ 2010/07/28 21:26:48.673113  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:327 startup_validation ] WARNING:  Using DelayValidation, module_name: rtrmgr
[ 2010/07/28 21:26:48.673178  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:348 config_validation ] WARNING:  Using DelayValidation, module_name: rtrmgr
[ 2010/07/28 21:26:48.673971  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:369 ready_validation ] WARNING:  Using DelayValidation, module_name: rtrmgr
[ 2010/07/28 21:26:48.674057  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: interfaces (xorp_fea)
[ 2010/07/28 21:26:48.678313  WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fea" does not exist or is not enabled.
[ 2010/07/28 21:26:48.679305  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed  retries: 0  max_retries: 30
[ 2010/07/28 21:26:49.710205  INFO xorp_fea:2274 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled
[ 2010/07/28 21:26:49.710685  INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled
[ 2010/07/28 21:26:49.712299  INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:92 start ] CLI started
[ 2010/07/28 21:26:49.712464  INFO xorp_fea:2274 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled
[ 2010/07/28 21:26:49.712543  INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled
[ 2010/07/28 21:26:49.713527  INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:92 start ] CLI started
[ 2010/07/28 21:26:49.751207  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rtrmgr ()
[ 2010/07/28 21:26:55.811914  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: firewall (xorp_fea)
[ 2010/07/28 21:26:55.815042  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: fea (xorp_fea)
[ 2010/07/28 21:26:55.815764  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rib (xorp_rib)
[ 2010/07/28 21:26:55.828681  WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled.
[ 2010/07/28 21:26:55.829153  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed  retries: 0  max_retries: 30
[ 2010/07/28 21:26:56.865792  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: policy (xorp_policy)
[ 2010/07/28 21:26:56.868770  WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "policy" does not exist or is not enabled.
[ 2010/07/28 21:26:56.869172  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed  retries: 0  max_retries: 30
[ 2010/07/28 21:26:57.905775  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: ospf4 (xorp_ospfv2)
[ 2010/07/28 21:26:57.908040  WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv2" does not exist or is not enabled.
[ 2010/07/28 21:26:57.908473  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed  retries: 0  max_retries: 30
[ 2010/07/28 21:27:24.210672  WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 20.414893 seconds
[ 2010/07/28 21:27:24.210784  WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 18.395036 seconds
[ 2010/07/28 21:27:24.210896  WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 17.345121 seconds
[ 2010/07/28 21:27:24.211157  WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 16.305401 seconds
[ 2010/07/28 21:27:24.211476  WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 25.303181 seconds
[ 2010/07/28 21:27:24.212195  WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled.
[ 2010/07/28 21:27:24.212371  WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed  retries: 1  max_retries: 30
[ 2010/07/28 21:27:24.389087  WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:948 updates_made ] XrlIO<IPv4>::updates_made, _iftree:
[ 2010/07/28 21:27:25.251905  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1  dbg: create_peer  vif: epair3b/epair3b  old-status: 0
[ 2010/07/28 21:27:25.251984  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3b/epair3b  running: 0  status: 0  link-status: 1
[ 2010/07/28 21:27:25.260140  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3b/epair3b  running: 0  status: 1  link-status: 1
[ 2010/07/28 21:27:25.260297  WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair3b Vif epair3b
[ 2010/07/28 21:27:25.263083  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1  dbg: create_peer  vif: epair2b/epair2b  old-status: 0
[ 2010/07/28 21:27:25.263159  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair2b/epair2b  running: 0  status: 0  link-status: 1
[ 2010/07/28 21:27:25.271045  WARNING xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:230 IoIpSocket ] Registering with iftree: pushed-config
[ 2010/07/28 21:27:25.272803  INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3b vif epair3b  socket: 43
[ 2010/07/28 21:27:25.274128  WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair2b/epair2b  running: 0  status: 1  link-status: 1
[ 2010/07/28 21:27:25.274128  WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair2b Vif epair2b
[ 2010/07/28 21:27:25.274721  INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair2b vif epair2b  socket: 43
[ 2010/07/28 21:27:25.277490  INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run
Welcome to XORP on router3
beheer at router3> [ 2010/07/28 21:27:34.966123  INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair2b vif epair2b  socket: 43
[ 2010/07/28 21:28:05.280182  INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair3b vif epair3b  socket: 43

Maybe I did something wrong installing xorp ? or is xorp.ct not compatible with the configuration file ?

> 
> Thanks,
> Ben
> 
> -- 
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 

Edwin Schokkenbroek
edwin at spacebugs.nl

Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble.