[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20040804: problem with ldm installation on Linux (cont.)
- Subject: 20040804: problem with ldm installation on Linux (cont.)
- Date: Wed, 04 Aug 2004 13:27:19 -0600
>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200408041851.i74IpUaW005990
Ying,
re: what is your request line
request ANY ".*" atm.geo.nsf.gov
OK. Can you ping atm.geo.nsf.gov? The ldmping failure you sent
previously would work even if atm does not have an allow for your
machine. Since the LDM on atm _is_ running (it is feeding a LOT
of downstream sties), and since an ldmping from your machine failed,
I am beginning to suspect a firewall issue on your side.
re: fully qualified hostname of your LDM machine
unidata.scs.gmu.edu
Thanks.
re: forward and reverse name lookup for your LDM machine
>Hmm, I don't think so.
This _will_ be a problem. One of the requirements is that a
downstream machine have forward and reverse name lookup. This
relates to security on the server side.
I just checked, and your machine does not have both forward and reverse
name lookup:
% nslookup unidata.scs.gmu.edu
Server: 128.117.140.62
Address: 128.117.140.62#53
Non-authoritative answer:
Name: unidata.scs.gmu.edu
Address: 129.174.124.79
% nslookup 129.174.124.79
Server: 128.117.140.62
Address: 128.117.140.62#53
** server can't find 79.124.174.129.in-addr.arpa: SERVFAIL
You need to contact your network folks and work with them to get
forward and reverrse name lookup for your box.
re: what does your ~ldm/logs/ldmd.log file have to say
>I have ~ldm/logs/ldmd.log, but it is always 0 byte -- it's empty. the file
>owner is ldm, and group is unidata (which include gempak, mcidas, and ldm)
This tells me that it is very likely that your /etc/syslog.conf file
has not been setup/setup correctly for the entries needed for logging.
Please check this file for the following:
1) entry for local0.none. It should look like:
*.info;mail.none;news.none;authpriv.none;cron.none;local0.none
/var/log/messages
...
# Unidata LDM
local0.debug /usr/local/ldm/logs/ldmd.log
NOTE: white space between the service and the log file pathname are tabs,
not spaces! This is important!!
>Yeah, when we first contacted with unidata support, we were told our
>"unidata.scs.gmu.edu" should point its request to "atm.geo.nsf.gov".
This is correct. I meant to say that I am seeing NO denial messages
in the ~ldm/logs/ldmd.log files on atm. This means that your
feed reqest is not making it to atm. This, in turn, tells me that
there may be a firewall issue on your end.
The things to look for now are:
1) firewall rules on your machine or in your department/domain that would
keep unidata.scs.gmu.edu from making requests to atm.geo.nsf.gov on
port 388
2) work with your network folks on getting forward and reverse name lookup
setup for unidata.scs.gmu.edu
3) one last thing I forgot to ask: did you make sure to run the
final installation step as 'root':
cd ~ldm/ldm-6.0.14/src
./configure
make
make install
sudo make install_setuids <- this is the step I am talking about
-- or --
<as root>
cd ~ldm/ldm-6.0.14/src
make install_setuids <- this is the step I am talking about
>Thank you!
No worries.
Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.