Joseph Mack PhD, High Performance Computing Scientific Visualisation
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007 Federal
Infrastructure Contact-Ravi Nair 919-541-5467 - [EMAIL PROTECTED],
Federal Visualization Contact - Joe Retzer, Ph.D. 919-541-4190 -
[EMAIL PROTECTED]
I
From the faq http://www.opendx.org/faq.html#cantconnect
The user interface and the server (exec) communicate over sockets.
Netwoking must work in order for this process to work completely.
There are several reasons why this communictaion may fail. One may be
that your hostname does not
Joseph Mack PhD, High Performance Computing Scientific Visualisation
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007 Federal
Infrastructure Contact-Ravi Nair 919-541-5467 - [EMAIL PROTECTED],
Federal Visualization Contact - Joe Retzer, Ph.D. 919-541-4190 -
[EMAIL PROTECTED]
One of the tests you can always do is
dx -uionly
dx -execonly
Then go into the UI and try to connect to an already running server.
See if it allows you to get past it. If not, then I'd almost bet that
there is some kind of network problem on the machine (sockets are
somehow getting
