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

[LDM #JWV-419912]: Data feed dropping out?

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: [LDM #JWV-419912]: Data feed dropping out?
  • Date: Mon, 07 Jul 2014 12:53:34 -0600
Evan,

Offhand, I'd say that error couldn't possibly occur. :-)

Seriously, the error indicates an inconsistency in the product-queue. Did you 
have a power outage or send the LDM a SIGKILL signal? Are you having any 
problems with the disk that the product-queue is on?

My suggestion is to stop the LDM, delete and recreate the product-queue, and 
then restart the LDM. You'll lose some data -- but you're not getting anything 
right now.

Please tell me if this problem re-occurs with the new product-queue.

> Good afternoon,
> 
> I hope this finds you well today. I seem to be having a problem with a
> downstream LDM receiving data. It seems that data shows up as expected
> for a short time, but then the feed stops while the LDM appears to still
> be running. Here are some details:
> 
> 1. ldmping returns the following:
> 
> ldmping 129.82.225.8
> 
> Jul 07 16:30:39 INFO:      State Elapsed Port Remote_Host rpc_stat
> Jul 07 16:30:40 INFO: RESPONDING   0.140582  388 129.82.225.8
> 
> Jul 07 16:31:05 INFO: RESPONDING   0.027639  388 129.82.225.8
> Jul 07 16:31:30 INFO: RESPONDING   0.026767  388 129.82.225.8
> Jul 07 16:31:55 INFO: RESPONDING   0.028274  388 129.82.225.8
> Jul 07 16:32:20 INFO: RESPONDING   0.026373  388 129.82.225.8
> Jul 07 16:32:45 INFO: RESPONDING   0.027317  388 129.82.225.8
> Jul 07 16:33:10 INFO: RESPONDING   0.027174  388 129.82.225.8
> Jul 07 16:33:35 INFO: RESPONDING   0.027064  388 129.82.225.8
> 
> 2. The ldmd.log shows the following:
> 
> $ tail ldmd.log
> Jul  5 04:58:58 centos 129.82.225.8[21697] NOTE: LDM-6 desired
> product-class: 20140705035858.554 TS_ENDT {{WMO,  "^...... ....
> ([0-3][0-9])([0-2][0-9])([0-5][0-9]).*/p(ZFP...)"}}
> Jul  5 04:58:58 centos 129.82.225.8[21697] NOTE: Upstream LDM-6 on
> 129.82.225.8 is willing to be a primary feeder
> Jul  5 18:45:37 centos 129.82.225.8[21697] ERROR: pq_del_oldest:
> signature 8954bbe48c486291fbde508076dc1ef4: Not Found
> Jul  5 18:45:37 centos 129.82.225.8[21697] ERROR: pq_insert() failed:
> Invalid argument:    34304 20140705184536.756 IDS|DDPLUS 37407417
> FPUS53 KDDC 051845 /pZFPDDC
> Jul  5 18:45:37 centos 129.82.225.8[21697] NOTE: Exiting
> Jul  5 18:45:37 centos ldmd[21693] NOTE: child 21697 exited with status 10
> Jul  5 19:45:20 centos 129.82.225.8[21696] ERROR: pq_del_oldest:
> signature e79ebc1fa6583db1f39a575fba1d1b32: Not Found
> Jul  5 19:45:20 centos 129.82.225.8[21696] ERROR: pq_insert() failed:
> Invalid argument:     1084 20140705194329.479 IDS|DDPLUS 37525601
> WWUS86 KSGX 051943 /pSPSSGX
> Jul  5 19:45:20 centos 129.82.225.8[21696] NOTE: Exiting
> Jul  5 19:45:20 centos ldmd[21693] NOTE: child 21696 exited with status 10
> 
> 3. The status of the LDM shows:
> 
> ldm 21693     1  0 Jul02 ?        00:00:03 ldmd -I 0.0.0.0 -P 388 -M 256
> -m 3600 -o 3600 -q /home/ldm/var/queues/ldm.pq /home/ldm/etc/ldmd.conf
> 
> What do you suggest to solve this problem?
> 
> Many thanks,
> Evan

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JWV-419912
Department: Support LDM
Priority: Normal
Status: Closed