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.
Gilbert, That's great news! I was concerned about my SWAG diagnosis. This version will be officially released soon. > We just did the test on NFS01, using LDM01 to try to crash the beta on > NFS01. Here is what happened: > > NFS01 logged the outage of LDM01. This does NOT happen on 6.13.10; > NFS01 switched to other backups instantly; > When LDM01's LDM was "turned back on", after like 30 seconds or so, NFS01 > noted that it was able to connect, and decided to use it as a primary.. > That did NOT happen before. > NFS01's pqacts are still writing to disk. This did NOT happen before. > The LDM stops even faster than before on NFS01 when I request a shutdown. > > I am also not getting any messages about "X feed has not received data in > the last Y minutes" after I stop the LDM on NFS01, delete the queue, > ldmadmin clean it, and restart it. > It never sent those messages before for very brief outages before, and with > this beta, it is not doing it now. > > I'm going to run this for another hour to make sure everything is good. It > is working fine on all the other machines I updated last night. At noon CT, > I'll email you back and call this good > if I see no errors or issues, and request that this be made operational. > > No other issues are noted. The beta LDM is working as intended on all > servers. > > Thank you, Ryan, for letting me do extensive testing today. Thanks, Mike, > for letting me test at COD. Regards, Steve Emmerson Ticket Details =================== Ticket ID: WOM-274153 Department: Support LDM Priority: High 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.