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

[NOAAPORT #GGP-872890]: New Noaaport server with ldm

Hi Heather,

re:
> Thank you so much for helping me out with this.

No worries.  I truly wish that we could have figured out what
was happening on your system!

re:
> I think I am going to give up on this and start fresh with a
> new installation. I will probably go back to Centos 6 so I can
> grab the configuration files from my previous working install!

This is exactly what I would do :-)

Please let us know if your re-installation/configuration results
in a fully functional NOAAPort ingest system... or not!

> Heather
> 
> Sent from my iPhone
> 
> > On Feb 24, 2019, at 6:03 PM, Unidata NOAAPORT Support <address@hidden> 
> > wrote:
> >
> > Hi Heather,
> >
> > Well, the latest test that I could conceive of to get things working
> > on npingest failed.  I am sorry to say that I am completely out of
> > ideas.
> >
> > If I were in your position, I would reload the OS on npingest and not
> > try to migrate over any configurations that were in place from your
> > previous NOAAPort ingest instance.
> >
> > The procedure I would follow is:
> >
> > - load a fresh instance of CentOS
> >
> >  As I said in a previous email, it will be up to you if you load
> >  CentOS 7.x or 6.10 as both _should_ work fine.
> >
> > - create an 'ldm' account
> >
> >  Download, build and install the latest LDM release.
> >
> >  As you found out, you may need to load in some packages that
> >  will be needed to build the LDM.
> >
> > - after the LDM v6.13.7 is built and installed, I would first:
> >
> >  - configure the firewall on the newly built OS to either be
> >    completely disabled, or to make sure that all traffic is
> >    allowed from the Ethernet interface to which your Novra
> >    S300N is connected
> >
> >  - immediately after this, I would use 'tcpdump' to see if
> >    you see the traffic from the Novra S300N hitting the
> >    Ethernet interface
> >
> >    NB: if all is well, we do not think you will see the
> >    'bad length' indications in the 'tcpdump' output!
> >
> >    <as 'root'>
> >
> >    tcpdump -c 20 -i <ethernet interface>
> >
> >    If this goes well, only then would I move forward.
> >
> > - setup the multicast routing
> >
> >  This does not have to be done before the 'tcpdump' test
> >  since 'tcpdump' is looking at the raw device.
> >
> > - setup the kernel parameters for DVBS ingest and ip
> >  fragmentation
> >
> >  Do this as per our emails, not what you see before reloading
> >  an OS!
> >
> > Please let us know what you decide to do!
> >
> > We will contact you if we have a brainstorm overnight!!
> >
> > 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: GGP-872890
> > Department: Support NOAAPORT
> > 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.
> >
> >
> 
> 

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: GGP-872890
Department: Support NOAAPORT
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.