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

[LDM #OQE-357383]: (No Subject)

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: [LDM #OQE-357383]: (No Subject)
  • Date: Tue, 21 Feb 2023 12:04:06 -0700
Kevin,

> Hi Steve,
> 
> We might not have a "resolution of the problem" but we have a work around.
> Gilbert called yesterday and he wanted to try out a couple of things.  So
> after looking at a couple files he asked me to add the ldm commands into
> the rc.local file again, but this time using the su - c and then the path
> name for the ldmadmin stop, clean, delqueue, and mkqueue paths.

Unless the LDM user was specified in the su(1) command, everything will be 
owned and run by root, which is very, very, bad.

> In
> addition, I had been running the KDE Plasma Workspace instead of GNOME
> before all this happened.  Well..something wiped it out and I was in GNOME
> when we were going through everything. So I was finally able to get KDE
> back and when we rebooted, with the commands in the rc.local file, LDM
> started to run and receive data from batman2.  I added Gilbert into this
> email in case I missed anything else that would be pertinent.  But the
> bottom line is LDM is running now and I am receiving data on it.

Who owns the LDM processes, the product-queue, and log file?

> Once again, thanks for your patience and all the help you provided the
> other night. It was very much appreciated.

You're welcome. Without understanding the problem, however, I worry that it 
will re-occur.

Good Luck.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OQE-357383
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.