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

[LDM #TCW-702523]: downstream LDM server not receiving all data (e.g. nexrad) from local LDM/NOAAPORT ingest systems



Hi Gregory,

> Thank you so much to both of you for the quick detailed replies!  Thanks
> for pointing out I needed a NEXRAD3 REQUEST line and also the other
> details.
> 
> I wanted to work on the SBN2 issue, and stopped LDM on SBN2 and now the
> noaaportingester processes do NOT stay running, they exit out a few seconds
> after LDM starts.  With errors like the following (compete errors are at
> bottom of this thread):
> 
> 20200902T224443.554194Z ldmd[19145]                 *ldmd.c:reap:177 *
> NOTE  *child 19151 exited with status 1: noaaportIngester -I
> 10.0.5.50 -m 224.0.1.3 -n -l /home/ldmcp/logs/3.nmc2.log*
> 
> The noaaportIngestor log entries (bottom of thread has all logs) have a few
> interesting entries:
> 
> 20200902T224441.998338Z noaaportIngester[19151]     noaaportIngester.c:
> *spawnProductMaker*:546 *ERROR Operation not permitted*
> 
> 20200902T224441.998388Z noaaportIngester[19151]     noaaportIngester.c:
> *spawnProductMaker*:546 *ERROR Couldn't start product-maker thread*

Wow! This error is the result of noaaportIngester not being able to create a 
new thread via pthread_create(). To say this shouldn't happen is an 
understatement.

Is there something about the VM that prevents threads from being created? 
What's the VM's O/S?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TCW-702523
Department: Support LDM
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.