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
Yep, it was the firewall. I disabled the firewall and now it works
without having to set DXHOST to localhost.
This could very well be the case. I will make a note on this in the FAQ.
David
As far as I can see there is nothing wrong with my host name
resolution. When DXHOST is set to
As far as I can see there is nothing wrong with my host name
resolution. When DXHOST is set to localhost it works, but when it is
set to my fully qualified network address it fails. Could it be due
to the default firewalling rules that Redhat 7.2 sets up to prevent
intrusion? If it is
This could very well be the case. I will make a note on this in the FAQ.
David
As far as I can see there is nothing wrong with my host name
resolution. When DXHOST is set to localhost it works, but when it
is set to my fully qualified network address it fails. Could it be
due to the
I set up the install prefix to be /usr/local, and it put the dx
program in /usr/local/bin, but it put the dxexec and other programs
in /usr/local/dx/linux-bin and dx/bin. So I created symbolic links
from /usr/local/bin so that they'd be in my path. I also used ldd to
check that the programs
Ok, I tried the stuff on the Getting Started page, and I was able to
get things to run by following the directions there. (dx -uionly dx
-execonly) Is there a simpler way of starting it up so that it
connects to the local server? Typing in two commands and navigating
through the dialogs
I figured out how to get dx to connect to dxexec without manual
intervention (ala Getting Started). Setting DXHOST to localhost
(setenv DXHOST localhost) solves the problem.
-steve
If this is the case, then you have some problem in your network
setup. Like your machine's name/IP address is not the same as in the
DNS Lookup (or hosts) file.
David
I figured out how to get dx to connect to dxexec without manual
intervention (ala Getting Started). Setting DXHOST to
I just compiled and installed DX on my RedHat 7.2 linux machine, but it dies
when I try to open a .net file. The compile and install ran without a hitch.
I ran dx at the command line, and got the main window. I click on the
Edit Visual Programs.. button, and select the example1.net file
There is a faq topic I found on that.
http://www.research.ibm.com/dx/faq.html
What if the user interface can't connect to server?
This problem can be caused if OpenDX wasn't installed using the
standard install process. If you have to type a
pathname in front of the dx command to
13 matches
Mail list logo
