[Thread Prev][Thread Next][Index]
[las_users] a fresh new LAS not plotting COADS!
Dear LAS-ists,
I've just made a fresh new LAS installation on my Linux machine and it
works properly UNTIL the moment I ask to plot!
LAS configuration had no problem and I set the server up use the sample
COADS climatology and Levitus climatology datasets that are distributed with LAS.
I can manually plot them via Ferret, but I have errors when I try to
plot them using LAS.
On the browser I succesfully go up to the CONSTRAINTS page
http://localhost:8080/las/servlets/constrain?var=2
Datasets > COADS climatology Variable(s): AIR TEMPERATURE
and when I click the red "Next >" I get a new window with the following
error:
javax.servlet.ServletException: Server returned HTTP response code: 500 for URL: http://colore.ifa.rm.cnr.it/las-bin/LASserver.pl?xml=%3C%3Fxml+version%3D%221.0%22%3F%3E%3ClasRequest+package%3D%22%22+href%3D%22file%3Alas.xml%22+%3E%3Clink+match%3D%22%2Flasdata%2Foperations%2Fshade%22+%2F%3E%3Cproperties+%3E%3Cferret+%3E%3Csize+%3E.5%3C%2Fsize%3E%3Cformat+%3Eshade%3C%2Fformat%3E%3Ccontour_levels+%3E%3C%2Fcontour_levels%3E%3Cdo_contour+%3Edefault%3C%2Fdo_contour%3E%3Cexpression+%3E%3C%2Fexpression%3E%3Cfill_levels+%3E%3C%2Ffill_levels%3E%3Cfill_type+%3Edefault%3C%2Ffill_type%3E%3Cimage_format+%3Edefault%3C%2Fimage_format%3E%3Cinterpolate_data+%3Efalse%3C%2Finterpolate_data%3E%3Cland_type+%3Edefault%3C%2Fland_type%3E%3Cmark_grid+%3Edefault%3C%2Fmark_grid%3E%3Cpalette+%3Edefault%3C%2Fpalette%3E%3Csize+%3E0.5%3C%2Fsize%3E%3Cuse_graticules+%3Edefault%3C%2Fuse_graticules%3E%3Cuse_ref_map+%3Edefault%3C%2Fuse_ref_map%3E%3C%2Fferret%3E%3C%2Fproperties%3E%3Cargs+%3E%3Clink+match%3D%22%!
2Flasdata%2Fdatasets%2Fcoads_climatology_cdf%2Fvariables%2Fairt%22+%2F%3E%3Clink+match%3D%22%2Flasdata%2Fdatasets%2Fcoads_climatology_cdf%2Fvariables%2Fslp%22+%2F%3E%3Cregion+%3E%3Crange+low%3D%22-48.0%22+type%3D%22x%22+high%3D%22-18.0%22+%2F%3E%3Crange+low%3D%22-4.0%22+type%3D%22y%22+high%3D%2244.0%22+%2F%3E%3Cpoint+v%3D%2215-Jan%22+type%3D%22t%22+%2F%3E%3C%2Fregion%3E%3C%2Fargs%3E%3C%2FlasRequest%3E
at gov.noaa.pmel.tmap.FormFilter.doFilter(FormFilter.java:103)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at gov.noaa.pmel.tmap.SessionFilter.doFilter(SessionFilter.java:506)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at gov.noaa.pmel.tmap.ExceptionFilter.doFilter(ExceptionFilter.java:24)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
There are so many other messages (as usual in Java!)
My installation is:
java/jdk1.5.0_05
LAS 6_5_1_2
tomcat is the one coming with LAS (5.5.9)
I notice that /server/log dir is empty and also noticed some strange (to
me) lines in the file server/Ferret_config.pl which contents are the
following:
sub ferret_config_init {
my $config = shift;
my $which_ferret = "/usr/local/ferret/bin/ferret";
my $ferret_args = "-gif -server";
my $ferret_ps_args = "-server -batch";
my $ferret_transcript = "log/debug_ferret.jnl";
$config->{which_ferret} = $which_ferret;
$config->{ferret_args} = $ferret_args;
$config->{ferret_ps_args} = $ferret_ps_args;
$config->{ferret_transcript} = $ferret_transcript;
}
$ENV{FER_DIR} = ". /usr/local/ferret";
$ENV{FER_DESCR} = "des . . /usr/local/ferret/descr";
$ENV{FER_DATA} = "./data . . /usr/local/ferret/data /usr/local/ferret/go /usr/local/ferret/examples /usr/local/ferret/contrib";
$ENV{FER_GRIDS} = ". . /usr/local/ferret/grids";
$ENV{FER_PALETTE} = "custom jnls jnls/insitu jnls/section . . /usr/local/ferret/ppl";
$ENV{FER_GO} = "custom jnls jnls/insitu jnls/section . . /usr/local/ferret/go /usr/local/ferret/examples /usr/local/ferret/contrib";
$ENV{PLOTFONTS} = "/usr/local/ferret/ppl/fonts";
$ENV{FER_EXTERNAL_FUNCTIONS} = ". /usr/local/ferret/ext_func/libs";
$ENV{DODS_CONF} = "dods/.dodsrc";
1;
What's strange (to me) is the last line (1;) and the values of:
$ENV{FER_DESCR}
ENV{FER_GRIDS}
$ENV{FER_GO}
Can you help me, please?
Thank you from Italy,
Emanuele Lombardi
--
$$$ Emanuele Lombardi
$$$ mail: ENEA CLIM Casaccia
$$$ I-00060 S.M. di Galeria (RM) ITALY
$$$ mailto:emanuele.lombardi@casaccia.enea.it
$$$ tel +39 0630483366
$$$ fax +39 0630484264 |||
$$$ \|/ ;_;
$$$ What does a process need | /"\
$$$ to become a daemon ? | \v/
$$$ | |
$$$ - a fork o---/!\---
$$$ | |_|
$$$ | _/ \_
$$$* Contrary to popular belief, UNIX is user friendly.
$$$ It's just very particular about who it makes friends with.
$$$* Computers are not intelligent, but they think they are.
$$$* True programmers never die, they just branch to an odd address
$$$* THIS TRANSMISSION WAS MADE POSSIBLE BY 100% RECYCLED ELECTRONS
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement