[LDM #XTZ-897730]: New set of LDM problems

Hi Gerry,

I thought I had driven your email into our inquiry tracking system this
morning, but the attachments you included made the overall size greater
than 2 MB, so it was not incorporated.  When I looked to see if Steve
had had a chance to take a look, I couldn't find your inquiry, and
finally figured out what had happened.  Also, Steve is not in the office
today, so I'll jump in and try to help...

re:
> First day of our Spring Forecasting Experiment and something decided to go
> south on the 27th. Since I was nowhere near a system on Friday or Saturday,
> and no one else has access to this system to change things, I'm starting to
> assume I've possibly got an NFS problem but I can't tell without some
> interpretive help from you, please.

OK.

re:
> And, this is important to getting up and running today here.

Sorry for the delay!

re:
> To that end, I've rebooted the VM, restarted LDM, and I'm still seeing
> errors.  I'm attaching the ldmd.log, ldmd.conf, and 2 pqact config files of
> interest.

I'm looking through the ldmd.log file you sent for ERROR entries, and
the first I found (starting from the end, not the beginning) is:

20190429T151621.706064Z                pqact[16648]              
palt.c:prodAction() INFO                 pipe: -close  python 
/usr/local/ldm/scripts/chomp.py /work/LDM/GOES16/Meso/TISH02_KNES_291515_PAA.n
c and the ident is TISH02 KNES 291515 PAA
20190429T151621.706508Z                pqact[19943]              
filel.c:pipe_open() INFO  Executing decoder "python"
20190429T151621.732395Z                pqact[16648]       
filel.c:fl_removeAndFree() INFO  Deleting closed PIPE entry: pid=19943, 
cmd="-close python /usr/local/ldm/scripts/chomp.py /work/LDM/GOES16/Meso/TI
SH02_KNES_291515_PAA.nc"
20190429T151621.732542Z                pqact[16648]                   
filel.c:reap() INFO  Child 19942 exited with status 0

I believe that the operative part of these messages is the piece:

cmd="-close python /usr/local/ldm/scripts/chomp.py 
/work/LDM/GOES16/Meso/TISH02_KNES_291515_PAA.nc"

The fact that pqact thinks that the command is "-close python ..." suggested to 
me
that there is not a tab between PIPE and -close in your pattern-action file.  
Examination
of the pqact.conf file you included as an attachment, however, shows that each
'PIPE -close python' action does have a tab between the PIPE and '-close'.  This
is also supported by the message:

Executing decoder "python"

So, my next guess would be that either 'python' is not being found;
it is not the correct version (e.g., not python 3.x); or there is
something wrong with the script it is to execute, 
/usr/local/ldm/scripts/chomp.py.

By the way, Steve told me that invoking a script like this:

python<tab>-close<tab> python_script

has the disadvantage that any error messages that would be issued by 'python'
will not be logged.  A better way to find out what is going on is to change
the invocation to:

PIPE<tab>-close<tab> /usr/local/ldm/scripts/chomp.py

This requires, of course, that /usr/local/ldm/scripts/chomp.py be executable
and that the environment of the LDM when the LDM was started be such that
the correct version of 'python' be found in 'ldm's PATH.

re:
> As an aside, the latest netcheck has a potential gotcha for the logfile
> path:
> # set the file paths
> 
> unless (($logpath) || ($no_log)) {
> $logpath = "$ldmhome/var/logs/netcheck.log";
> 
> This should be a reference to $ldmhome/var/logs/netcheck.log, I believe...

This is definitely something for Steve, not me.  That being said, I can't
see a difference in what you listed and your comment:

listed:
$logpath = "$ldmhome/var/logs/netcheck.log";
comment:
            $ldmhome/var/logs/netcheck.log

Those look the same to me.  What am I missing?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: XTZ-897730
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.