Console logs are written to $HOME/caveData/logs/consoleLogs/$HOSTNAME/*.log
There is probably a connect error traceback in one of those that might shed
more light.
Oh, this is why the EDEX setup.env is important. What's the exact string for
"export HTTP_SERVER=" on the EDEX side?
What happens if you use 'wget' for that same URL on the CAVE machine? You
should get something like:
$ wget http://cb-acq2:9581/services
--2014-06-12 17:47:44-- http://cb-acq2:9581/services
Resolving cb-acq2... 10.5.1.156
Connecting to cb-acq2|10.5.1.156|:9581... connected.
HTTP request sent, awaiting response... 404 Not Found
2014-06-12 17:47:45 ERROR 404: Not Found.
If you get anything else, something is wrong with the ability to make http
connections. (Or more commonly a typo in the HTTP_SERVER line or a client with
a broken DNS or hosts file.)
Kill AlertViz. Then delete the file
"$HOME/caveData/.metadata/.plugins/org.eclipse.core.runtime/.settings/localization.prefs"
Now restart AlertViz and it will ask for the localization data again.
--
Erik Magnuson, ENSCO Inc.
From: Neil Smith [mailto:neils@xxxxxxxx]
Sent: Thursday, June 12, 2014 5:40 PM
To: Magnuson.Erik
Cc: awips2-users@xxxxxxxxxxxxxxxx
Subject: Re: [awips2-users] can't connect CAVE to EDEX
Thanks Erik.
I've changed the Alert server to localhost; started AlertViz (manually) first;
still same error.
I've confirmed firewall is turned off at the EDEX server, the CAVE OS, which is
a VM, and the host OS for the VM host.
Must be something else.
What talks to the CAVE client and where is its log?
Also, is there a way for my CAVE client to connect to someone's properly
running EDEX server so I can test the client on our hardware?
-Neil
---
Neil Smith neils@xxxxxxxx<mailto:neils@xxxxxxxx> 979.845.6272
Senior IT Professional, Atmospheric Sciences, TAMU
On Jun 12, 2014, at 2:53 PM, "Magnuson.Erik"
<Magnuson.Erik@xxxxxxxxx<mailto:Magnuson.Erik@xxxxxxxxx>> wrote:
For one, 'Alert server' should be 'localhost' or the name of the CAVE machine
(i.e. that's the connection between CAVE and Alertviz.) It's possible to run
AlertViz on a separate host from CAVE but I can't think of a good reason to
(other than it's annoying.)
I assume you started Alertviz manually or it started on login? AlertViz must
be running for CAVE to start. I prefer to turn off automatically starting
AlertViz on login (in session preferences) and start it manually.
The other way this error can happen is if there is any firewalling blocking
ports 9581 (EDEX request) or 9582 (Pypies.)
--
Erik Magnuson, ENSCO Inc.
________________________________
The information contained in this email message is intended only for the use of
the individual(s) to whom it is addressed and may contain information that is
privileged and sensitive. If you are not the intended recipient, or otherwise
have received this communication in error, please notify the sender immediately
by email at the above referenced address and note that any further
dissemination, distribution or copying of this communication is strictly
prohibited.
The U.S. Export Control Laws regulate the export and re-export of technology
originating in the United States. This includes the electronic transmission of
information and software to foreign countries and to certain foreign nationals.
Recipient agrees to abide by these laws and their regulations -- including the
U.S. Department of Commerce Export Administration Regulations and the U.S.
Department of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived from
this email to either a foreign national or a foreign destination in violation
of such laws.
