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

[LDM #APJ-776066]: new noaaport install

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 #APJ-776066]: new noaaport install
  • Date: Fri, 07 Jul 2017 12:48:51 -0600
Hi Brendon,

re:
> The setuids are all set properly:
> 
> [ldm@noaaport5 bin]$ pwd
> /usr/local/ldm/bin
> [ldm@noaaport5 bin]$ ls -l ldmd hupsyslog noaaportIngester dvbs_multicast
> -rwsr-xr-x. 1 root ldm 368880 Jul  6 18:41 dvbs_multicast
> -rwsr-xr-x. 1 root ldm  12648 Jul  6 18:41 hupsyslog
> -rwsr-xr-x. 1 root ldm 148840 Jul  6 18:41 ldmd
> -rwsr-xr-x. 1 root ldm 474752 Jul  6 18:41 noaaportIngester

These do indeed look correct.

re:
> The firewall is turned off:
> [root@noaaport5 ~]# systemctl status firewalld
> ? firewalld.service - firewalld - dynamic firewall daemon
> Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
> vendor preset: enabled)
> Active: inactive (dead) since Fri 2017-07-07 18:33:21 GMT; 2min 15s ago
> Docs: man:firewalld(1)
> Process: 850 ExecStart=/usr/sbin/firewalld --nofork --nopid
> $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
> Main PID: 850 (code=exited, status=0/SUCCESS)
> 
> Jul 07 13:45:43 noaaport5.plymouth.edu systemd[1]: Starting firewalld -
> dynamic firewall daemon...
> Jul 07 13:45:43 noaaport5.plymouth.edu systemd[1]: Started firewalld -
> dynamic firewall daemon.
> Jul 07 18:33:20 noaaport5.plymouth.edu systemd[1]: Stopping firewalld -
> dynamic firewall daemon...
> Jul 07 18:33:21 noaaport5.plymouth.edu systemd[1]: Stopped firewalld -
> dynamic firewall daemon.

We've been through this will other CentOS 7.x users, and invariably the firewall
was the cause.  I'm looking through past email exchanges to see what might
be happening.

re:
> Anything else to look at?

You said you can ping the S300N.  Can you connect to it using 'cmcs'?

Also (so we have a better idea of your setup):

- what version of 'cmcs' are you running?

- what is the firmware version that the S300N is running?

- now the big one, can we get a login to your machine AND get 'root' privilege
  so we can take a close-up look?

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: APJ-776066
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.