Re: [ros-users] socket-related error

Top Page
Attachments:
Message as email
+ (text/plain)
+ grasping_service-1.log (text/x-log)
Delete this message
Reply to this message
Author: User discussions
Date:  
To: ros-users
Subject: Re: [ros-users] socket-related error
Full log file attached.
Thanks,
Mike

Author: Ken Conley
Date: 2011-01-12 19:04 -800
To: User discussions
Subject: Re: [ros-users] socket-related error
Hi Mike,

Nothing immediately comes to mind, though looking back at the logs you
sent I think it may actually be missing the original error. Can you
provide a complete log file somewhere?

thanks,
Ken

On Wed, Jan 12, 2011 at 12:11 PM, Michael Krainin
<> wrote:
> Also possibly relevant is that I recently upgraded both machines to
> Ubuntu 10.10 and also switched the second machine over to the ROS
> Ubuntu packages instead of SVN. What were essentially the same nodes
> worked before these changes.
>
> -Mike
>
>
> Author: Michael Krainin
> Date: 2011-01-12 12:04 -800
> To: ros-users
> Subject: Re: [ros-users] socket-related error
> Hi Ken,
>
> The node on the second machine provides a service for computing
> grasps. Upon receiving a request, it looks up the camera pose using a
> tf TransformListener. It then calls a service on the first machine
> which provides it with the table parameters, a point cloud of the
> object to be grasped, and a point cloud of any obstacles on the table.
> It then adds the points as a mesh into an openrave environment and
> begins trying potential grasps.
>
> It's around here that I get the error, though it's not always exactly
> at the same point. Were it to continue, the node would eventually
> select a grasp, plan a trajectory, and finally call a service back on
> the first machine to run the trajectory.
>
> -Mike
>
>
> Author: Ken Conley
> Date: 2011-01-12 11:352011-01-12 19:35 -800UTC
> To: User discussions
> Subject: Re: [ros-users] socket-related error
> Hi Michael,
>
> Can you describe more about the node on the second machine. The only
> time I can recall seeing this was when rospy was coupled with Twisted,
> which uses signals.
>
> - Ken
>
> On Wed, Jan 12, 2011 at 11:31 AM, Michael Krainin
> <> wrote:
>> Hi,
>>
>> I'm running into an error that I'm not sure how to fix and was wondering if
>> anyone might have some insight into what's going wrong.
>>
>> I have roscore and a few nodes running on one machine. Then on a second
>> machine is a node which interacts with nodes on the first machine through
>> service calls. Everything seems to run fine for a while, then the node on
>> the second machine dies with a message:
>>
>> Unhandled exception in thread started by <bound method TCPServer.run of
>> <rospy.impl.tcpros_base.TCPServer object at 0x2fee1d0>>
>> Traceback (most recent call last):
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 141, in run
>>     (client_sock, client_addr) = self.server_sock.accept()
>>   File "/usr/lib/python2.6/socket.py", line 197, in accept
>>     sock, addr = self._sock.accept()
>> socket.error: [Errno 4] Interrupted system call

>>
>> Additionally, the log for this node includes the following messages:
>>
>> [INFO] 2011-01-12 10:43:14,691: signal_shutdown [error in XML-RPC server]
>> [ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 593, in receive_once
>>     recv_buff(sock, b, p.buff_size)
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 93, in recv_buff
>>     d = sock.recv(buff_size)
>> error: [Errno 4] Interrupted system call

>>
>> [ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 593, in receive_once
>>     recv_buff(sock, b, p.buff_size)
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 93, in recv_buff
>>     d = sock.recv(buff_size)
>> error: [Errno 4] Interrupted system call

>>
>> [ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 593, in receive_once
>>     recv_buff(sock, b, p.buff_size)
>>   File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line
>> 93, in recv_buff
>>     d = sock.recv(buff_size)
>> error: [Errno 4] Interrupted system call

>>
>> [INFO] 2011-01-12 10:43:14,739: error in XML-RPC server
>> [INFO] 2011-01-12 10:43:16,010: signal_shutdown [atexit]
>>
>> Any thoughts on where the problem might lie?
>>
>> Thanks,
>> Mike
>>
>> _______________________________________________
>> ros-users mailing list
>>
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
> _______________________________________________
> ros-users mailing list
>
> https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
>
> https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
>
> https://code.ros.org/mailman/listinfo/ros-users
>

_______________________________________________
ros-users mailing list

https://code.ros.org/mailman/listinfo/ros-users
[INFO] 2011-01-12 10:39:16,330: init_node, name[/grasping_service], pid[3294]
[INFO] 2011-01-12 10:39:16,331: Node initialized: callerId[/grasping_service] local name[grasping_service] port[None]
[INFO] 2011-01-12 10:39:16,331: XML-RPC server binding to 0.0.0.0
[INFO] 2011-01-12 10:39:16,331: Started XML-RPC server [http://pr-seattle-1:40961/]
[INFO] 2011-01-12 10:39:16,331: ROS Slave URI: [http://pr-seattle-1:40961/]
[INFO] 2011-01-12 10:39:16,332: _ready: http://pr-seattle-1:40961/
[INFO] 2011-01-12 10:39:16,336: Registering with master node http://marvin:11311
[INFO] 2011-01-12 10:39:16,336: xml rpc node: starting XML-RPC server
[INFO] 2011-01-12 10:39:16,432: registered with master
[INFO] 2011-01-12 10:39:16,441: initializing /rosout core topic
[INFO] 2011-01-12 10:39:16,451: connected to core topic /rosout
[INFO] 2011-01-12 10:39:16,454: /use_sim_time is not set, will not subscribe to simulated time [/clock] topic
[INFO] 2011-01-12 10:43:13,783: Received grasp request
[INFO] 2011-01-12 10:43:13,883: waiting for segmentation service
[INFO] 2011-01-12 10:43:14,663: Got plane params: -0.043115, -0.021448, 0.998840, 0.376473
[INFO] 2011-01-12 10:43:14,664: Got 'object' cloud with 4459 points
[INFO] 2011-01-12 10:43:14,664: Got 'on table' cloud with 4479 points
[INFO] 2011-01-12 10:43:14,691: signal_shutdown [error in XML-RPC server]
[ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 593, in receive_once
    recv_buff(sock, b, p.buff_size)
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 93, in recv_buff
    d = sock.recv(buff_size)
error: [Errno 4] Interrupted system call


[ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 593, in receive_once
    recv_buff(sock, b, p.buff_size)
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 93, in recv_buff
    d = sock.recv(buff_size)
error: [Errno 4] Interrupted system call


[ERROR] 2011-01-12 10:43:14,692: Traceback (most recent call last):
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 593, in receive_once
    recv_buff(sock, b, p.buff_size)
  File "/opt/ros/cturtle/ros/core/rospy/src/rospy/impl/tcpros_base.py", line 93, in recv_buff
    d = sock.recv(buff_size)
error: [Errno 4] Interrupted system call


[INFO] 2011-01-12 10:43:14,739: error in XML-RPC server
[INFO] 2011-01-12 10:43:16,010: signal_shutdown [atexit]