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.
Frank, The information you sent is difficult to understand because you appear to have more than one system named "drizzl". What is the fully-qualified hostname of the system associated with the file "ldmd-drizzl.log"? The file "ldmd-drizzl.conf" doesn't appear to have an ALLOW entry for connections from *any* system in the "uml.edu" domain. This is likely the source of your problem. The file "ldmd-stratus.conf" does have this entry: ALLOW ANY ^drizzl.uml.edu (which, BTW, would be better written as "ALLOW ANY ^drizzl\.uml\.edu$"). The file "ldmd-drizzl.conf" should likely have something similar. > I am trying to upgrade an old ldm server (stratus.uml.edu), and am > trying to test the replacement (drizzl.uml.edu) > > I keep getting the "connection not allowed" in the new ldmd.log. > > The log on the old machine never shows the connection request. > > I have attached the log files and ldmd.conf files from both machines. Regards, Steve Emmerson Ticket Details =================== Ticket ID: LIT-351851 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.