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

[McIDAS #SJA-155956]: LDM decoder problem



Hi Hsie,

re: which decoders are having problems.

> I ldmd.log file is full of:
> 
> May 21 21:20:20 rainbow pqact[29007] NOTE: child 722 exited with status
> 2 (buoy2nc/home/ldm/decoders/etc/buoy.cdldata/wxp/decoded200905)
> May 21 21:20:25 rainbow pqact[29007] NOTE: child 724 exited with status
> 2 (metar2nc/home/ldm/decoders/etc/metar.cdldata/wxp/decoded200905)

 ...

> May 21 21:20:48 rainbow stratus.al.noaa.gov(feed)[576] ERROR: Couldn't
> flush connection; nullproc_6() failure to stratus.al.noaa.gov: RPC:
> Unable to receive; errno = Connection reset by peer
> May 21 21:20:48 rainbow rpc.ldmd[29004] NOTE: child 576 exited with status 6
> May 21 21:20:49 rainbow stratus.al.noaa.gov(feed)[737] NOTE: Starting
> Up(6.7.0/6): 20090521202048.862 TS_ENDT {{FNEXRAD|FSL2|UNIDATA,  ".*"}},
> SIG=c113e17bd8ac0bb8a645d522a0c6e949, Alternate
> May 21 21:20:49 rainbow stratus.al.noaa.gov(feed)[737] NOTE: topo:
> stratus.al.noaa.gov {{FNEXRAD|FSL2|UNIDATA, (.*)}}

 ...

> May 21 21:21:10 rainbow pqact[29007] NOTE: child 742 exited with status
> 2 (ua2nc-h/home/ldm/decoders/etc/raob.cdldata/wxp/decoded200905)

> May 21 21:21:10 rainbow pqact[29007] NOTE: child 745 exited with status
> 2 (syn2nc/home/ldm/decoders/etc/syn.cdldata/wxp/decoded200905)

> May 21 21:21:10 rainbow pqact[29007] NOTE: child 747 exited with status
> 2 (ua2nc-h/home/ldm/decoders/etc/raob.cdldata/wxp/decoded200905)

> May 21 21:21:51 rainbow stratus.al.noaa.gov(feed)[737] NOTE: feed or
> notify failure; COMINGSOON: RPC: Unable to receive; errno = Connection
> reset by peer
> May 21 21:21:51 rainbow rpc.ldmd[29004] NOTE: child 737 exited with status 6
> May 21 21:21:51 rainbow pqact[29007] NOTE: child 780 exited with status
> 2 (metar2nc/home/ldm/decoders/etc/metar.cdldata/wxp/decoded200905)

> May 21 21:21:52 rainbow stratus.al.noaa.gov(feed)[779] NOTE: Starting
> Up(6.7.0/6): 20090521202151.849 TS_ENDT {{FNEXRAD|FSL2|UNIDATA,  ".*"}},
> SIG=9963d95ebcde1decc655a32223f74b6f, Primary
> May 21 21:21:52 rainbow stratus.al.noaa.gov(feed)[779] NOTE: topo:
> stratus.al.noaa.gov {{FNEXRAD|FSL2|UNIDATA, (.*)}}

The output you sent indicates that the problems are with the netCDF decoders
(e.g., metar2nc, etc.).  I would guess that the problem is one of a small
set of things:

- the metar decoders are not in a directory in the PATH defined for your
  'ldm' user

  Check this by running the following:

  <as 'ldm'>
  which metar2nc

  If 'metar2nc' can not be found, then your PATH setting is incorrect
  OR the execute bit is not set on 'metar2nc'.

- one or more shared libraries needed by the netCDF decoders is not being
  found.

  This one is easy to check using the 'ldd' facility.  For example, if
  the executable 'metar2nc' is located in the ~ldm/decoders directory,
  run:

  <as 'ldm'>
  ldd ~ldm/decoders/metar2nc

  The output listing for metar2nc should show which shared library(ies)
  is(are) missing.

- the netCDF decoder binaries you have are an incorrect type for your
  platform

  Check for this using the 'file' utillity:

  <as 'ldm'>
  file `which metar2nc`

I intended to logon to rainbow to see which of the above three options was
the likely culprit, but I was unable to SSH to any of your machines (I
tried cirrus, cumulus, and rainbow).

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: SJA-155956
Department: Support netCDF Decoders
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.