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.
Mike, Deletion of inter-process communication objects on user logout by systemd(8), eh? I knew there was a reason some developers don't like systemd(8). Sorry you were the guinea pig on this one. At least your sacrifice won't be in vain. See <https://github.com/Unidata/LDM/issues/62>. And thanks a bunch for sending this in. > I know it's been a little while but wanted to provide an update. Two > things actually... > > First, we haven't seen any issue with the product queue vanishing > since we added RemoveIPC=no to /etc/systemd/logind.conf, that seems to > have done the trick. > > Second, it appears as though that same edit may be the solution to an > unrelated problem I ran into on another server. On this particular > setup, I came in one day to find we weren't answering any downstream > requests. Errors in the log file brought me to the following support > thread, seemingly identical symptoms: > https://www.unidata.ucar.edu/support/help/MailArchives/ldm/msg08123.html. > I added RemoveIPC=no to /etc/systemd/logind.conf here as well, and we > haven't seen any issues since. FWIW this was a relatively new > installation on Ubuntu 16.04, only online for a short while, and the > product queue which appeared unharmed resides on disk there. A clean > LDM restart would restore operation, but believe "RemoveIPC=no" is a > more permanent solution. Thought you'd like to know. Regards, Steve Emmerson Ticket Details =================== Ticket ID: QZZ-219946 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.