[Thread Prev][Thread Next][Index]
LAS 6.2.1 unable to access DODS served data
Hi all,
I'm having trouble with a new LAS 6.2.1 install on a linux RH9 system:
It seems I am unable to access DODS served data from LAS 6.2.1.
I hoping someone out there has a suggestion for why LAS might not be
able to access a DODS dataset.
Details of my situation:
Instead of the requested plot, the following is displayed in the
browser window
yes? go std_initialize "http://usjgofs.whoi.edu/dods-bin/nph-dods/dods/data/fer_dsets/data/coads_climatology.cdf" "1" "1" "airt"
** netCDF error: Invalid Argument
is this a CDF file ?
but I am able to access the data directly from ferret using the same
command, and also via a DODS URL as well.
I've done lots of testing and have narrowed this down to an inability
of LAS 6.2.1 to access data via DODS.
I am suspicious that something on the linux system has gotten clobbered
somehow, since when I regenerate the server/UI, the following lines are
returned:
../xml/perl/genLas.pl -h usjgofs2.whoi.edu -u root -p PSWD las.xml
Serializing file:/usr/local/las-lite/server/las.xml to database
Building indexes...
Resolving links...
Generating dataset COADS climatology
Generating dataset Levitus Climatology
notice the absence of "ExternEnt (XML::Parser::Expat=" type lines.
as opposed to those I receive when generating the analogous server on
a different system (an SGI):
../xml/perl/genLas.pl -h usjgofs.whoi.edu -u root -p PSWD las.xml
ExternEnt (XML::Parser::Expat=HASH(0x10383ebc),las.xml,operations.xml)
ExternEnt (XML::Parser::Expat=HASH(0x10383ebc),las.xml,coads.xml)
ExternEnt (XML::Parser::Expat=HASH(0x10383ebc),las.xml,levitus.xml)
Serializing file:/users/las/las-lite/server/las.xml to database
Building indexes...
Resolving links...
ExternEnt (XML::Parser::Expat=HASH(0x108e94b8),ui.xml,options.xml)
Generating dataset COADS climatology
Generating dataset Levitus Climatology
perhaps it's just a difference in the two OS (SGI IRIX v. RH9)?
but I include it here in case this observation is related to my
LAS/DODS problem.
I have two LAS6.2.1 servers set up, both configured with the default
las.xml (COADS and Levitus only) and none of my customizations (hence
the las-lite names).
The one that works is running on an SGI/IRIX system (that is old and
tired):
http://usjgofs.whoi.edu:8060/las-lite/servlets/
and the one that can not see any DODS datasets is (a new RH9 -
superfast, but DODS-challenged!):
http://usjgofs2.whoi.edu:8060/las-lite/servlets/
On each one, I set up the xml files so that COADS is served via DODS
3.2 running on the SGI
(since DODS 3.4 on the RH9 system is new and may have issues of it's
own)
OS environment details follow in case that's helpful.
Thanks for any hints anyone can provide,
Cyndy
linux RH9 environment details:
Linux RedHat 9.0 2.4.24 #11 SMP
DODS server core software: DAP/3.4.5 <-- on RH9 system
(but the DODS server being used is v3.2) <-- on SGI/IRIX system
Apache/2.0.40 (Red Hat Linux)
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
perl, v5.8.0 built for i386-linux-thread-multi
netcdf library version 3.5.0 of Oct 10 2003 13:42:35
FERRET v5.53 - Linux(g77) 2.4.20 - 10/16/03
mysql Ver 11.18 Distrib 3.23.58, for redhat-linux-gnu (i386)
Bit::Vector 6.1
CGI 2.89
Compress::Zlib 1.33
DBD::mysql 2.1021
DBI 1.32
Data::ShowTable (unknown)
Date::Calc 5.3
Date::Manip 5.40
Digest::MD5 2.20
File::PathConvert 0.9
HTML::Parser 3.26
HTML::Tagset 3.03
LWP::UserAgent 2.001
Log::Agent 0.305
MD5 2.03
MIME::Base64 2.12
NetCDF (unknown)
Parse::Lex (unknown)
Parse::Yapp (unknown)
Template 2.12
Test::More 0.47
Time::HiRes 1.38
URI::URL 5.03
XML::DOM 1.27
XML::Parser 2.31
XML::Parser::PerlSAX 0.07
XML::RegExp (unknown)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cyndy Chandler | voice: (508) 289-2765
MS #43, WHOI | Office hrs: M-F ~ 9-4
Woods Hole, MA 02543 | FAX: (508) 457-2161
cchandler@whoi.edu | FAX2: (508) 457-2164
U.S. JGOFS Data Management Office
Department of Marine Chemistry and Geochemistry
Woods Hole Oceanographic Institution
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement