ESGF Installer Known Issues

Installer Known Issues

This is a list of know issues that might be encountered after an ESGF 2.X installation or upgrade:

• v2.3.8 - CoG doesn't load (500 error, sanitizer error reported in httpd error_log)

  Solution: manually upgrade CoG
  See instructions here: https://acme-climate.atlassian.net/wiki/display/ESGF/Manual+Installation+of+ESGF+Software+Components

• 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)

• Publishing: upgrading to TLS v1.2. If your site requires TLS v1.2 to be configured in apache, then you also will need to modify the publisher. With sudo privs, edit /usr/local/uvcdat/2.2.0/lib/python2.7/site-packages/esgcet-3.0.1-py2.7.egg/esgcet/publish/thredds.py. Change ssl.PROTOCOL_TLSv1 to ssl.PROTOCOL_TLSv1_2. For older versions of the publisher, find the latest esgcet-2.X.X instead of 3.0.1.

---

Also, check out the FAQ: https://github.com/ESGF/esgf.github.io/wiki/ESGFNode|FAQ