[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #CFG-797475]: NOAA - LDM Issue
This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
- Subject: [LDM #CFG-797475]: NOAA - LDM Issue
- Date: Tue, 28 Feb 2017 16:09:31 -0700
Hi Russ,
Thanks for sending us the output of the various commands we asked for
yesterday. For the most part, I didn't see anything that looked out
of place EXCEPT the following:
> [rlancast@fos2-cip ~]$ netstat -gn
> IPv6/IPv4 Group Memberships
> Interface RefCnt Group
> --------------- ------ ---------------------
> lo 1 224.0.0.1
> ens32 1 224.0.1.8
> ens32 1 224.0.1.7
> ens32 1 224.0.1.5
> ens32 1 224.0.1.6
> ens32 1 224.0.1.10
> ens32 1 224.0.1.9
> ens32 1 224.0.0.251
> ens32 1 224.0.0.1
> ens34 1 224.0.1.3
> ens34 1 224.0.1.2
> ens34 1 224.0.1.4
> ens34 1 224.0.1.1
> ens34 1 224.0.0.251
> ens34 1 224.0.0.1
> lo 1 ff02::1
> lo 1 ff01::1
> ens32 1 ff02::202
> ens32 1 ff08::2
> ens32 1 ff02::1:ff98:20b0
> ens32 1 ff02::1
> ens32 1 ff01::1
> ens34 1 ff02::202
> ens34 1 ff08::2
> ens34 1 ff02::1:ff98:2cae
> ens34 1 ff02::1
> ens34 1 ff01::1
Notice that the multicast addresses 224.0.1.1 - 224.0.1.10 are not all
associated with the same interface:
> ens32 1 224.0.1.5
> ens32 1 224.0.1.6
> ens32 1 224.0.1.7
> ens32 1 224.0.1.8
> ens32 1 224.0.1.9
> ens32 1 224.0.1.10
> ens34 1 224.0.1.1
> ens34 1 224.0.1.2
> ens34 1 224.0.1.3
> ens34 1 224.0.1.4
All ten of the multicast addresses should be associated with the
Ethernet interface to which your Novra S300N is connected, ens34.
As an example of this, here is the 'netstat -gn' output from one
of our CentOS 6 NOAAPort ingest machines:
~: netstat -gn
IPv6/IPv4 Group Memberships
Interface RefCnt Group
--------------- ------ ---------------------
lo 1 224.0.0.1
eth1 1 224.0.1.8
eth1 1 224.0.1.5
eth1 1 224.0.1.9
eth1 1 224.0.1.7
eth1 1 224.0.1.1
eth1 1 224.0.1.4
eth1 1 224.0.1.10
eth1 1 224.0.1.6
eth1 1 224.0.1.3
eth1 1 224.0.1.2
eth1 1 224.0.0.1
eth0 1 224.0.0.1
lo 1 ff02::1
eth1 1 ff02::1
eth0 1 ff02::1
It is very interesting (to me, at least) that the IP addresses that
we _added_ to your LDM configuration file are all associated with
ens32, not ens34. Because of this anomaly, I need to see your
the contents of your ~ldm/etc/ldmd.conf file. If possible, please
send the file as an attachment, not as a cut and paste from a
listing.
The other things that I would like to see are your:
/etc/hosts
/etc/sysconfig/network-scripts/ifcfg-ens32
/etc/sysconfig/network-scripts/ifcfg-ens34
On a new note, please send us the output of:
netstat -nl
The output of 'netstat -nl' run on our same CentOS 6.8 NOAAPort ingest
machine looks like:
~: netstat -nl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 0.0.0.0:388 0.0.0.0:*
LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:*
LISTEN
tcp 0 0 0.0.0.0:6010 0.0.0.0:*
LISTEN
tcp 0 0 0.0.0.0:6011 0.0.0.0:*
LISTEN
tcp 0 0 :::22 :::*
LISTEN
tcp 0 0 :::6010 :::*
LISTEN
tcp 0 0 :::6011 :::*
LISTEN
udp 0 0 128.117.156.25:123 0.0.0.0:*
udp 0 0 192.168.1.7:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp 0 0 224.0.1.1:1201 0.0.0.0:*
udp 0 0 224.0.1.2:1202 0.0.0.0:*
udp 0 0 224.0.1.3:1203 0.0.0.0:*
udp 0 0 224.0.1.4:1204 0.0.0.0:*
udp 0 0 224.0.1.5:1205 0.0.0.0:*
udp 0 0 224.0.1.6:1206 0.0.0.0:*
udp 0 0 224.0.1.7:1207 0.0.0.0:*
udp 0 0 224.0.1.8:1208 0.0.0.0:*
udp 0 0 224.0.1.9:1209 0.0.0.0:*
udp 0 0 224.0.1.10:1210 0.0.0.0:*
udp 0 0 :::123 :::*
...
Notice how all multicast IP addresses 224.0.1.1 - 224.0.1.10, inclusive, all
have the Foreign Address 0.0.0.0:*. I am guessing that your listing may look
different.
re:
> [rlancast@fos2-cip ~]$ grep ldm /etc/passwd
> ldm:x:345:201::/home/ldm:/bin/bash
OK. I asked for this to verify where the HOME directory of 'ldm' is.
re:
> [rlancast@fos2-cip ~]$ cat /etc/fstab
>
> #
> # /etc/fstab
> # Created by anaconda on Tue Feb 14 12:35:12 2017
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk'
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
> #
> /dev/mapper/rhel-root / xfs defaults 0 0
> UUID=d22893cc-5037-4a74-83dd-7c0ccd04b07e /boot xfs defaults 0 0
> /dev/mapper/rhel-data /data xfs defaults 0 0
> /dev/mapper/rhel-home /home xfs defaults 0 0
> /dev/mapper/rhel-opt /opt xfs defaults 0 0
> /dev/mapper/rhel-tmp /tmp xfs defaults 0 0
> /dev/mapper/rhel-usr /usr xfs defaults 0 0
> /dev/mapper/rhel-var /var xfs defaults 0 0
> /dev/mapper/rhel-swap swap swap defaults 0 0
> [rlancast@fos2-cip ~]$
> [rlancast@fos2-cip ~]$ mount
> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
> devtmpfs on /dev type devtmpfs
> (rw,nosuid,size=3989676k,nr_inodes=997419,mode=755)
> securityfs on /sys/kernel/security type securityfs
> (rw,nosuid,nodev,noexec,relatime)
> tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> devpts on /dev/pts type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
> tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
> cgroup on /sys/fs/cgroup/systemd type cgroup
> (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
> pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
> cgroup on /sys/fs/cgroup/devices type cgroup
> (rw,nosuid,nodev,noexec,relatime,devices)
> cgroup on /sys/fs/cgroup/memory type cgroup
> (rw,nosuid,nodev,noexec,relatime,memory)
> cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup
> (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
> cgroup on /sys/fs/cgroup/hugetlb type cgroup
> (rw,nosuid,nodev,noexec,relatime,hugetlb)
> cgroup on /sys/fs/cgroup/blkio type cgroup
> (rw,nosuid,nodev,noexec,relatime,blkio)
> cgroup on /sys/fs/cgroup/freezer type cgroup
> (rw,nosuid,nodev,noexec,relatime,freezer)
> cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup
> (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
> cgroup on /sys/fs/cgroup/pids type cgroup
> (rw,nosuid,nodev,noexec,relatime,pids)
> cgroup on /sys/fs/cgroup/perf_event type cgroup
> (rw,nosuid,nodev,noexec,relatime,perf_event)
> cgroup on /sys/fs/cgroup/cpuset type cgroup
> (rw,nosuid,nodev,noexec,relatime,cpuset)
> configfs on /sys/kernel/config type configfs (rw,relatime)
> /dev/mapper/rhel-root on / type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-usr on /usr type xfs (rw,relatime,attr2,inode64,noquota)
> systemd-1 on /proc/sys/fs/binfmt_misc type autofs
> (rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
> mqueue on /dev/mqueue type mqueue (rw,relatime)
> debugfs on /sys/kernel/debug type debugfs (rw,relatime)
> hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
> nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
> /dev/sda1 on /boot type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-data on /data type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-tmp on /tmp type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-opt on /opt type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-home on /home type xfs (rw,relatime,attr2,inode64,noquota)
> /dev/mapper/rhel-var on /var type xfs (rw,relatime,attr2,inode64,noquota)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
> tmpfs on /run/user/987 type tmpfs
> (rw,nosuid,nodev,relatime,size=801108k,mode=700,uid=987,gid=20001)
> tmpfs on /run/user/6042 type tmpfs
> (rw,nosuid,nodev,relatime,size=801108k,mode=700,uid=6042,gid=6042)
I asked for the output of 'cat /etc/fstab' and 'mount' so that we could see if
the 'nosuid' flag was set for the directory (/home/ldm) where your LDM is
installed. As you can see, it is not.
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: CFG-797475
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.
- Prev by Date: [LDM #CFG-797475]: NOAA - LDM Issue
- Next by Date: [LDM #JPD-183890]: LDM and security question
- Previous by thread: [LDM #CFG-797475]: NOAA - LDM Issue
- Next by thread: [LDM #CMI-630638]: LDM
- Index(es):