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

RE: (#WCA-4105061) LDM 6.15.0 on Red Hat Enterprise Linux release 8.10 on VMware



-#-#- Please reply above this line -#-#-

Your ticket #WCA-4105061 has been updated. You can reply to this email above or review the ticket by going to:
https://support.unidata.ucar.edu/tickets/view/WCA-4105061?token=ebaeb59ab67b85d1d61ab2dd4f4ebf0d754637ec

Stonie Cooper
Staff - Tuesday 10th September 2024 3:15 PM

James - good so far!  Next up, I'm guessing you had already done this, but just for my sake . . .

 

ps -ef | grep jgerlach

 

Just to make sure you have at least one instance of the noaaportIngester running, along with at least one instance of ldmd.

 

Is there any logs showing up at all in /opt/local/home/jgerlach/var/logs/nwstg.log?

 

Let us step up the logging a bit.  In your ldmd.conf file, swap out the "-v" for your EXEC on the keep_running for the noaaportIngester to "-n" - this is more verbose . . . actually logs every product inserted in the queue (or attempted).

 

Which reminds me.  Do an "ldmadmin stop".  Then do the above "ps -ef | grep jgerlach" and make sure all the processes actually stopped.  If the noaaportIngester gets hung up on an empty socket, it may not exit, and will hang and not let a new instance fire up . . . so make sure all of the ldm processes did exit.  Then do an ldmadmin start to fire it back up.

 

And, finally . . . . when you do an "ldmadmin watch" - nada, correct?  Or is it showing data flowing?

Stonie Cooper, PhD

Software Engineer III

NSF Unidata Program Center

University Corporation for Atmospheric Research

I acknowledge that the land I live and work on is the traditional home of The Chahiksichahiks (Pawnee), The Umoⁿhoⁿ (Omaha), and The Jiwere (Otoe).


Gerlach, James
User - Tuesday 10th September 2024 2:57 PM

Stonie, how nice it is to hear from you again. Thank you for taking my service request.
Packet capture with tcpdump shows what appears to be a steam of data from Novra.

# Network configuration
On the Linux VM, we have interface ens224
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:a3:56:d9 brd ff:ff:ff:ff:ff:ff
    altname enp19s0
    inet 10.17.228.20/24 brd 10.17.228.255 scope global noprefixroute ens224
       valid_lft forever preferred_lft forever
    inet6 fe80::8321:cef7:3278:b6ed/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

The Novra S300N has IP address 10.17.228.30

# Status of S300N
The cmcs utility appears to indicate that the satellite receiver is ok.

CMCS 10.17.228.30> show satellite
        Satellite Interface Settings:

        Receiver MAC Address:   00-06-76-05-01-bf
        Receiver Mode:          DVBS2
        Frequency:              1130.0 MHz
        Symbol Rate:            30.000 Msps
        ModCod:                 2/3 16APSK
        Gold code:              0
        Input Stream Filter:    On
        Input Stream ID:        18

        Signal Lock:            On
        Data Lock:              On
        Uncorrectable Rate:     0/Second
        Packet Error Rate:      0.0000e+00

        Carrier to Noise C/N:   15.3dB
        Signal Strength:        -47 dBm

# Packet Capture
# Here I capture the traffic when "running bin/ldmadmin start".
# The igmp query occurred prior to running "start".

[root@metbox6 ~]# tcpdump -n -nn -c20 -i ens224 port not 6516
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens224, link-type EN10MB (Ethernet), capture size 262144 bytes
16:48:29.577207 IP 10.17.228.1 > 224.0.0.1: igmp query v2
16:48:42.619613 IP 10.17.228.20 > 224.0.1.1: igmp v2 report 224.0.1.1
16:48:42.952022 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.952088 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.952196 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.952439 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.952557 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.952677 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.952797 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.952926 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.953042 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.953325 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.953461 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.953585 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.953686 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.953828 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.954586 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.954602 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:48:42.954606 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:48:42.954611 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
20 packets captured
22 packets received by filter
0 packets dropped by kernel

# Additional packet capture with ldmd running
[root@metbox6 ~]# tcpdump -i ens224 -n -n -c 100
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens224, link-type EN10MB (Ethernet), capture size 262144 bytes
16:54:36.079422 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4092 > 1472
16:54:36.079587 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.079698 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.079846 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.079982 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.080105 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.080274 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.080421 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.080539 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.089079 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.089210 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.089318 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.089446 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.089649 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.089762 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.089889 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.090026 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.090161 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.090374 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.090512 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.090627 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.090787 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.090933 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.091046 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.091242 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.091392 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.095017 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.097490 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.097620 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.097736 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.098104 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.098116 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.098211 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.098348 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.098565 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.098689 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.098810 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.098927 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.099068 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.099250 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.099489 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.099495 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.099688 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.099834 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.099948 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.100158 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.100297 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.100417 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.100541 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.100746 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.100852 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.100989 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.101125 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.102564 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.102716 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.102937 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.103063 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.103192 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.103346 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.103464 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.103618 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.103751 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.103864 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.104128 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.104254 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.104371 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.104492 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.104652 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.104756 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.104901 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.105035 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.105190 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.105397 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.105633 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.105641 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.105867 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.105992 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.107803 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.108013 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.108163 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.108271 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.108485 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.108622 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.108740 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.108860 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 1989 > 1472
16:54:36.108981 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.109132 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4092 > 1472
16:54:36.109282 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.109401 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.109529 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.109731 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.109845 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.109967 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, length 1193
16:54:36.110165 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4092 > 1472
16:54:36.110310 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.110423 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.110552 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 4032 > 1472
16:54:36.110753 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.112614 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
16:54:36.112752 IP 10.0.9.51.42419 > 224.0.1.1.1201: UDP, bad length 2238 > 1472
100 packets captured
101 packets received by filter
0 packets dropped by kernel

# Configuration of ldmd
[jgerlach@metbox6 ~]$ egrep -v '^#' etc/ldmd.conf
EXEC "keep_running noaaportIngester -v -m 224.0.1.1 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nwstg.log"
ALLOW   ANY     ^((localhost|loopback)|(127\.0\.0\.1\.?))$

I have also tried these, but they're currently commented out.
#EXEC "keep_running noaaportIngester -m 224.0.1.2 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/goes.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.3 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nwstg2.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.4 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/oconus.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.5 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.6 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.7 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.8 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.9 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.0.1.10 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/nother.log"
#EXEC "keep_running noaaportIngester -m 224.1.1.1 -I 10.17.228.20 -l /opt/local/home/jgerlach/var/logs/wxwire.log"

[jgerlach@metbox6 ~]$ bin/ldmadmin showsettings

        LDMHOME environment varriable is NOT set. Setting it to default!

LDMHOME:/opt/local/home/jgerlach

Setuid programs verification:

$ ls -l /opt/local/home/jgerlach
total 64
lrwxrwxrwx 1 jgerlach sfwmd    11 May 31 16:40 bin -> runtime/bin
-rw-r--r-- 1 jgerlach sfwmd  7002 Aug  5 10:25 commands
-rw-r--r-- 1 jgerlach sfwmd     0 Jun  5 13:02 err
drwxr-xr-x 2 jgerlach sfwmd  4096 Sep  4 16:30 etc
-rw-r--r-- 1 jgerlach sfwmd 11088 Jun 19 10:00 history.out
lrwxrwxrwx 1 jgerlach sfwmd    15 May 31 16:40 include -> runtime/include
drwxr-xr-x 7 jgerlach sfwmd    92 May 31 16:40 ldm-6.15.0
-rw-r--r-- 1 jgerlach sfwmd     8 Sep  4 16:22 ldmd.pid
lrwxrwxrwx 1 jgerlach sfwmd    11 May 31 16:40 lib -> runtime/lib
drwxr-xr-x 3 jgerlach sfwmd    29 Jun 18 18:09 opt
lrwxrwxrwx 1 jgerlach sfwmd    10 May 31 16:40 runtime -> ldm-6.15.0
drwxr-xr-x 3 jgerlach sfwmd   130 Aug 12 15:52 scratch
lrwxrwxrwx 1 jgerlach sfwmd    13 May 31 16:40 share -> runtime/share
lrwxrwxrwx 1 jgerlach sfwmd    11 May 31 16:40 src -> runtime/src
-rw-r--r-- 1 jgerlach sfwmd 33895 Jun  2 10:41 strace.out
drwxr-xr-x 5 jgerlach sfwmd    44 May 31 16:40 var

$ ls -l /opt/local/home/jgerlach/bin/
total 5032
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 afos -> pqing
-rwsr-xr-- 1 root     sfwmd 823576 May 31 16:40 blender
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 ddplus -> pqing
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 dds -> pqing
-rwxr-xr-x 1 jgerlach sfwmd     48 May 31 16:40 dvbs_goes
-rwsr-xr-- 1 root     sfwmd 432960 May 31 16:40 dvbs_multicast
-rwxr-xr-x 1 jgerlach sfwmd     40 May 31 16:40 dvbs_nwstg
-rwxr-xr-x 1 jgerlach sfwmd     40 May 31 16:40 dvbs_nwstg2
-rwxr-xr-x 1 jgerlach sfwmd     40 May 31 16:40 dvbs_oconus
-rwxr-xr-x 1 jgerlach sfwmd    650 May 31 16:40 ensureLdmhomeLinks
-rwxr-xr-x 1 jgerlach sfwmd    156 May 31 16:40 ensureRpcEntry
-rwxr-xr-x 1 jgerlach sfwmd    173 May 31 16:40 ensureServicesEntry
-rwxr-xr-x 1 jgerlach sfwmd   1700 May 31 16:40 ensureSyslogEntry
-rwxr-xr-x 1 jgerlach sfwmd    612 May 31 16:40 ensureVar
-rwxr-xr-x 1 jgerlach sfwmd  61024 May 31 16:40 feedme
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 feedtest -> pqing
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 hds -> pqing
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 hrs -> pqing
-rwsr-xr-- 1 root     sfwmd  22384 May 31 16:40 hupsyslog
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 ids -> pqing
-rwxr-xr-x 1 jgerlach sfwmd    558 May 31 16:40 keep_running
-rwxr-xr-x 1 jgerlach sfwmd  65907 May 31 16:40 ldmadmin
-rwsr-xr-- 1 root     sfwmd  90944 May 31 16:40 ldmd
-rwxr-xr-x 1 jgerlach sfwmd   7435 May 31 16:40 ldmfail
-rwxr-xr-x 1 jgerlach sfwmd  45560 May 31 16:40 ldmping
-rwxr-xr-x 1 jgerlach sfwmd  54128 May 31 16:40 ldmsend
-rwxr-xr-x 1 jgerlach sfwmd 305688 May 31 16:40 nbs_ingest
-rwxr-xr-x 1 jgerlach sfwmd   9012 May 31 16:40 netcheck
-rwxr-xr-x 1 jgerlach sfwmd    910 May 31 16:40 newlog
-rwxr-xr-x 1 jgerlach sfwmd  12006 May 31 16:40 noaaportBlender.py
-rwsr-xr-- 1 root     sfwmd 552008 May 31 16:40 noaaportIngester
-rwxr-xr-x 1 jgerlach sfwmd  64752 May 31 16:40 notifyme
-rwxr-xr-x 1 jgerlach sfwmd    481 May 31 16:40 nplog_rotate
-rwxr-xr-x 1 jgerlach sfwmd   6640 May 31 16:40 plotMetrics
lrwxrwxrwx 1 jgerlach sfwmd      5 May 31 16:40 pps -> pqing
-rwxr-xr-x 1 jgerlach sfwmd 269360 May 31 16:40 pqact
-rwxr-xr-x 1 jgerlach sfwmd  59216 May 31 16:40 pqcat
-rwxr-xr-x 1 jgerlach sfwmd  41464 May 31 16:40 pqcheck
-rwxr-xr-x 1 jgerlach sfwmd  51616 May 31 16:40 pqcopy
-rwxr-xr-x 1 jgerlach sfwmd  35848 May 31 16:40 pqcreate
-rwxr-xr-x 1 jgerlach sfwmd  59280 May 31 16:40 pqexpire
-rwxr-xr-x 1 jgerlach sfwmd 202584 May 31 16:40 pqing
-rwxr-xr-x 1 jgerlach sfwmd  75224 May 31 16:40 pqinsert
-rwxr-xr-x 1 jgerlach sfwmd  56928 May 31 16:40 pqmon
-rwxr-xr-x 1 jgerlach sfwmd  71968 May 31 16:40 pqsend
-rwxr-xr-x 1 jgerlach sfwmd 111664 May 31 16:40 pqsurf
-rwxr-xr-x 1 jgerlach sfwmd  62304 May 31 16:40 pq_test_insert
-rwxr-xr-x 1 jgerlach sfwmd 118664 May 31 16:40 pqutil
-rwxr-xr-x 1 jgerlach sfwmd 468480 May 31 16:40 readnoaaport
-rwxr-xr-x 1 jgerlach sfwmd    548 May 31 16:40 refresh_logging
-rwxr-xr-x 1 jgerlach sfwmd  29160 May 31 16:40 regex
-rwxr-xr-x 1 jgerlach sfwmd  56440 May 31 16:40 regutil
-rwxr-xr-x 1 jgerlach sfwmd   1958 May 31 16:40 rpmUserActions
-rwxr-xr-x 1 jgerlach sfwmd 123144 May 31 16:40 rtstats
-rwxr-xr-x 1 jgerlach sfwmd 114016 May 31 16:40 scour
-rwxr-xr-x 1 jgerlach sfwmd   4297 May 31 16:40 scour.sh
-rwxr-xr-x 1 jgerlach sfwmd   1396 May 31 16:40 showSettings
-rwxr-xr-x 1 jgerlach sfwmd   7399 May 31 16:40 syscheck
-rwxr-xr-x 1 jgerlach sfwmd 363104 May 31 16:40 testBlender
-rwxr-xr-x 1 jgerlach sfwmd  36752 May 31 16:40 uldbutil
-rwxr-xr-x 1 jgerlach sfwmd  34544 May 31 16:40 ulogger
-rwxr-xr-x 1 jgerlach sfwmd    315 May 31 16:40 updateGempakTables
-rwxr-xr-x 1 jgerlach sfwmd   1029 May 31 16:40 wasReceived

$ ldmadmin config

hostname:              metbox6.sfwmd.gov
os:                    Linux
release:               4.18.0-553.16.1.el8_10.x86_64
ldmhome:               /opt/local/home/jgerlach
LDM version:           6.15.0
PATH:                  /opt/local/home/jgerlach/ldm-6.15.0/bin:/opt/local/home/jgerlach/util:/opt/local/home/jgerlach/ldm-6.15.0/bin:/opt/local/home/jgerlach/util:/opt/local/home/jgerlach/.local/bin:/opt/local/home/jgerlach/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin
LDM conf file:         /opt/local/home/jgerlach/etc/ldmd.conf
pqact(1) conf file:    /opt/local/home/jgerlach/etc/pqact.conf
scour(1) conf file:    /opt/local/home/jgerlach/etc/scour.conf
product queue:         /opt/local/home/jgerlach/var/queues/ldm.pq
queue size:            500M bytes
queue slots:           default
reconciliation mode:   do nothing
pqsurf(1) path:        /opt/local/home/jgerlach/var/queues/pqsurf.pq
pqsurf(1) size:        2M
IP address:            0.0.0.0
port:                  388
PID file:              /opt/local/home/jgerlach/ldmd.pid
Lock file:             /opt/local/home/jgerlach/.ldmadmin.lck
maximum clients:       256
maximum latency:       3600
time offset:           3600
log file:              /opt/local/home/jgerlach/var/logs/ldmd.log
numlogs:               7
log_rotate:            1
netstat:               /usr/bin/netstat -A inet -t -n
top:                   /usr/bin/top -b -n 1
metrics file:          /opt/local/home/jgerlach/var/logs/metrics.txt
metrics files:         /opt/local/home/jgerlach/var/logs/metrics.txt*
num_metrics:           4
check time:            1
delete info files:     0
ntpdate(1):            /usr/sbin/chronyd
ntpdate(1) timeout:    5
time servers:          us.pool.ntp.org
time-offset limit:     10


$ pqmon -S
0 1000001536 0 0 7142 0 0 0 -1 -1 -1 0

$ mount | grep /dev/mapper/rhel-root
/dev/mapper/rhel-root on / type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)

$ sestatus
SELinux status:                 disabled

$ head /opt/local/home/jgerlach/src/config.log

---------------------------------------------------------------------------------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by LDM configure 6.15.0, which was
generated by GNU Autoconf 2.71.  Invocation command line was

  $ ./configure --with-noaaport

## --------- ##
## Platform. ##
---------------------------------------------------------------------------------





From: NSF Unidata Local Data Manager (LDM) <address@hidden>
Sent: Tuesday, September 10, 2024 4:30 PM
To: Gerlach, James <address@hidden>
Cc: address@hidden <address@hidden>; address@hidden <address@hidden>
Subject: RE: (#WCA-4105061) LDM 6.15.0 on Red Hat Enterprise Linux release 8.10 on VMware
 
You don't often get email from address@hidden. Learn why this is important
[Please remember, this is an external email]


user.png?v=5.4.0
Stonie Cooper
Staff - Tuesday 10th September 2024 2:29 PM

James - Sorry for the a few questions - but I will need a little background.

 

What tool or log are you using to show that there is incoming data to noaaportIngester?  I just want to confirm that you are actually getting data to that point, as it would be unusually to get that far and not have data going into ldmd.

 

So, here are some questions:

 

  • what does your noaaportIngester entries look like in your ~ldm/etc/ldmd.conf file?
  • most VM instances like to do weird things to the NICs - virtual or not - could you send me a snippet of the output when you run:

tcpdump -i <the interface attached to the Novra, directly or indirectly> -n -n

 

  •  could you send me the output from "ldmadmin showsettings"?

 

Stonie Cooper, PhD

Software Engineer III

NSF Unidata Program Center

University Corporation for Atmospheric Research

I acknowledge that the land I live and work on is the traditional home of The Chahiksichahiks (Pawnee), The Umoⁿhoⁿ (Omaha), and The Jiwere (Otoe).


user.png?v=5.4.0
Gerlach, James
User - Tuesday 10th September 2024 1:43 PM

Good day. We have compiled LDM 6.15.0 on a RHEL 8.10 VM, and we are trying to use noaaportIngester to receive data from Novra S300N. When we start the ingester, packet capture shows multicast stream, but we are not receiving data into queue. Would you have any documentation or suggestions specific to running noaaportIngester on VMware, or is anyone available to help us troubleshoot? Thank you for taking a look at this.

Ticket Details

Ticket #: WCA-4105061
Subject: LDM 6.15.0 on Red Hat Enterprise Linux release 8.10 on VMware
Department: Local Data Manager (LDM)
Status: Open
Priority: Normal

You can review the ticket by going to:
https://support.unidata.ucar.edu/tickets/view/WCA-4105061?token=ebaeb59ab67b85d1d61ab2dd4f4ebf0d754637ec

Kind Regards,
NSF UnidataNOTE: All email exchanges with NSF Unidata User Support are recorded in the NSF Unidata support portal. Inquires to some departments are 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.

Stonie Cooper
Staff - Tuesday 10th September 2024 2:29 PM

James - Sorry for the a few questions - but I will need a little background.

 

What tool or log are you using to show that there is incoming data to noaaportIngester?  I just want to confirm that you are actually getting data to that point, as it would be unusually to get that far and not have data going into ldmd.

 

So, here are some questions:

 

  • what does your noaaportIngester entries look like in your ~ldm/etc/ldmd.conf file?
  • most VM instances like to do weird things to the NICs - virtual or not - could you send me a snippet of the output when you run:

tcpdump -i <the interface attached to the Novra, directly or indirectly> -n -n

 

  •  could you send me the output from "ldmadmin showsettings"?

 

Stonie Cooper, PhD

Software Engineer III

NSF Unidata Program Center

University Corporation for Atmospheric Research

I acknowledge that the land I live and work on is the traditional home of The Chahiksichahiks (Pawnee), The Umoⁿhoⁿ (Omaha), and The Jiwere (Otoe).


Gerlach, James
User - Tuesday 10th September 2024 1:43 PM

Good day. We have compiled LDM 6.15.0 on a RHEL 8.10 VM, and we are trying to use noaaportIngester to receive data from Novra S300N. When we start the ingester, packet capture shows multicast stream, but we are not receiving data into queue. Would you have any documentation or suggestions specific to running noaaportIngester on VMware, or is anyone available to help us troubleshoot? Thank you for taking a look at this.

Ticket Details

Ticket #: WCA-4105061
Subject: LDM 6.15.0 on Red Hat Enterprise Linux release 8.10 on VMware
Department: Local Data Manager (LDM)
Status: Open
Priority: Normal

You can review the ticket by going to:
https://support.unidata.ucar.edu/tickets/view/WCA-4105061?token=ebaeb59ab67b85d1d61ab2dd4f4ebf0d754637ec

Kind Regards,
NSF UnidataNOTE: All email exchanges with NSF Unidata User Support are recorded in the NSF Unidata support portal. Inquires to some departments are 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.