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

Re: Portmapper Problems

Hi, Robb!

Someone here at the office figured out the problem.  The person who set 
up the machine for higher security moved the portmapper to run at run-
time level 4.  Apparently, LDM needs to have it at level 3.  That was a 
tough one to catch!  We're looking somebody figured that out.  The box 
is now back to doing a great job running LDM and sending files to our 
webserver.

BTW...you'll recall my message traffic of a couple of months ago where 
the Perl script was kicking off lots of child processes from system 
calls...I fixed it by having just the one script run all the time in 
the background.  Now it just sleeps for 5 seconds, then gets the list 
of files in the directory and increments through them.  I'm not even 
kicking off the script any more in pqact.conf.  Rather, I found it much 
more efficient to just do a FILE on the incoming products.  I got a lot 
of the ideas of how to get that to work from you, so THANKS!

Ken


----- Original Message -----
From: Robb Kambic <address@hidden>
Date: Friday, May 19, 2000 5:23 pm
Subject: Re: Portmapper Problems

> On Fri, 19 May 2000, Ken Waters wrote:
> 
> > We are trying to set up a new primary LDM machine, running on Redhat
> > Linux 6.0.  This machine was successfully running LDM just fine 
> a few
> > weeks ago.  Since then, several changes were made to it relating to
> > firewall installation.
> > 
> > Now, the LDM does not seem to start correctly.  It "hangs" on the
> > 'ldmadmin start' command.  I double-checked all the root-level
> > pre-installation steps (/etc/services, /etc/rpc, 
> /etc/syslog.conf, etc.)
> > and they are all okay.  Now, going on to your troubleshooting 
> section,> when I issue the "rpcinfo -p <hostname>" command, I get 
> an error that
> > rpc is unable to access the portmapper.  I issue the "rpcinfo -d 
> 300029> 4" command but that does not seem to fix the problem.
> 
> Ken,
> 
> I believe your problem stems from your Firewall configurations. First,
> port 388 needs to be open for TCP/UDP packets for sites trying to 
> accessthe LDM server machine. That's the basic communication needs 
> for the LDM,
> plus the LDM needs to access the portmapper so it can determine 
> which port
> it's using.  Your invocation "rpcinfo -p" failure indicates that 
> at one
> Firewall configuration is not correct. 
> 
> I would review the Firewall documentation to see if there are
> other configuration/flags the need to be set to permit proper
> communication between the LDM processes and the outside world.  
> Since, I
> have never installed a Firewall I don't know the details and each 
> Firewallpackage is different.
> 
> Robb...
> 
> > 
> > I'm sorry I can't include snippets of the log files right now 
> because we
> > did an emergency switch of the machines back so that we can continue
> > serving data.  I hope to be able to provide more information a 
> little> bit later once I regain access to the box.
> > 
> > Thanks!!
> > 
> > Ken Waters
> > Southern Region HQ, NWS
> > 
> > 
> > 
> > 
> 
> 
========================================================================
=======
> Robb Kambic                              Unidata Program Center
> Software Engineer III                    Univ. Corp for Atmospheric 
Research
> address@hidden                   WWW: 
http://www.unidata.ucar.edu/
> 
========================================================================
=======
> 
>