All
In the past two months I have seen this problem more and more. It seems to
affect my windows nodes more than the mac ones. Below is the VenueClient logs
from one of our nodes. Is there a solution to this? We are using 3.02 with XP.
any help would be appreciated.
Thanks
Paul
Venue Client log
12/05/07 16:13:01 3716 VenueClient venueclient.py:477 ERROR Error sending
heartbeat; next heartbeat in 30s
Traceback (most recent call last):
File "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\VenueClient.py",
line 457, in Heartbeat
nextTimeout = self.__venueProxy.UpdateLifetime(
File
"C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\interfaces\Venue_client.py",
line 254, in UpdateLifetime
self.binding.Send(None, None, request, soapaction="urn:#UpdateLifetime",
**kw)
File "C:\Python23\lib\site-packages\ZSI\client.py", line 254, in Send
self.h.connect()
File "C:\Python23\lib\httplib.py", line 987, in connect
sock.connect((self.host, self.port))
File "<string>", line 1, in connect
error: (10060, 'Operation timed out')
12/05/07 16:13:31 2336 VenueClient venueclient.py:450 DEBUG Calling
Heartbeat, time now: 1196903611
12/05/07 16:13:52 2336 VenueClient venueclient.py:477 ERROR Error sending
heartbeat; next heartbeat in 30s
Traceback (most recent call last):
File "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\VenueClient.py",
line 457, in Heartbeat
nextTimeout = self.__venueProxy.UpdateLifetime(
File
"C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\interfaces\Venue_client.py",
line 254, in UpdateLifetime
self.binding.Send(None, None, request, soapaction="urn:#UpdateLifetime",
**kw)
File "C:\Python23\lib\site-packages\ZSI\client.py", line 254, in Send
self.h.connect()
File "C:\Python23\lib\httplib.py", line 987, in connect
sock.connect((self.host, self.port))
File "<string>", line 1, in connect
error: (10060, 'Operation timed out')
12/05/07 16:14:16 2868 VenueClient venueclient.py:561 DEBUG
RemoveUserEvent: Got Remove User Event
12/05/07 16:14:16 2868 VenueClient venueclient.py:1132 INFO ExitVenue
12/05/07 16:14:16 2868 VenueClient venueclient.py:1103 DEBUG ExitVenue:
Stop event client obj
12/05/07 16:14:16 2868 VenueClient venueclient.py:1105 DEBUG ExitVenue:
Remove event client reference
12/05/07 16:14:16 2868 VenueClient venueclient.py:1110 INFO ExitVenue:
Stopping text client
12/05/07 16:14:16 2868 JabberClient jabberclient.py:73 DEBUG Sending the
presence to
'Remote-Control-Device-1(agserver.arsc.edu)@conference.mcs.anl.gov/WRRB Shuttle
Node' of type 'unavailable'...
12/05/07 16:14:16 2868 bajjer.io io.py:122 DEBUG SEND: <presence
to="Remote-Control-Device-1(agserver.arsc.edu)@conference.mcs.anl.gov/WRRB
Shuttle Node" type="unavailable"><x /></presence>
12/05/07 16:14:16 2868 RTPBeacon rtpbeacon.py:296 DEBUG Called Stop.
12/05/07 16:14:16 2868 EventClient insecurevenueeventclient.py:77 INFO
BaseVenueEventClient lost connection.
12/05/07 16:14:16 3980 bajjer.io io.py:161 DEBUG RECV: <presence
to='c7a550e509785d73b6915968a3240...@jabber.mcs.anl.gov/default'
type='unavailable'
from='remote-control-device-1(agserver.arsc.edu)@conference.mcs.anl.gov/WRRB
Shuttle Node'><x/><x xmlns='http://jabber.org/protocol/muc#user'><item
affiliation='none' role='none'/></x></presence>
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:72 DEBUG start
<{jabber:client}presence> level=1
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:72 DEBUG start
<{jabber:client}x> level=2
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:86 DEBUG end
<{jabber:client}x> level=2
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:72 DEBUG start
<{http://jabber.org/protocol/muc#user}x> level=2
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:72 DEBUG start
<{http://jabber.org/protocol/muc#user}item> level=3
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:86 DEBUG end
<{http://jabber.org/protocol/muc#user}item> level=3
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:86 DEBUG end
<{http://jabber.org/protocol/muc#user}x> level=2
12/05/07 16:14:16 3980 bajjer.serialize serialize.py:86 DEBUG end
<{jabber:client}presence> level=1
12/05/07 16:14:16 3980 JabberClient jabberclient.py:148 DEBUG
remote-control-device-1(agserver.arsc.edu)@conference.mcs.anl.gov/WRRB Shuttle
Node is unavailable (None / None)
12/05/07 16:14:16 2868 VenueClient venueclientui.py:3349 DEBUG
ContentListPanel.RemoveParticipant: Remove participant
12/05/07 16:14:16 3980 VenueClient venueclientui.py:2322 DEBUG remove
user: WRRB Shuttle Node
12/05/07 16:14:16 1368 RTPBeacon rtpbeacon.py:289 INFO
RTPBeacon.UpdateThread exiting
On Oct 19, 2007, at 3:25 PM, gurcharan khanna wrote:
Vic
I don't think I saw anything here but I think Tom Uram said this was a known
issue. Maybe
someone could clarify what the solution is or in what release version it is
fixed????
-gurcharan
VicSalva wrote:
Did we get an opinion on this? My PIG (lap top) client will time out and
lose connection to the venue client, but the Vic and RAT continue to work.
I'm running 3.0.2. However, I have a PC that will run just fine.
Thx!!
-----Original Message-----
From: owner-ag-t...@mcs.anl.gov [mailto:owner-ag-t...@mcs.anl.gov] On
Behalf
Of gurcharan khanna
Sent: Tuesday, September 25, 2007 3:02 PM
To: ag-t...@mcs.anl.gov<mailto:ag-t...@mcs.anl.gov>
Subject: [AG-TECH] Venue Client keeps leaving the venue and i need to
reenter..
hi,
every day, or couple of days i get kicked out of the RIT Venue on the ANL
server
and need to reenter manually. most of the videos and audio keep running
however.
is there anyway to keep the venue client up persistently? i have
persistent venues
that need to stay up 24/7.
thanks,
-gurcharan
PS WinXP, AG 3.1beta
--
-------------------------
Gurcharan S. Khanna, Ph.D.
Director of Research Computing
Office of the Vice President for Research
Director, Interactive Collaboration Environments Laboratory,
Center for the Advancing the Study of Cyberinfrastructure
---
Rochester Institute of Technology
1 Lomb Memorial Drive
Rochester, New York 14623-5603
Phone: 585-475-7504 ~ Cell: 585-451-8370
Email: gurcharan.kha...@rit.edu<mailto:gurcharan.kha...@rit.edu>
Http: www.rit.edu/~gskpop
Paul Mercer
Arctic Region Supercomputing Center
907 450 8649
