For the benefit of everybody watching at home, this problem turned
out to be the use of the old operationsV7.xml file with the new
release.
This is really a problem with our installation scripts and we'll be
working on getting this to be more robust, but for the time being if
you are upgrading, unless you have made modifications to it, please
choose to overwrite your old operationsV7.xml file when you do the
configure step to upgrade.
Or, you move your $TOMCAT_HOME/content/las/conf/server directory to
a new location, install the new LAS, and copy over only those pieces
of the configuration you modified into your newly created
$TOMCAT_HOME/content/las/conf/server directory and restart (this is
the technique I use to upgrade).
Roland
On 12/29/2010 05:13 PM, Roland Schweitzer wrote:
John,
I borrowed your configuration, changed all the OPeNDAP references
to the external OPeNDAP URL and your configuration works just fine
with the release code.
So. I conclude that the problem we are having is still a
proxy/set up problem of some sort.
Roland
On 12/29/2010 03:29 PM, John Maurer, IV wrote:
Hi Roland,
I had answered yes and entered my proxy URL during installation,
but the installation still gives the incorrect URL in my files.
Remembering needing to make this corrective step from a previous
installation, I had previously manually edited everything to be
lawelawe:8080 (our internal URL) instead of oos (our external
proxy URL). Neither form works. Maybe we can step through this
together via phone...
Thanks,
John
----- Original Message -----
From: Roland Schweitzer <Roland.Schweitzer@xxxxxxxx>
Date: Wednesday, December 29, 2010 5:37 am
Subject: Re: [las_users] unsuccessful LAS V7.2.1 upgrade: no
maps produced
To: "John Maurer, IV" <jmaurer@xxxxxxxxxx>
Cc: las_users <oar.pmel.las_users@xxxxxxxx>
> John,
>
> The problem you are experiencing likely has to do with your
> proxy server
> setup and how you answered the configuration questions
during
> the
> configure step.
>
> The bottom line is that your LAS ProductServer is trying
access
> URL's of
> the form:
> http://lawelawe.soest.hawaii.edu:8080/las/services/LASFerretBackend
>
> See: http://oos.soest.hawaii.edu/las/ProductServer.do
>
> I believe that you should be using the oos.soest.hawaii.edu
host
> name
> and answering yes to the proxy question in the configure
step to
> make
> sure that LAS always uses the oos.soest.hawaii.edu URL's
internally.
>
> You can find the services definitions in
> $TOMCAT_HOME/content/las/conf/server/productserver.xml.
>
> You can try reconfiguring or editing them by hand. Likely
> you'll need
> some editing in your FerretConfig.xml and
> FerretBackendConfig.xml files
> as well. You can launch a find with a grep on the lawelawe
> host name in
> $TOMCAT_HOME/content/las/ and
> $TOMCAT_HOME/webapps/thredds/WEB-INF/classes/resources
>
> Roland
>
>
>
>
> On 12/22/2010 05:38 PM, John Maurer, IV wrote:
> > Hi All,
> > I attempted to upgrade my LAS from 7.1.1 to 7.2.1. I
upgraded
> Ferret
> > from 6.6.2 to 6.6.5 beforehand, as instructed.
Although the
> interface
> > starts up and I get the list of my datasets, after
selecting
> any
> > variable nothing else happens: I don't get a map or
any
> options on the
> > left. My catalina.out log shows nothing but LAS INFO
> statements:
> > nothing that seems to indicate a problem.
> >
> > LAS 2010-12-22T13:27:09.789 -1000 INFO -
GetCategories -
> START:
> > http://oos.soest.hawaii.edu/las/getCategories.do?catid=hiroms_hiog
> > LAS 2010-12-22T13:27:09.797 -1000 INFO -
GetCategories -
> END:
> > http://oos.soest.hawaii.edu/las/getCategories.do?catid=hiroms_hiog
> > LAS 2010-12-22T13:27:11.346 -1000 INFO - GetRegions -
> START:
> >
>
http://oos.soest.hawaii.edu/las/getRegions.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.348 -1000 INFO - GetRegions -
> END:
> >
>
http://oos.soest.hawaii.edu/las/getRegions.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.374 -1000 INFO - GetGrid -
> START:
> >
>
http://oos.soest.hawaii.edu/las/getGrid.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.377 -1000 INFO - GetGrid -
> END:
> >
>
http://oos.soest.hawaii.edu/las/getGrid.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.380 -1000 INFO -
> GetDataConstraints - START:
> >
>
http://oos.soest.hawaii.edu/las/getDataConstraints.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.388 -1000 INFO -
> GetDataConstraints - END:
> >
>
http://oos.soest.hawaii.edu/las/getDataConstraints.do?dsid=hiroms_hiog&varid=salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.505 -1000 INFO -
GetOperations -
> START:
> >
>
http://oos.soest.hawaii.edu/las/getOperations.do?xpath=/lasdata/datasets/hiroms_hiog/variables/salt-hiroms_hiog
> > LAS 2010-12-22T13:27:11.525 -1000 INFO -
GetOperations -
> END:
> >
>
http://oos.soest.hawaii.edu/las/getOperations.do?xpath=/lasdata/datasets/hiroms_hiog/variables/salt-hiroms_hiog
> >
> > ProductServer.do doesn't seem to indicate any problems
either.
> And my
> > F-TDS seems to be working: I can click on datasets and
get data.
> >
> > Here's the URL to our LAS and F-TDS:
> >
> > http://oos.soest.hawaii.edu/las/
> > http://oos.soest.hawaii.edu/thredds/dodsC/las/
> >
> > Any ideas?
> > Thanks!,
> > John Maurer
> > Hawaii Ocean Observing System (HiOOS)
> > University of Hawaii
>
|