[IDD #KUD-512290]: Backup NOAAPort source ?

Hi Rosie, et. al,

re: 
> Sounds good about the script install.

Very good.

Comment and question:

- while setting up our NOAAport monitoring scripts on np1 and np2, I
  found that there are thousands (>67K) of mail messages in 'ldm's
  mailbox literally all of which were being generated because of
  the 'echo `which cmcs`' line in the 'nplog_rotate_np[12]' script
  in ~ldm

  I took a look at about 30 of these messages, and they have no value
  that I can think of.

  The question is if I can delete these mail messages?

Next, both np1 and np2 now have once-per-minute, cron-initiated Novra
stats logging being saved in the ~ldm/logs/novras300.log file.  There
are also crontab entries that will rotate the log files once-per-week.
The contents of the novras300.log file look like:

20160504.1939 DVBS2 1110.0 30.001 2/3_16PSK 0 On 18 On On 0/s 0.0000e+00 14.0dB 
100dBm   0.020 -100.985  173.39  43.53
20160504.1940 DVBS2 1110.0 30.001 2/3_16PSK 0 On 18 On On 0/s 0.0000e+00 14.0dB 
100dBm   0.020 -100.985  173.39  43.53
20160504.1941 DVBS2 1110.0 30.001 2/3_16PSK 0 On 18 On On 0/s 0.0000e+00 14.4dB 
100dBm   0.020 -100.985  173.39  43.53
20160504.1942 DVBS2 1110.0 30.001 2/3_16PSK 0 On 18 On On 0/s 0.0000e+00 14.4dB 
100dBm   0.020 -100.985  173.39  43.52
20160504.1943 DVBS2 1110.0 30.001 2/3_16PSK 0 On 18 On On 0/s 0.0000e+00 14.4dB 
100dBm   0.020 -100.985  173.39  43.52

In case anyone is worried about interrogating the Novra S300N once-per-minute I
can say that our testing has shown that this high of a sampling frequency being
done by a single machine has little to no effect on the S300N's ability to
ingest data without error.

Next, I am implementing our scripts that count the number of Gap messages seen
"today".  When finished (meaning properly adjusted for your environment), this
gapstat gathering will run out of cron once-per-hour.  The purpose gathering
Gap stats is so that the ingest quality can be easily ascertained and compared
with the other NOAAPort ingest sites that are powering the IDD.  For example,
here is a listing of the last 2 days of ingest stats on our and LSU/SRCC's
machines:

Gap stats for the past 2 days:

20160503:
  chico:: 20160503.224001: nGap:    210 nFrame:       1055 nGsec:    15 nGmin:  
 12

   leno:: 20160503.230901: nGap:    207 nFrame:        937 nGsec:    16 nGmin:  
 13
 jackie:: 20160503.235933: nGap:   2226 nFrame:      29300 nGsec:  1469 nGmin:  
665
  burns:: 20160503.175732: nGap:    573 nFrame:       5379 nGsec:   245 nGmin:  
159

mistral:: 20160502.204014: nGap:      6 nFrame:         17 nGsec:     4 nGmin:  
  4

20160504: up to 13:48 MDT/19:48 UTC
  chico:: 20160504.165502: nGap:     36 nFrame:  896544723 nGsec:    22 nGmin:  
 15

   leno:: 20160504.154626: nGap:     31 nFrame:  896544684 nGsec:    17 nGmin:  
 12
 jackie:: 20160504.190001: nGap:   1370 nFrame:  896561339 nGsec:  1067 nGmin:  
559
  burns:: 20160504.120900: nGap:    201 nFrame:  800755359 nGsec:   110 nGmin:  
 83

mistral:: 20160504.135524: nGap:    800 nFrame:  759608390 nGsec:   266 nGmin:  
107

The machines in question are:

leno    - Unidata "operational" NOAAPort ingester
chico   - Unidata "operational" NOAAPort ingester
jackie  - Unidata test NOAAPort ingester
burns   - Unidata test NOAAPort ingester
mistral - LSU/SRCC "operational" NOAAPort ingester

One quick comment is in order:

- when the number of missed frames (nFrame) is as high as we are seeing for
  today, it often (typically?) means that the SBN uplink has changed from
  primary to backup or visa versa

re:
> To keep you up to date, Dave had some trials and tribulations again
> today.  Since switching LNB's to the spare did not change things the
> other day he put the original LNB back in this morning. Long story short
> is that really messed things up, so he put the spare LNB back on and we
> were still messed up (messed up = c/n ok but signal low and getting gap
> errors).
> 
> So, about 1730z he put the original LNB back in (still messed up as half
> expected) so he swapped the cable between the splitter and LNB input.
> 
> Carrier to noise is now good at 14.3, but the signal strength being
> reported is +100.   The last Gap error at this time was at 1721z and
> data seems to be flowing.

Hmm... Just to see if would have any effect, I rebooted the Novra S300N
connected to np2.  The indicated signal strength stayed at 100 dBm which
is obviously wrong.  As you note, the C/N looks consistent, and is good
enough to not encounter too many Gap messages.

Please let me know if it is OK to delete the thousands of emails in 'ldm's
mailbox on both np1 and np2...

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: KUD-512290
Department: Support NOAAPORT
Priority: Normal
Status: Closed