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

Re: hung downstream LDM

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: Re: hung downstream LDM
  • Date: Fri, 28 Oct 2005 16:58:54 -0600
Justin,

Would you be willing to rebild the LDM with support for debugging and
then obtain a core-file from the hung downstream LDM by sending it a
SIGABRT the next time it happens?  If so, then

    1.  Go to the top-level source-directory of the LDM package as the
        LDM user.

    2.  Execute the command "make distclean".

    3.  Ensure that the environment variable CFLAGS contains the string
        "-g".

    4.  Execute the configure(1) script.  Simultaneously redirect the
        standard output and standard error streams to the file
        "configure.log".

    5.  Execute the command "make".  Simultaneously redirect the
        standard output and standard error streams to the file
        "make.log".

    6.  Ensure that core-files may be created.  This is user-shell
        dependent.  The ulimit(1) utility is the standard way of testing
        and setting this.

    7.  Execute the command "ldmadmin stop".

    8.  Become root, execute the command "make install_setuids", and
        then become the LDM user.

    9.  Execute the command "ldmadmin start".

    10. Keep an eye on the downstream LDM that's receiving NEXRAD2 data.
        When it hangs, send it a SIGABRT via the kill(1) utility.  A
        core-file should be created in the top-level directory of the
        LDM user.  Use the dbx(1) utility to obtain a stack-trace and
        send it to me.

Regards,
Steve Emmerson