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.
Hi Carol, re: > I do have 'sudo' privileges, but I trust TC more than myself when it > comes to installing packages. I don't believe there is a restriction by > TC to install packages. I haven't heard back from them yet about the > installation, but it will probably get done at some point today. OK. Like I said, I was just curious. re: > I've attached the make and configure log files for the installation I > tried to do on Friday on aws.ssec.wisc.edu. OK. The make_aws.log file indicates that the build went to completion with no errors. It also pointed out that 'root' needs to execute the 'make root-actions' step to finish the build: NOTE: The command "make root-actions" will have to be executed by the superuser in order to complete the installation process. make[3]: Leaving directory `/home/ldm/ldm-6.13.2/src' make[2]: Leaving directory `/home/ldm/ldm-6.13.2/src' make[1]: Leaving directory `/home/ldm/ldm-6.13.2/src' So, it looks like you need to: sudo su - cd ~ldm/ldm-6.13.2/src make root-actions exit <as 'ldm'> cd ~ldm ldmadmin stop && rm runtime && ln -s ldm-6.13.2 runtime && ldmadmin start re: > When I ran the ldmadmin config it showed that I was still running the > old version. This is probably saying that you did not do the last steps that I indicated above. re: > It also showed that the name of the machine was > minke.ssec.wisc.edu (the old name of the machine) instead of > aws.ssec.wisc.edu. I'm not sure if that matters but I thought it was > worth noting. The name that the machine will report in 'ldmadmin config' is the name that is specified in the <hostname></hostname> setting in the LDM registry file, ~ldm/etc/registry.xml. This setting does _not_ get changed when the machine gets renamed since the registry file is only updated (after initial creation) by the 'ldm' user either by editing the file directly or by changing individual values by running the LDM utility 'regutil'. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: EIW-321327 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.