I agree. Found this after beating my head against the wall with no ingest into
ldm. Its multicast, ldm and centos should theoretically just find it.
Ray Weber
MA Skywarn
Sent from my T-Mobile 4G LTE Device
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Gilbert Sebenste <gilbert@xxxxxxxxxxxxxxxx>
Sent: Sunday, March 29, 2020 1:32:11 PM
To: Jack Snodgrass <jack@xxxxxxxxxxxxxx>
Cc: Raymond Weber <admin@xxxxxxxx>; ldm-users@xxxxxxxxxxxxxxxx
<ldm-users@xxxxxxxxxxxxxxxx>
Subject: Re: [ldm-users] noaaportIngester config issues
And boom, I have put in a ticket to UNIDATA LDM support and UNIDATA NOAAport
support to document this. Hopefully there is a much easier way to do this as
before, where you don't have to tell CentOS and LDM where the packets are and
should be; LDM just "knows".
This issue is not happening on the latest version of Debian.
Gilbert
On Mar 29, 2020, at 9:51 AM, Jack Snodgrass <jack@xxxxxxxxxxxxxx> wrote:
BOOM... drop the mike....
that was it. Thanks..... maybe someone should document that somewhere.
I am sure that I will have more questions but for now.. I have a ton of files
getting stored in var/data now...
var/data/WI/KWAL/14/SR20.wmo
var/data/WI/KWAL/14/SR30.wmo
var/data/WV/KWAL/14/SR20.wmo
var/data/AU/YBBN/14/SP33.wmo
var/data/AU/KWBC/14/SP31.wmo
var/data/MR/KWAL/14/SO10.wmo
var/data/AF/KWBC/14/SA36.wmo
var/data/RA/RUHB/12/UE03.wmo
var/data/HK/VHHH/14/SE40.wmo
so I can start figuring out what to do with this next.
Thanks
- jack
On 3/29/20 9:43 AM, Raymond Weber wrote:
There is an odd quirk with Centos, and here is how I got around it.
The destination IP on the noaaport multicast is a 10.0.9.51 IP.
So I configured an IP in that range on the ethernet connected to the Novra.
ifconfig em4:1 10.0.9.44 netmask 255.255.255.0
Replace em4 with your interface.
Then, In the noaaport ingester command in ldmd.conf, I did this:
EXEC "noaaportIngester -v -m 224.0.1.3 -I 10.0.9.44"
just added the -I at the end to force it to that interface
And, it works fine now. Several installations ago I had to start doing that.
Ray Weber
MA Skywarn
________________________________
From: ldm-users
<ldm-users-bounces@xxxxxxxxxxxxxxxx><mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx>
on behalf of Jack Snodgrass <jack@xxxxxxxxxxxxxx><mailto:jack@xxxxxxxxxxxxxx>
Sent: Sunday, March 29, 2020 10:36 AM
To: ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx>
<ldm-users@xxxxxxxxxxxxxxxx><mailto:ldm-users@xxxxxxxxxxxxxxxx>
Subject: Re: [ldm-users] noaaportIngester config issues
I did the sudo password thing when the make requested it....
per your instructions I ran:
make root-actions
chown root /home/ldm/bin/ldmd
chmod 4754 /home/ldm/bin/ldmd
chown root /home/ldm/bin/hupsyslog
chmod 4754 /home/ldm/bin/hupsyslog
if test -f /home/ldm/bin/noaaportIngester; then \
chown root /home/ldm/bin/noaaportIngester; \
chmod 4754 /home/ldm/bin/noaaportIngester; \
fi
if test -f /home/ldm/bin/fileIngester; then \
chown root /home/ldm/bin/fileIngester; \
chmod 4754 /home/ldm/bin/fileIngester; \
fi
if test -f /home/ldm/bin/dvbs_multicast; then \
chown root /home/ldm/bin/dvbs_multicast; \
chmod 4754 /home/ldm/bin/dvbs_multicast; \
fi
./ensureRpcEntry
./ensureServicesEntry
I then ran
ldmadmin stop
ldmadmin start
and let it run for a bit.
ldmadmin restart
reset the logs and I still ended up with:
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Received frames:
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Mean Rate 0/s
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Missed frames:
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE % -nan
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Full FIFO:
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE % -nan
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Products:
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Inserted 0
20200329T142722.809088Z noaaportIngester[21441]
noaaportIngester.c:reportStats:784 NOTE Mean Rate 0/s
values for everything.
I hae NO IDEA if:
EXEC "noaaportIngester -x -m 224.0.1.1 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.2 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.3 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.4 -l /home/ldm/var/logs/ldmd.log"
is correct... I don't know how the s300 novra modem is setup. Could those
224.x.x.x addresses be wrong for our modem.
The S300 was setup years ago... it's been working with the CENTOS 5 box with
minimal changes over the years.
I tried to use the cmcs command to login to the 192.168.1.2 modem but the
default pw does not work and no one seems to know that the pw is. I was
thinking I could verify the configureation it has if I could get logged into
that device.
Is the 224.0.1.1 address a 100% certainty or could it need to be something else?
- jack
On 3/29/20 8:52 AM, Patrick L. Francis wrote:
it sounds as if your configure script did not have access to superuser
privileges... do a make root-actions to finish the install
i.e. su root -c 'make root-actions'
from the install directory
cheers,
--patrick
------ Original Message ------
From: "Jack Snodgrass" <jack@xxxxxxxxxxxxxx<mailto:jack@xxxxxxxxxxxxxx>>
To: ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx>
Sent: 3/29/2020 9:40:43 AM
Subject: [ldm-users] noaaportIngester config issues
First of all LDM is toally new to me. I am try to set this up for a friend.
I have a new LDM 6.13.12.42 installation.
I used the latest from github - https://github.com/Unidata/LDM.git.
I used:
./configure --with-noaaport --with-ingester --with-retrans --with-gribinsert
to configure. I am in a Centos 7 server.
The main goal of this system is to receive data from a noaaport reciver / modem.
The system reports:
cmcs -list
S300 IP address: 192.168.1.2 MAC: 00-06-76-05-02-4d
so I 1) know that the server sees the modem and 2) it is a Novra type modem:
http://www.satcomsource.com/Novra-S300-Technical-User-Manual.pdf
Currently we have an OLD Centos 5 system with propriatary noaaport software
that works with that modem. The Centos 5 system is having some issues so we're
looking to move the noaaport receive process to a newer system.
The modem is on a 192.168.1.x network that is just setup for the modem and the
servers receiving data from it.
According to:
https://www.unidata.ucar.edu/software/ldm/ldm-current/utilities/noaaport/index.html
I need to setup:
sysctl -w net.ipv4.ipfrag_max_dist=4096
sysctl -w net.ipv4.conf.default.rp_filter=2
sysctl -p
which I have done. I have disabled selinux and he firewall on the Centos 7 box.
I have verified that the
/proc/sys/net/ipv4/conf/default/rp_filter
and
/proc/sys/net/ipv4/ipfrag_max_dist
are the expected values after the system has booted.
If I run
tcpdump -n -i enp7s0f1 | grep 192.168.1.
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp7s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes
08:30:55.413481 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
08:30:55.905608 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
08:30:56.412681 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
08:30:56.900813 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
I see data from the S300 modem... I assume that is the Multcast Data that the
modem sends.. but that is guess on my part.
I have tried server different instances ( different values ) for:
EXEC "noaaportIngester -x -m 224.0.1.1 -I 192.168.1.99 -l
/home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.2 -I 192.168.1.99 -l
/home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.3 -I 192.168.1.99 -l
/home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.4 -I 192.168.1.99 -l
/home/ldm/var/logs/ldmd.log"
or
EXEC "noaaportIngester -x -m 224.0.1.1 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.2 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.3 -l /home/ldm/var/logs/ldmd.log"
EXEC "noaaportIngester -x -m 224.0.1.4 -l /home/ldm/var/logs/ldmd.log"
but when I do ldmadmin start or ldmadin restart the logs show:
------------
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Ingestion Statistics:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Since Previous Report (or Start):
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Duration
PT4M59.454614S
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Raw Data:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Octets 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Mean Rate:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Octets 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Bits 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Received frames:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Mean Rate 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Missed frames:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE % -nan
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Full FIFO:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE % -nan
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Products:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Inserted 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Mean Rate 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Since Start:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Duration
PT4M59.454614S
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Raw Data:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Octets 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Mean Rate:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Octets 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Bits 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Received frames:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Mean Rate 0/s
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Missed frames:
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE Number 0
20200329T125412.495533Z noaaportIngester[20413]
noaaportIngester.c:reportStats:784 NOTE % -nan
20
and never any data received from the modem.
netstat -ang | grep -v ff
reports:
IPv6/IPv4 Group Memberships
Interface RefCnt Group
--------------- ------ ---------------------
lo 1 224.0.0.1
enp7s0f0 1 224.0.0.1
enp7s0f1 1 224.0.1.4
enp7s0f1 1 224.0.1.2
enp7s0f1 1 224.0.1.3
enp7s0f1 1 224.0.1.1
enp7s0f1 1 224.0.0.1
so .. what am I missing in order to received data from this S300 noaaport
receiver?
On the OLD / WORKING system we have:
[PARAMS]
NOAAPORT_BUF_SIZE = 1,1,1,1
LOGMASK = 0x06,5
NUM_USERS = 4
NUM_SATCOMM_BOARDS = 1
SAVE_HDLC_FRAMES = {1,0}, {2,0}, {3,0}, {4,0}
NOAAPORT_DATA_STREAM = DVB_NWSTG,DVB_GOES,DVB_NWSTG2,DVB_OCONUS
MULTICAST_INTERFACE = 192.168.1.4
On the new LDM system... I didn't configure: MULTICAST_INTERFACE =
192.168.1.99 ( the new box is 192.168.1.99 ) anyplace.
any one have any ideas on why the LDM noaaportIngester stuff doesn't appear to
be ingesting?
- jack
--
jack - Southlake Texas - http://mylinuxguy.net<http://mylinuxguy.net/>
--
jack - Southlake Texas - http://mylinuxguy.net<http://mylinuxguy.net/> -
817-601-7338
--
jack - Southlake Texas - http://mylinuxguy.net<http://mylinuxguy.net/> -
817-601-7338
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
https://www.unidata.ucar.edu/mailing_lists/
