20040822: ldmad.log error msg

>From: mynul khan <address@hidden>
>Organization: St. Clouds State
>Keywords: 200408221611.i7MGBLXn021387 LDM ldmd.log

Mynul,

>Here is the new error msg in ldmd.log. 
>*********************************
>Aug 22 16:06:59 meteor striker2[12352]: ERROR:
>requester6.c:459; ldm_clnt.c:286: nullproc_6 failure
>to striker2.atmos.albany.edu; ldm_clnt.c:142: RPC:
>Unable to receive; errno = Connection reset by peer
>Aug 22 16:07:29 meteor striker2[12352]: Desired
>product class: 20040822150629.023 TS_ENDT {{NLDN, 
>".*"}}
>Aug 22 16:07:29 meteor striker2[12352]: ERROR:
>requester6.c:459; ldm_clnt.c:286: nullproc_6 failure
>to striker2.atmos.albany.edu; ldm_clnt.c:142: RPC:
>Unable to receive; errno = Connection reset by peer
>Aug 22 16:07:59 meteor striker2[12352]: Desired
>product class: 20040822150629.023 TS_ENDT {{NLDN, 
>".*"}}
>Aug 22 16:07:59 meteor striker2[12352]: ERROR:
>requester6.c:459; ldm_clnt.c:286: nullproc_6 failure
>to striker2.atmos.albany.edu; ldm_clnt.c:142: RPC:
>Unable to receive; errno = Connection reset by peer
>Aug 22 16:08:29 meteor striker2[12352]: Desired
>product class: 20040822150629.023 TS_ENDT {{NLDN, 
>".*"}}
>Aug 22 16:08:29 meteor striker2[12352]: ERROR:
>requester6.c:459; ldm_clnt.c:286: nullproc_6 failure
>to striker2.atmos.albany.edu; ldm_clnt.c:142: RPC:
>Unable to receive; errno = Connection reset by peer
>****************************************
>Can you tell me what's it saying?

The Unidata LDM web site has a good description of the various
error messages that can be written to the ldmd.log log file:

Unidata HomePage
http://my.unidata.ucar.edu
  LDM
  http://my.unidata.ucar.edu/content/software/ldm/index.html
    LDM 6.0.14
    http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.14/index.html

    LDM Basics
    http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.14/basics/index.html

      The LDM Logfile
      Format and interpretation 
      
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.0.14/basics/logfile-format.html

The message you sent above follows:

downhost(feed)[pid]: srcloc: nullproc_6() failure to downhost: RPC: Timed out
    An attempt by an upstream LDM 6 to flush the connection to its downstream 
LDM 6 on downhost failed due to an RPC timeout. This might be due to network 
congestion and the downstream LDM 6 might still be connected. This error 
occurred at srcloc.

>From address@hidden  Sun Aug 22 10:55:23 2004

>Hi Tom,
>I was trying to sartup ldm that is installed in
>cyclone. As soon as I typed in "ldmadmin start", the
>following messeges keep printing non-stop on the
>console.Even if I log as another user, for example, as
>mcidas and open a console window it starts printing
>these up.

This tells me two things:

- you have most likely not setup your syslog.conf file so that log
  messages are written to ldmd.conf

- the messages you sent below are related to GEMPAK decoders.

>2941] 040822/1651 [DM -1]
>/data/gempak/surface/20040822_sao.gem
>[2941] 040822/1651 [SF -1]
>/data/gempak/surface/20040822_sao.gem
>[2941] 040822/1651 [SF -1]
>/data/gempak/surface/20040822_sao.gem
>[2941] 040822/1651 [RA -4] 040822/1600
>[2941] 040822/1651 [FL -3]
>/data/gempak/surface/20040822_sao.gem
 ...
>...and it goes on. Can you tell me what the problem
>is?

Since you did not include how you setup the decoding for GEMPAK
decoders (i.e., contents of pqact.conf file(s) (may be
pqact.gempak.conf, etc)), it is hard for us to know what may be wrong

>Also I checked on the ldmd.log after starting up the
>ldm. It has the following error messages.
>
>
>
>Aug 22 16:53:00 cyclone pqact[2886]: unio_open:
>/data/gempak/nexrad/NIDS/FSD/N2S/N2S_20040822_1624:
>Permission denied
>Aug 22 16:53:00 cyclone pqact[2886]: unio_open:
>/data/gempak/nexrad/NIDS/FSD/N2R/N2R_20040822_1624:
>Permission denied
 ...
This looks like you are trying to write to a directory that
you don't have write permission for.

>I have no clue whats going on. I really need to have
>either cyclone or meteor working with their ldm and
>mcidas. 

Since you havn't been through a training session for either the LDM
or McIDAS, it is likely that you are simply missing a simple setup
step and don't realize it.  We would be happy to help you get this
working.  In order to do so, we would need:

- ssh enabled to cyclone from machines here at the UPC (128.117.140.*)

- login as 'ldm'

- login as 'root' or sudo as user 'ldm'

- login as 'mcidas'

If you decide that you want us to login, please send me the passwords
for the various accounts -- without mentioning the account's user name
or machine on which the account is active -- to my personal email
address, address@hidden.

>I very much appreciate you help.

No worries.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.