[LDM #VVJ-331218]: LDM 6.11.7 Errors - exit LDM Not starting

Russ,

> Hey good morning Steve,
> 
> I get an error issuing the kill command below.  but let me explain a few
> things.
> [ldm@fos2 logs]$ kill - USR2 'cat $HOME/ldmd.pid'
> -bash: kill: : invalid signal specification

The first kill(1) argument should be "-USR2"; not "- USR2".

> We have two FOS servers (3.80 is primary and 3.120 is backup).  I issued
> the above kill command on the backup FOS.  I will be doing all testing
> on the Backup FOS (3.120).

Sounds like a good idea.

> I have two GEOPROD servers ( 2.197 is GEOPROD4 (PRIMARY) and 2.173 is
> GEOPROD4T (BACKUP) )
> 
> The notifyme from the backup (geoprod4t) to the FOS Backup seems to work
> OK but I see in the ldmd.log:
> 
> Sep 23 12:33:50 fos2 dvbs_multicast[4844] ERROR: Gap in SBN last
> 93071932, this 93071934
> Sep 23 12:33:54 fos2 dvbs_multicast[4844] ERROR: Gap in SBN last
> 93072682, this 93072684

The "Gap" messages indicate that the NOAAPORT ingest program, 
dvbs_multicast(1), noticed a gap in the data-packets being broadcast by the 
satellite. Such a loss results in lost data and, potentially, a lost 
data-product.

We're seeing the same "Gap" messages here and are working to reduce them.

> Sep 23 12:33:59 fos2 x.x.x.173(noti)[13998] ERROR: SDUS84 KBRO 231231
> /pN2HBRO !nids/: RPC: Unable to receive
> Sep 23 12:33:59 fos2 x.x.x.173(noti)[13998] ERROR: pq_sequence
> failed: Input/output error (errno = 5)

The ERROR messages from the "noti" process are due to the termination of the 
corresponding notifyme(1) process on a downstream host (x.x.x.173). They may be 
safely ignored.

> Sep 23 12:34:02 fos2 dvbs_multicast[4852] ERROR: Gap in SBN last
> 61841861, this 61841863
> Sep 23 12:34:02 fos2 dvbs_multicast[4844] ERROR: Gap in SBN last
> 93073926, this 93073928
> Sep 23 12:34:02 fos2 dvbs_multicast[4852] ERROR: Gap in SBN last
> 61841869, this 61841871
> Sep 23 12:34:02 fos2 dvbs_multicast[4844] ERROR: Gap in SBN last
> 93073977, this 93073979
> 
> The GEOPROD4 Primary does not work to the FOS Backup, and neither
> GEOPROD works to the FOS Primary.
> 
> So, I guess if we can get the verbose logging activated, we may see more
> info to assist in debugging.

Let me know what you discover.

> Thanks
> Russ

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VVJ-331218
Department: Support LDM
Priority: Normal
Status: Closed