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

[LDM #UHO-873587]: Possible bug with 6.13.7 (and previous)

Regards,
Steve Emmerson


---------- Forwarded message ---------
From: Mike Zuranski <address@hidden>
Date: Wed, Mar 6, 2019 at 8:38 AM
Subject: New Client Reply - [LDM !UHO-873587]: Possible bug with 6.13.7
(and previous)
To: <address@hidden>


New Client Reply: Possible bug with 6.13.7 (and previous)

On Tue, Mar 5, 2019 at 11:19 PM Gilbert Sebenste <address@hidden>
wrote:

>
> Let me say something else, too: thanks for the heads up on how to most
> effectively use primary and backup feeds, and how they are used and done
in
> the LDM. We don’t care about incoming bandwidth, but in the not too
distant
> future, Mike Zuranski at COD may go the route of how we are doing it now.
> It will be interesting to see bandwidth usage/performance on their end if
> they implement it.
>

I'm working on this now.  FWIW I am concerned about incoming bandwidth,
both myself and the rest of COD's IT watch that pretty closely.  I started
tinkering with my request lines yesterday, still working out how I want to
set up the final topology but I'm starting my testing.  Especially now that
I am aware of the two-feed limitation I want to get cranking on this, and
make things here both as reliable & efficient as possible.

I already have a couple of questions.  First, what does this error mean?
I'm seeing these on my downstream sever (v6.13.6), and they seem fairly
common:

pqact[66069] ERROR filel.c:3032:reap() Child 39808 exited with status 255
The Child number will vary, but the rest is always the same.

Similarly, what does "ldmd.c:cleanup() NOTE  Exiting" mean?  I'm seeing
this on my upstream server (v6.13.7) associated with a few different
IPs/hostnames, also pretty common.  A couple of those IPs are also mine,
and I've already made sure to limit redundant requests to no more than two
on both of those.

And yes, I do plan on updating everything to v6.13.8 soon, just figured I'd
start with some initial adjustments to my requests lines first.

Thanks,

-Mike

======================
Mike Zuranski
Meteorology Support Analyst
College of DuPage - Nexlab
Weather.cod.edu <http://weather.cod.edu/>
======================



Ticket Details
===================
Ticket ID: UHO-873587
Department: Support LDM
Priority: High
Status: Open
Link:
https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=30084



Ticket Details
===================
Ticket ID: UHO-873587
Department: Support LDM
Priority: High
Status: Open
===================
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.