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

20061027; ldmadmin start/stop problems at SSEC



Guys,

Kevin Baggett send this email in yesterday.

Steve:
I thought that this is the situation that you had been working on
at SSEC.  Also, I don't think that having to turn on the portmapper
is needed; true?

Mike,
Kevin sent this to you and CCed support.  Did you respond?

Tom

------- Forwarded Message

>To: address@hidden
>From: Kevin Baggett <address@hidden>
>Subject: [Fwd: Re: Question about computer at UW-SSEC]
>Organization: UW-SSEC
>Keywords: 200610271532.k9RFWnXX028466

This is a multi-part message in MIME format.
--------------080004010500010405020303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,
I just wanted to be sure that you know of this issue as it was a problem 
on a Linux SSEC LDM machine.
With our ldm logs and executing "ldmadmin start" and "ldmadmin stop", we 
were getting messages like
 NOTE: local_portmapper_running(): clnttcp_create() failure: : RPC: 
Remote system error - Connection refused
 ERROR:      NAMED  12.000833    0   localhost    can't contact 
portmapper: RPC: Timed out
So, it was taking quite a bit of time to start and stop.
One of our tech guys here found that the "portmap" program was off. 
Whether this was on purpose or not, we don't know.
Anyway, we turned the "portmap" back on by (logged in as root on our 
machine)
"chkconfig portmap on"
and this solved the problem of slow ldmadmin stop/start.
Kevin Baggett
UW-SSEC


-------- Original Message --------
Subject:        Re: Question about computer at UW-SSEC
Date:   Wed, 25 Oct 2006 16:07:33 -0600
From:   Mike Schmidt <address@hidden>
Organization:   UCAR/Unidata
To:     address@hidden



Kevin,

Steve Emmerson fowarded me your support inquiry below.  Normally,
localhost is defined in /etc/hosts as the following;

% grep localhost /etc/hosts
127.0.0.1       localhost loopback

if that definition is missing, it can cause all sorts of unusual
problems.  If you find it is missing, add the above line back.
If localhost *is* listed in /etc/hosts, make the following check;

% grep hosts /etc/nsswitch.conf
hosts:      files dns

to confirm that name resolution on your system does use /etc/hosts.
Let us know if that resolves the issue.

Going forward, please direct support questions to;

 address@hidden

which will assist us in answering you more quickly in the event
specific support staff are out of the office.

Best,

mike

> From:    Kevin Baggett <address@hidden>
> Subject: Question about computer at UW-SSEC
>
> Steve,
> I think (thanks to logging being turned on) I figured out why my LDM is
> taking so long to go on and off.
> The SELINUX keyword being disabled allows logging to work, but doesn't
> solve the slow startup/stop.
> So, after turning the LDM off, the following message shows in the log:
> Oct 25 21:21:54 stimpy ldmping[13141] ERROR:      NAMED  12.000833
> 0   localhost    can't contact portmapper: RPC: Timed out
> I've done a little poking around in the Log Interpretation page, but
> didn't see anything like this.
> In some of the archives, I see messages where "localhost" is a specific
> computer name. Where is this "localhost" being set - is it a
> configuration file variable?
> Thanks!
> Kevin Baggett
> UW-SSEC


--------------080004010500010405020303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
I just wanted to be sure that you know of this issue as it was a
problem on a Linux SSEC LDM machine.<br>
With our ldm logs and executing "ldmadmin start" and "ldmadmin stop",
we were getting messages like<br>
&nbsp;NOTE: local_portmapper_running(): clnttcp_create() failure: : RPC:
Remote system error - Connection refused<br>
&nbsp;ERROR:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAMED&nbsp; 
12.000833&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp; localhost&nbsp;&nbsp;&nbsp; can't 
contact
portmapper: RPC: Timed out<br>
So, it was taking quite a bit of time to start and stop.<br>
One of our tech guys here found that the "portmap" program was off.
Whether this was on purpose or not, we don't know.<br>
Anyway, we turned the "portmap" back on by (logged in as root on our
machine)<br>
"chkconfig portmap on"<br>
and this solved the problem of slow ldmadmin stop/start.<br>
Kevin Baggett<br>
UW-SSEC<br>
<br>
<br>
-------- Original Message --------
<table border="0" cellpadding="0" cellspacing="0">
  <tbody>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Subject: </th>
      <td>Re: Question about computer at UW-SSEC</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Date: </th>
      <td>Wed, 25 Oct 2006 16:07:33 -0600</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">From: </th>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Organization:
      </th>
      <td>UCAR/Unidata</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">To: </th>
    </tr>
  </tbody>
</table>
<br>
<br>
<pre>Kevin,

Steve Emmerson fowarded me your support inquiry below.  Normally,
localhost is defined in /etc/hosts as the following;

% grep localhost /etc/hosts
127.0.0.1       localhost loopback

if that definition is missing, it can cause all sorts of unusual
problems.  If you find it is missing, add the above line back.
If localhost *is* listed in /etc/hosts, make the following check;

% grep hosts /etc/nsswitch.conf
hosts:      files dns

to confirm that name resolution on your system does use /etc/hosts.
Let us know if that resolves the issue.

Going forward, please direct support questions to;


which will assist us in answering you more quickly in the event
specific support staff are out of the office.

Best,

mike

&gt; From:    Kevin Baggett <a class="moz-txt-link-rfc2396E" 
href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
&gt; Subject: Question about computer at UW-SSEC
&gt;
&gt; Steve,
&gt; I think (thanks to logging being turned on) I figured out why my LDM is
&gt; taking so long to go on and off.
&gt; The SELINUX keyword being disabled allows logging to work, but doesn't
&gt; solve the slow startup/stop.
&gt; So, after turning the LDM off, the following message shows in the log:
&gt; Oct 25 21:21:54 stimpy ldmping[13141] ERROR:      NAMED  12.000833
&gt; 0   localhost    can't contact portmapper: RPC: Timed out
&gt; I've done a little poking around in the Log Interpretation page, but
&gt; didn't see anything like this.
&gt; In some of the archives, I see messages where "localhost" is a specific
&gt; computer name. Where is this "localhost" being set - is it a
&gt; configuration file variable?
&gt; Thanks!
&gt; Kevin Baggett
&gt; UW-SSEC
</pre>
</body>
</html>

--------------080004010500010405020303--

--
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.

------- End of Forwarded Message


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.