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

20030613: LDM under hpux

Brian,

>Date: 13 Jun 2003 09:55:48 -0400
>From: "Brian S Maher" <address@hidden>
>Organization: National Hurricane Center
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20030610: LDM under hpux

The above message contained the following:

> I may have an issue:

You had to try it yourself, didn't you.  And all I asked for was a "make
install_setuids" as root.  Some people!  :-)

Let's take a look.

> Jun 13 13:54:40 mutton rpc.ldmd[2679]: Starting Up (version: 6.0.13;
> built: Jun 12 2003 21:59:14)
> Jun 13 13:54:40 mutton hagfish[2684]: Starting Up(6.0.13):
> hagfish.nhc.noaa.gov: TS_ZERO TS_ENDT {{ANY,  ".*"}}
> Jun 13 13:54:40 mutton pqact[2682]: Starting Up
> Jun 13 13:54:40 mutton hagfish[2684]: NOTICE: requester6.c:421; 
> ldm_clnt.c:271: nullproc_6 failure to hagfish.nhc.noaa.gov; ldm_clnt.c:142: 
> RPC: Program/version mismatch; low version = 4, high version = 5

The last message above means that the LDM on mutton wasn't able to
connect to the LDM on hagfish using version 6 of the LDM protocol
because hagfish was running an LDM 5.

> Jun 13 13:54:40 mutton pqexpire[2681]: Starting Up
> Jun 13 13:54:40 mutton pqbinstats[2683]: Starting Up (2679)
> Jun 13 13:54:40 mutton hagfish[2684]: FEEDME(hagfish.nhc.noaa.gov): OK

The last line above means that the LDM on mutton was able to connect to
the LDM on hagfish using version 5 of the LDM protocol.

> Jun 13 13:54:40 mutton hagfish[2684]: svc_fd_create: No memory!
> Jun 13 13:54:40 mutton hagfish[2684]: cannot create fd service.
> Jun 13 13:54:40 mutton hagfish[2684]: Done

The above lines indicate a severe problem with the execution environment
because a malloc() of an RPC CLIENT structure was unsuccessful.  This
error -- which shouldn't occur and doesn't on any other system -- is the
reason the LDM won't run under HP-UX 11.

You discovered the same problem we've been having here.  We believe that
we need to rebuilt the kernel in order to make the "data segment size"
limit "unlimited" in order to fix this problem.  We've been
unsuccessful in two rebuilt attempts, so far.

Regards,
Steve Emmerson