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

[ldmMcidas #KHY-214172]: ldm help help pnga2area / MCIDAS ?

Hi Steven,

> I know I am bypassing the protocol list serve -- but we have tried
> numerous things to try to get this to work to no avail. Given that you
> did the install for us when I was there in July...I was hoping that you
> could just log in and knock this out.

OK, this works for me.

> I can text you the password and IP.

No cell phone, so no texts.  I do have an iPod Touch, however, so you can
iMessage me: address@hidden  Otherwise, you can call me at

Quick comment:

- the pipe_put(): write error message seems to say that 'pnga2area'
  is not being found, so 'pqact' is unable to pipe the product
  to it

  Can you/Mike verify that 'pnga2area' can be found?  You can
  test this by substituting 'pnga2area' in the LDM pattern-action
  file with its fully qualified name (e.g., /home/ldm/decoders/pnga2area
  if 'pnga2area' was copied to the /home/ldm/decoders directory.

  Given the specific reference to /home/ldm/ldm-mcidas/ldm-mcidas-2008/etc
  for both SATANNOT and SATBAND, I would suspect one of three things:

  - the 'pnga2area' executable was not copied to /home/ldm/decoders or
    /home/ldm/util (both of these directories are in the PATH Mike
    included below)

  - 'pnga2area' was copied to either /home/ldm/decoders or /home/ldm/util,
    but you are using the C Shell (or TC Shell), and 'rehash' was not
    run after the copy

  - OR 'pnga2area' was copied to either /home/ldm/decoders or /home/ldm/util
    after the LDM was already running.  In this case 'pnga2area' would not
    be found

You can easily test the above by doing the following:

<login as 'ldm'>
ldmadmin stop
which pnga2area

Is 'pnga2area' found?  If yes, run the following:

ldd /home/ldm/decoders/pnga2area

Does 'ldd' indicate that all needed shared libraries found?

> Thanks!

No worries.

I included some additional comments below...

> Steven
> Can you get help for the following?
> I am trying to get the following working in the pqact.conf:
> MCIDAS  ^pnga2area Q. UI (.*) (.*) (.*) (.*) (........) (....)
> PIPE    -close
> pnga2area -vl /home/ldm/data/gempak/logs/dcsat.log
> -a /home/ldm/ldm-mcidas/ldm-mcidas-2008/etc/SATANNOT
> -b /home/ldm/ldm-mcidas/ldm-mcidas-2008/etc/SATBAND
> /home/ldm/data/gempak/images/sat/goes13/\4/IR/IR_\5_\6

This looks OK.

> I was able to get pnga2area to compile and it "seems to work", the "make
> test" for decoding seemed OK.

This should mean that there is nothing fundamentally wrong with 'pnga2area'.

> The errors I am getting in the log file are a classic "broken pipe" --
> of which I have tried many variants in fixing:
> > Aug  5 12:04:56 cumulus pqact[5853] ERROR: pipe_put(): write error:
> > pid=6004, cmd=(-close pnga2area -vl logs/ldm-mcidas.log -a
> > etc/SATANNOT -b etc/SATBAND
> > /home/ldm/data/gempak/images/sat/goes13/4km/IR/IR_20120805_1545)
> > Aug  5 12:04:56 cumulus pqact[5853] ERROR: Deleting failed PIPE entry:
> > pid=6004, cmd="-close pnga2area -vl logs/ldm-mcidas.log -a
> > etc/SATANNOT -b etc/SATBAND
> > /home/ldm/data/gempak/images/sat/goes13/4km/IR/IR_20120805_1545"
> > [filel.c:290]
> Based on a "ldd" of pnga2area I have set the following in the
> .bash_profile for ldm
> # User specific environment and startup programs
> PATH=$HOME/bin:$HOME/decoders:$HOME/util:$PATH
> export PATH
> LD_LIBRARY_PATH=/home/ldm/ldm-6.10.1/lib:/usr/lib64:/lib64
> I have messed with setting the tabs in the pqact.conf many times, etc. I
> am either really close or really far!
> Mike


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: KHY-214172
Department: Support ldm-mcidas
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.