[IDD #PMD-399578]: Nexrad 2 Data Question

Hi Justin,

re:
> My apologies for the mix-up. Please disregard what I mentioned recarding
> the "ddcraft_move" file. I was looking at the wrong thing.

OK.

re:
> I am still running into an error on my ldm feed with the NEXRAD2 data. I
> get " ERROR: Notification specified but shared memory is not available."
> 
> This data is being ingested into an edex server.
> 
> [ldm@localhost ~]$ tail -f var/logs/ldmd.log
> Mar 10 02:08:18 localhost ldm.tamu.edu[4945] NOTE: Starting Up(6.11.5): 
> ldm.tamu.edu:388 20150310050818.350 TS_ENDT {{NEXRAD2,  "(MLB|TBW)"}}
> Mar 10 02:08:18 localhost ldm.tamu.edu[4945] NOTE: LDM-6 desired 
> product-class: 20150310050818.351 TS_ENDT {{NEXRAD2,  "(MLB|TBW)"},{NONE, 
> "SIG=79fb85d12cfb27770cec0e5d2ede9ed3"}}
> Mar 10 02:08:18 localhost pqact[4941] NOTE: Starting Up
> Mar 10 02:08:18 localhost rtstats[4944] NOTE: Starting Up (4939)
> Mar 10 02:08:18 localhost pqact[4943] NOTE: Starting Up
> Mar 10 02:08:18 localhost pqact[4941] NOTE: Starting from insertion-time 
> 2015-03-10 06:07:52.477765 UTC
> Mar 10 02:08:18 localhost pqact[4943] NOTE: Starting from insertion-time 
> 2015-03-10 06:07:52.477765 UTC
> Mar 10 02:08:18 localhost edexBridge[4942] NOTE: Starting Up
> Mar 10 02:08:18 localhost edexBridge[4942] NOTE: Sent 1 messages (0 at the 
> end of the queue, 1 normally).
> Mar 10 02:08:18 localhost ldm.tamu.edu[4945] NOTE: Upstream LDM-6 on 
> ldm.tamu.edu is willing to be a primary feeder
> Mar 10 02:12:46 localhost pqact[4943] *ERROR: Notification specified but 
> shared memory is not available.*
> Mar 10 02:12:46 localhost pqact[4943] NOTE: Filed in 
> "/awips2/data_store/level2/KMLB/20150310/.tmp/Level2_KMLB_20150310_061245.ar2v":
>  8932 20150310061246.485 NEXRAD2 947001 
> L2-BZIP2/KMLB/20150310061245/947/1/S/V06/0

This is the first time that I have seen a "shared memory is not available" 
ERROR.
It most likely means that your machine has exhausted the amount of shared
memory that was allocated.  If this is the case, it is possible/likely that
there are a number of allocated shared memory segments that need to be
cleaned out.  You can check for this with the 'ipcs' utility of Linux:

% ipcs

Look for shared memory segments that seem to be orphaned, and then remove them
using 'ipcrm'.  Cleaning out orphaned shared memory segments in most cases
will resolve problems related to shared memory allocation.  If it does not,
then a reboot of your system is the best next step.

The other thing that you will likely want to check is how much shared
memory your system is configured with.  A good resource for setting
shared memory is:

Chapter 7. Setting Shared Memory - Red Hat Customer Portal
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Tuning_and_Optimizing_Red_Hat_Enterprise_Linux_for_Oracle_9i_and_10g_Databases/chap-Oracle_9i_and_10g_Tuning_Guide-Setting_Shared_Memory.html

Increasing the amount of shared memory available is something that most
McIDAS-X users do if they run McIDAS sessions with a lot of display
frames, so fiddling with shared memory is not an unusual topic for
Unidata users.

NB:

If you continue to experience the "shared memory is not available" ERROR in
your LDM log file, please open an inquiry by sending a new email to
address@hidden.

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: PMD-399578
Department: Support IDD
Priority: Normal
Status: Closed