ESGF Installer Known Issues

Installer Known Issues

If you have started and have a broken installation try the following:
- cd /usr/local/bin
- ./esg-node stop - stop all services
- yum remove myproxy - ensure it is not installed as this package contributes to the conflict
- source esg-purge.sh & esg-purge all - remove installed components
Once done (or if you are starting from scratch) do the following (note that auto-installation will not work in this case) using the installation instructions ESGF Installation From Scratch:
- download and run esg-bootstrap as indicated
- before running esg-node, edit the file - on line 6823 you will see a "yum" invocation with a long list of packages. Remove "myproxy", which should be the second to last item on the list
- When you run esg-node as instructed, it will warn you that the file cannot be verify and may have been tampered with. In this case you want to continue anyway.
- continue with the installation as instructed

For compute nodes: Issue with LAS in 2.3.8. LAS is broken after installation due to tomcat upgrade. The fix is the following:

rm -Rf /usr/local/tomcat/content/las
ln -s /esg/content/las /usr/local/tomcat/content/las
esg-node restart

On freshly installed datanodes, your esg.ini file may contain globus:#DEFAULTENDPONTNAME#
- #DEFAULTENDPONTNAME# needs to be replaced with the UUID for your endpoint (assigned automatically to the gridftp server instance)
- You can log into globus.org and find the endpoint associated with your node's FQDN. The UUID should be listed in a the endpoints properties page
- or you can remove the entry from esg.ini altogether (not recommended) but globus urls can be added to existing publications later (once an endpoint has been established)