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

Re: 20050429: LDM - Binaries available?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20050429: LDM - Binaries available?
  • Date: Tue, 03 May 2005 16:42:52 -0600
Scott,

>Date: Tue, 03 May 2005 14:09:44 -0800
>From: "Scott Swank" <address@hidden>
>Organization: NOAA/NWS
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050429: LDM - Binaries available?
>Keywords: 200504291922.j3TJMbKx001883

The above message contained the following:

> I have downloaded and installed 6.3 on my linux box and it is behaving 
> with 5 much nicer than 6.1 did.  I am seeing all the products on my ldm 
> 5 server that are being inserted by my ldm 6.3 server.  However, I am 
> periodically seeing the following:
> ===================================================================
> In ldmd.log:
> 
> May 03 21:56:42 arhdata pqact[8280]:     2471 20050503215455.916     EXP 
> 000  METAR_vrh_SAUS20KNKA.86263.123215455
> May 03 21:56:43 arhdata pqcat[11691]: Starting Up (8278)
> May 03 21:56:43 arhdata pqcat[11691]: Exiting
> ===================================================================
> 
> This tells me the file METAR_vrh_SAUS20KNKA.86263.123215455 was received 
> in the queue, and saved to disk.  However, my EXEC command that was 
> called was called 2x at the same time.

The above doesn't show that something was executed twice -- so I have to
ask if you're confusing "pqact" with "pqcat" in the above.

> This seems to happen about 1 in 
> 50 products.  Here is the snip of the log file for the script that 
> processes the file after it is pulled from the queue:
> ===================================================================
> Arguments: /apps/decoders/ldm_metar.ksh METAR_vrh_SAUS20KNKA.86263.123215455
> Starting:21:56:43 05/03/05 11727
> Arguments: /apps/decoders/ldm_metar.ksh METAR_vrh_SAUS20KNKA.86263.123215455
> USER: uid=104(ldm) gid=20(users)
> USER: uid=104(ldm) gid=20(users)
> 21:56:43 05/03/05  /data/raw/METAR_vrh_SAUS20KNKA.86263.123215455 
> Decoding for /data
> 21:56:43 05/03/05  /data/raw/METAR_vrh_SAUS20KNKA.86263.123215455 
> Decoding for /data
> Modified file. New path = /data/raw/X_METAR_vrh_SAUS20KNKA.86263.123215455
> Modified file. New path = /data/raw/X_METAR_vrh_SAUS20KNKA.86263.123215455
> /data/raw/X_METAR_vrh_SAUS20KNKA.86263.1232154
> /data/raw/X_METAR_vrh_SAUS20KNKA.86263.1232154
> mv: /data/raw/X_METAR_vrh_SAUS20KNKA.86263.1232154: cannot access: No 
> such file or directory
> Stopping:21:56:43 05/03/05 11729
> Stopping:21:56:43 05/03/05 11727
> ===================================================================

I'm afraid that the above is Greek to me -- although it does appear to
contain duplicated information.

> Any suggestions on why the EXEC command is being called 2x for the same 
> file seemingly randomly?

Assuming that you're not confusing "pqact" with "pqcat", then I don't
have enough information.  Could you send me the LDM configuration-file
(etc/ldmd.conf) and the pqact(1) configuration-file (etc/pqact.conf).

Also, use the ps(1) utility to verify that you only have a single
pqact(1) process.

> Thanks,
> Scott

Regards,
Steve Emmerson