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.
Peter, I believe you can safely ignore the following HTTP log message: >> Could not reliably determine the server's fully qualified domain name, using >> 172.32.12.221. >> Set the 'ServerName' directive globally to suppress this message *** re: >> But still get the same messages. We assume because we don’t have an LDM set up yet I am a bit confused as LDM would have been setup up via the install script? To see if your regutil command worked correctly, look at the /awips2/ldm/etc/registry.xml file and the <hostname> entry should have your fully qualified host name. With CAVE not starting correctly it sounds like the OpenGL engine isn't running correctly. Are you using an nvidia graphics card? They are the least problematic. Also, is there any decently human-readable text in the core dump that might explain why it is failing? One more possibility, underneath the /home/<user>/caveData folder there may be a console log file (which might be found under a hidden directory named .logs). There may be some good information in there which explains why CAVE has crashed. Let me know if you can't find the console log file. It may not be there (never created) or it may take some grunt searching to find it. Best regards, Evan Polster Unidata AWIPS User Support Ticket Details =================== Ticket ID: RGA-719047 Department: Support AWIPS Priority: Critical Status: Open =================== 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.