From: Ángel de V. <an...@ia...> - 2010-03-10 09:29:54
|
Hi all, After a few days at last I managed to run both Google Earth and Stellarium in Chromium, but I found something weird... I installed Chromium, Google Earth and Stellarium from source (except Google Earth). I login as angelv to the tile nodes (compute-0-0 and compute-0-1) and to the head node. If I start the crserver program in the tile nodes when connected locally to them (in the console), with: crserver -mothership 192.168.0.1:10000 -port 7000, then I can start "crappfaker " in the head node and there is no problem with either Google Earth or Stellarium. If instead, I try to start the cserver remotely in the head node, with: ssh -x compute-0-0 'bash --login -c "env DISPLAY=:0.0 /home/angelv/cr-1.9/bin/Linux/crserver -mothership 192.168.0.1:10000 -port 7000"' ssh -x compute-0-1 'bash --login -c "env DISPLAY=:0.0 /home/angelv/cr-1.9/bin/Linux/crserver -mothership 192.168.0.1:10000 -port 7000"' then, when I start crappfaker in the head node, compute-0-0 aborts with: [angelv@vaiven configs]$ ssh -x compute-0-0 'bash --login -c "env DISPLAY=:0.0 /home/angelv/cr-1.9/bin/Linux/crserver -mothership 192.168.0.1:10000 -port 7000"' CR Info(compute-0-0:9338): Total output dimensions = (5120, 1024) CR Warning(compute-0-0:9338): EFAULT CR Warning(compute-0-0:9338): Bad bad bad socket error: Bad address CR Warning(compute-0-0:9338): Bad juju: 1048576 268760 on socket 0xc Anyone has any idea why starting remotely like this should crash Chromium? Or how could I start remotely the crserver with ssh? Cheers, Ángel de Vicente PS. glxgears runs fine when I start the crservers in the compute nodes via ssh... -- +---------------------------------------------+ | | | http://www.iac.es/galeria/angelv/ | | | | High Performance Computing Support PostDoc | | Instituto de Astrofísica de Canarias | | | +---------------------------------------------+ |