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

19991111: Broken pipes...and it isn't my plumbing (fwd)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19991111: Broken pipes...and it isn't my plumbing (fwd)
  • Date: Fri, 12 Nov 1999 08:24:47 -0700 (MST)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Thu, 11 Nov 1999 15:04:18 -0700
From: Unidata Support <address@hidden>
To: Gilbert Sebenste <address@hidden>
Subject: 19991111: Broken pipes...and it isn't my plumbing 

>From: Gilbert Sebenste <address@hidden>
>Organization: Northern Illinois University
>Keywords: 199911111745.KAA14977 LDM broken pipes

Gilbert-

>To Tom Yoksas,

Tom is out of town until late next week.

>Tom, I am having broken pipes all over the place. No, it isn't my
>plumbing! McIDAS-XCD is giving me tons of errors...mostly
>xcd_run DDS errors, causing broken pipe errors in my ldmd.conf
>file. Any idea what they are being caused by? I deleted the ldm queue
>a few days ago, then re-started the LDM, and that's when the trouble
>started.

Assuming you haven't deleted any programs or links that xcd_run
uses, I've seen this problem when ldmfail runs and there are poor
network connections to both feed sites.  Somehow this affects
the way xcd_run works.  The solution is to shut down and
restart your LDM (after making sure all LDM processes have died).
Another option is to comment out ldmfail from your crontab and
see if the problem goes away (but then you won't have automatic
failover).

>Any clues?

Tom will have to look at this when he gets back because another site
reported a similar problem.  I'll talk to Robb about this also.  If you
are not running ldmfail, let me know as this would indicate that there
is a different problem.  Also, check to see if the broken pipes happen
right after ldmfail is run (usually 0, 20, and 40 mins past the hour).

Don Murray