Running BridgeServers for ag-2 and vv2
Thomas D. Uram
turam at mcs.anl.gov
Mon Jun 14 14:54:16 CDT 2004
Starting BridgeServers
======================
BridgeServers for ag-2 and vv2 are run on the machine named ag-tech.
Scripts to start them reside in /home/ag, and are named StartBridge_ag2
and StartBridge_vv2. I usually start them in a screen session.
StartBridge_ag2 runs the BridgeServer.py script in the current
directory, using the config file ag2bridge.cfg, which bridges the entire
ag-2 server.
StartBridge_vv2 also uses the current-directory BridgeServer.py script,
using the config vv2bridge.cfg, which bridges the venues listed in the
vv2bridge.venues file. These venues are on the AG wiki here:
http://www-unix.mcs.anl.gov/fl/research/accessgrid/wiki/moin.cgi/BridgedVenues
Stopping BridgeServers
======================
If, for some reason, the bridges need to be restarted, you can re-enter
the screen session in which StartBridge_??? was started and Ctrl-C.
This often takes waaay too long (fixed in 2.2), so you'll want to kill
the processes.
You should make sure the python BridgeServer.py processes and related
QuickBridge processes all die, without killing processes that belong the
other bridge server. You can do this through the process group id:
ps -eo pgrp,args|grep Bridge
will show you all the BridgeServer and QuickBridge processes with their
process group id. From the argument lists, you should be able to
distinguish the ag-2 from the vv2 bridge processes, and kill the
appropriate process group:
sudo kill -9 -pgid
Since the vv2 BridgeServer uses static ports for the bridges, if a
QuickBridge process is left running through a restart, when you try to
run the BridgeServer again, you'll see output that indicates that
QuickBridge failed to start because it couldn't open a port (note the
last line):
max_unicast_mem is 32
myhostname=ag-tech.mcs.anl.gov
myhostipaddress=140.221.9.160
using multicast
ucport[data]=58688 ucport[rtcp]=58689
mcport[data]=60750 mcport[rtcp]=60751
can't bind ucaddr to socket!: Address already in use
I'll put this information in a conspicuous place (internal wiki?) later,
so it's readily referrable. This is obviosuly not a polished doc, but I
hope I've captured what's needed.
Tom
More information about the ag-dev
mailing list