[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #XDH-337278]: Directory structure for $GEMDATA and decoders not working



Hi Raymond,

Thanks for attaching the logs and environmental variable files.

The first thing noticed in ldmd.log is

Dec 05 14:35:36 awipserver pqact[19304] NOTE: Configuration-file 
"/usr/local/ldm/etc/pqact.conf" has no entries. You should probably not start 
this program instead.

Which suggests the pqact.conf isn't being taken correctly.  Even so, there are 
decoder entries in the log file such as:

Dec 05 14:35:36 awipserver pqact[19308] ERROR: [filel.c:1404] Couldn't execute 
decoder "decoders/dcnldn"

So I'm not entirely sure what the problem is, but I can guess that it's due to 
difference between data directories in the gempak and ldm users' environment.

What is 'env' os the user ldm, and does /usr/local/ldm/data point to 
/mnt/sbd/var/ldm?


-Michael

> Michael,
> 
> Ok, I have LDM and GEMPAK running but not much is getting decoded by
> pqact.gempak.   I suspect it is due to an incorrect directory
> structure in the LDM directory.
> 
> What I've done:
> 
> 1) I have ldm and gempak as users on awipsserver.physics.umbc.edu.
> ldm's home directory is /usr/local/ldm  (as suggested in the ldm
> documentation).  gempak's home directory is /home/gempak  (with other
> users)
> 
> 2)  If I run pqact.conf that comes with ldm, I can pull feeds (see
> watch.txt attached) from idd.meteo.psu.edu and it looks like the
> UNIDATA feed (and the UNIWISC) feeds work.
> 
> 3)  When I built ldm, I did not want the /var directory on my main
> hard drive on the server, but I put it on a raid  (/mnt/sdb/var) and I
> symbolically linked /var and /data in ldm to point to /mnt/sdb/var and
> /mnt/sdb/var/data).   That worked ok and the ldm data was pushed to
> /mnt/sdb/var/data/surface/US.... for the demo pqact.conf feeds from
> IDS.
> 
> 4) In GEMPAK, all built out ok (except for the /gf bug that I sent
> previously) and GEMPAK runs fine.   I attach the env for gempak.   I
> think the issue is here.   I left $GEMDATA as it was in Gemenviron as
> it was built by the csh routine in GEMPAK.
> 
> setenv GEMDATA       /data/ldm/gempak
> 
> That seemed strange to me but it started putting the gempak data in
> /usr/local/ldm/data/data/images/    etc....
> 
> I only got /images   /jason  and  /nwx  built in that directory.
> /surface doesn't get decoded.    From the gempak_env, you can see that
> it set up the /usr/local/ldm/data/data/gempak structure.
> 
> I attach a zipped version of the ldmd.log file with the errors.  It
> looks like this is not feed related but the decoders are not all
> working.
> 
> 5) To make GEMPAK read from the right files,  I had to change the
> above Gemenviron variable to be
> 
> setenv GEMDATA      /usr/local/ldm/data/data/gempak
> 
> and then GEMPAK could go and get the data that was available (images
> mostly.... the GOES data is coming in ok.)
> 
> Suggestions on how to fix the Gemenviron file (also attached)?
> 
> Ray
> 
> --
> Raymond M. Hoff
> Professor of Physics
> Rm 426, Physics Dept.
> University of Maryland, Baltimore County
> 1000 Hilltop Circle
> Baltimore MD 21250
> p: 410-455-1943 f:410-455-1042
> e: address@hidden
> physics.umbc.edu/~hoff
> 
> 

Ticket Details
===================
Ticket ID: XDH-337278
Department: Support GEMPAK
Priority: Normal
Status: Open