[prev in list] [next in list] [prev in thread] [next in thread]
List: npaci-rocks-discussion
Subject: [Rocks-Discuss] Help with getting SAGE started on an OptIPortal
From: "Boyce,Edward" <BOYCE () uchc ! edu>
Date: 2010-09-28 20:24:16
Message-ID: 787EE346CC481146A5AA02BCA4E439E54B75C26B09 () NSO-ITEXC-CCR02 ! uchc ! net
[Download RAW message or body]
Hi all.
I have deployed 2 tiles of our soon to be 12 tile OptIPortal and have successfully \
run several OpenGL apps across the tiles using Chromium.
I wonder why some OpenGL apps (like VisIt's viewer and glxgears) work automatically \
with Chromium and others (e.g. Celestia, Open Cobalt) don't (their OpenGL streams \
apparently don't get intercepted by Chromium when it is activated by 'rocks enable \
chromium' and just display on the frontend.)
I am also struggling to get SAGE working. I start SAGE on the front end with 'rocks \
start sage' (after disabling Chromium of course) and I get the GUI. I try to start a \
new connection giving the local host as the server info. But I'm unable to get \
anywhere. Below is pasted the output of the SAGE window in the SAGE Launcher \
Advanced Settings gui. Does this tell anyone here what might be going on? One \
confusing item where it says
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not \
ready
192.168.255.254 is the IP address of tile-0-0:0.0, not the front end, which has \
192.168.12.100 as its address. The second tile's (tile-1-0:0.0) IP address is \
192.168.255.253, which I don't see mentioned anywhere in SAGE info window. But in \
the SAGE UI window (pasted below the SAGE window output below), I do see evidence it \
has detected both screens -- it correctly reports their resolution. Below that I've \
pasted what the terminal shows from which I start SAGE, just in case its information \
sheds any light.
Lastly, I have a general question about where is the best and most recent place to \
find documentation about how to use SAGE on a Rocks/VizRoll based OptIPortal. There \
are only 3 sentences on the matter in the Viz Roll documentation (that I've found so \
far), and the docs on SAGE's official site seem to date from 5 years ago, and don't \
refer at all to how Rocks' Viz Roll has it set up. I will be more than glad to add \
to Rocks' documentation once I understand things better myself. In the meantime, and \
pointers and/or hand holding would be greatly appreciated.
Best Regards,
Ed Boyce
Center for Cell Analysis and Modeling
University of Connecticut Health Center
#####################################################
What the output from SAGE window shows:
**** Already running ****
fsManager using configuration file <fsManager.conf>
QUANTA 0.4 (APRIL 14 2004) [PTHREAD VERSION] - [COMPILED Dec 13 2009 12:23:57]
sshCmd = /usr/bin/ssh -fx 192.168.255.254 "env DISPLAY=:0.0 \
SAGE_DIRECTORY=/root/.sage /root/.sage/bin/sageDisplayManager 192.168.12.100 20002 0 \
12000 0 1 "
env: /root/.sage/bin/sageDisplayManager: No such file or directory
sshCmd = /usr/bin/ssh -fx 192.168.255.253 "env DISPLAY=:0.0 \
SAGE_DIRECTORY=/root/.sage /root/.sage/bin/sageDisplayManager 192.168.12.100 20002 1 \
12000 0 1 "
audio on
audio /root/.sage/bin/sageAudioManager 192.168.12.100 20002 0 12000
env: /root/.sage/bin/sageDisplayManager: No such file or directory
sshCmd = /usr/bin/ssh -fx 192.168.12.100 "env DISPLAY=:0.0 \
/root/.sage/bin/sageAudioManager 192.168.12.100 20002 0 12000 "
try to connect to .... 206.220.241.46 : 15557
SAGE Audio Manager : register to a Free Space Manager
sysClient 0 connected
recv 0 : 192.168.255.254 -1 0 44100 2 2048
QUANTA 0.4 (APRIL 14 2004) [PTHREAD VERSION] - [COMPILED Dec 13 2009 12:23:57]
---> message : 8388608 4194304 1400 28000 26000 24000 100 2 192.168.255.254 -1 0 \
44100 2 2048 sageAudioModule::init: initialized
Audio Manager is initializing network objects....
SAGE sageAudioManager Manager : tcp network object was initialized successfully
SAGE sageAudioManager Manager : udp network object was initialized successfully
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): sync server 192.168.255.254 : 12000 is not ready
sageSyncClient :: connectToServer(): Giving up after trying a few times
SAGE receiver : Fail to connect to sync master
sageTcpModule::checkConnections(): Invalid argument
sageAudioManager::nwCheckThread : exit
sageUdpModule::checkConnections() - error in accepting control connection
sageAudioManager::nwCheckThread : exit
uiClient 0 connected
uiClient 1 connected
uiClient 2 connected
connection to client 1000 was terminated
fsManager : fail to connect to the connection manager
######################################################
What the SAGE GUI window shows:
**** Already running ****
**** Already running ****
**** Already running ****
Currently running:
--------------------------
SAGE UI version: 3.0a
Python version: 2.4.2
wxPython version: 2.8.7.1
UsersClient: can't connect to SAGE UI Users Server.
no connection to the sage server... can't get the list of appLaunchers
connected to SAGE 192.168.12.100 20001
SEND: Register UI
[]
RECEIVED: Display Info
[2 2 1
5120 1600
2560 1600 0]
######################################################
What the terminal shows when I start SAGE:
[root@vizwall]# rocks start sage
[root@vizwall]# Traceback (most recent call last):
File "sageLauncher.py", line 896, in OnAppList
for c in self.configs.getApp(a).getAllConfigNames():
File "sageLauncher.py", line 2686, in getApp
return self._appConfigs[appName]
KeyError: u''
Overlay plugin loaded: wall
Overlay plugin loaded: pointer
Overlay plugin loaded: app
Device plugin loaded: puck
Device plugin loaded: joystick
can't connect to SAGE localhost 20001
No joysticks connected...
connected to SAGE localhost 20001
SEND: Register UI
[]
RECEIVED: Display Info
[2 2 1
5120 1600
2560 1600 0]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic