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

[LDM #QEL-970387]: LDM at NOAA



Hi Russ,

re:
> I have re-installed LDM using
> http://www.unidata.ucar.edu/software/ldm/ldm-6.11.7/basics/source-install-steps.html
> ..... still nada....

We do not believe that the problem is with the LDM.

re:
> ./configure --enable-logging=local0 --localstatedir=/data/ldm
> --disable-max-size --with-noaaport
> make install
> 
> address@hidden src]$ su root -c 'make root-actions'
> Password:
> chown root /home/ldm/ldm-6.11.7/bin/ldmd
> chmod 4755 /home/ldm/ldm-6.11.7/bin/ldmd
> chown root /home/ldm/ldm-6.11.7/bin/hupsyslog
> chmod 4755 /home/ldm/ldm-6.11.7/bin/hupsyslog
> if test -f /home/ldm/ldm-6.11.7/bin/noaaportIngester; then \
> chown root /home/ldm/ldm-6.11.7/bin/noaaportIngester; \
> chmod 4755 /home/ldm/ldm-6.11.7/bin/noaaportIngester; \
> fi
> if test -f /home/ldm/ldm-6.11.7/bin/dvbs_multicast; then \
> chown root /home/ldm/ldm-6.11.7/bin/dvbs_multicast; \
> chmod 4755 /home/ldm/ldm-6.11.7/bin/dvbs_multicast; \
> fi
> ./ensureSyslogEntry local0 /etc/rsyslog.conf /home/ldm/logs/ldmd.log
> ./ensureRpcEntry
> ./ensureServicesEntry

OK, looks good.

re:
> address@hidden src]$ ldmadmin start
> The product-queue is OK.
> Checking pqact(1) configuration-file(s)...
> /home/ldm/etc/pqact.conf: syntactically correct
> Checking LDM configuration-file (/home/ldm/etc/ldmd.conf)...
> Starting the LDM server...

OK.

re:
> rpcinfo -p
> program vers proto   port  service
> 100000    4   tcp    111  portmapper
> 100000    3   tcp    111  portmapper
> 100000    2   tcp    111  portmapper
> 100000    4   udp    111  portmapper
> 100000    3   udp    111  portmapper
> 100000    2   udp    111  portmapper
> 300029    6   tcp    388  ldmd
> 300029    5   tcp    388  ldmd

Looks good.

re:
> net.ipv4.ipfrag_max_dist = 4096
> net.ipv4.conf.default.rp_filter = 2

Our setting for net.ipv4.ipfrag_max_dist is different than yours:

#
# DVBS multicast fragment reassembly 
#
net.ipv4.ipfrag_max_dist = 0

This difference would not prevent your LDM from seeing packets from your
eth1 interface (where your Novra S300N is plugged in), but it might
cause you to see more errors.

re:
> ps -ef
> ldm      10390     1  0 18:53 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M 256 
> -m 3600 -o 3600 -q /data/ldm/queues/ldm.pq /home/ldm/etc/ldmd.conf
> ldm      10392 10390  0 18:53 ?        00:00:00 pqact
> root     10393 10390  0 18:53 ?        00:00:00 dvbs_multicast -m 224.0.1.1
> ldm      10394 10390  0 18:53 ?        00:00:00 readnoaaport -m 224.0.1.1 -n 
> -u 3
> root     10395 10390  0 18:53 ?        00:00:00 dvbs_multicast -m 224.0.1.2
> ldm      10396 10390  0 18:53 ?        00:00:00 readnoaaport -m 224.0.1.2 -n 
> -u 4
> root     10397 10390  0 18:53 ?        00:00:00 dvbs_multicast -m 224.0.1.3
> ldm      10398 10390  0 18:53 ?        00:00:00 readnoaaport -m 224.0.1.3 -n 
> -u 5
> root     10399 10390  0 18:53 ?        00:00:00 dvbs_multicast -m 224.0.1.4
> ldm      10400 10390  0 18:53 ?        00:00:00 readnoaaport -m 224.0.1.4 -n 
> -u 6

FYI: there are more channels in the NOAAPort boadcast that you will eventually
have to configure for (i.e., 224.0.1.5 - 224.0.1.8).  Not having these will not
have any effect on your ingestion, however.

re:
> address@hidden src]$ ldmadmin watch
> (Type ^D when finished)

Earlier you sent us the output of 'netstat -rn' on your
ingest machine:

 address@hidden ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask         Flags MSS Window irtt Iface
224.0.1.3   0.0.0.0 255.255.255.255 UH    0   0      0    eth1
224.0.1.2   0.0.0.0 255.255.255.255 UH    0   0      0    eth1
224.0.1.1   0.0.0.0 255.255.255.255 UH    0   0      0    eth1
224.0.1.4   0.0.0.0 255.255.255.255 UH    0   0      0    eth1

Here is the output from 'netstat -rn' on one of our CentOS 6.6 x86_64
ingest machines:

~: netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
128.117.156.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
224.0.0.0       192.168.1.7     240.0.0.0       UG        0 0          0 eth1
0.0.0.0         128.117.156.251 0.0.0.0         UG        0 0          0 eth0

We setup our static routing (again, on a CentOS machine) by creating a static 
routes
file:

~: cat /etc/sysconfig/static-routes 
any net 224.0.0.0 netmask 240.0.0.0 gw 192.168.1.7 dev eth1

This works for us because the network scripts on RedHat-variant machines check
to see if the file /etc/sysconfig/static-routes exists, and if it does, it reads
it.

I have to think that the difference in your 'netstat -rn' and ours is the key
to why your LDM is not seeing the traffic on your eth1 interface.

We will get together with our system administrator to review your settings
to see if the differences between yours and ours should have any effect.

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: QEL-970387
Department: Support LDM
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.