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]
[EMAIL PROTECTED] wrote on 04/13/2005 01:54:08 PM: > From the faq <http://www.opendx.org/faq.html#cantconnect> I did look, but didn't find this. Sorry > One may be that your hostname does not resolve properly. > You can test this by using the ping, and hostname > commands to determine if you can ping your own machine ping `hostname` works. hostname and the IP in /etc/hosts agree with hostname and the IP found by ifconfig. > or you can try setting the DXHOST environment > variable to "unix" to default to the local machine. did this and also tried with "localhost". In both cases after loading a (dx) program, I get udp sockets [EMAIL PROTECTED] linux-2.4]# netstat -an | grep DX unix 2 [ ACC ] STREAM LISTENING 508820 /tmp/.DX-unix/DX1920 unix 39 [ ] STREAM CONNECTED 508809 /tmp/.DX-unix/DX1900 however DX times out, and then these sockets disappear. > A second reason > may be that you have a firewall running on your system that refuses > the socket communication over the IP ports that DX uses. > Try shutting off your firewall to see if this fixes the problem. iptables -L, -L -t nat and -L -t mangle are empty. > Other tests to try: Does dx -execonly work? I get sockets like above if that's what you mean. The kernel has unix sockets enabled (built in not module). I didn't set this machine up. AFAIK it's a plain vanilla RedHat something or other. I have a phone call in to the sysadmin to see if he did anything "funny" to it, but I wouldn't expect so. Thanks Joe
