Open alaniwi opened 6 years ago
This is on a recently installed v2.5.12-devel-release
If I install netcdf from an RPM, which provides /usr/lib64/libnetcdf.so
, this error goes away. (Due to the yum setup on our machines, this finds an RPM that I built for netcdf 4.4.0, but presumably it would be the same if the RPM for 4.1.1 from EPEL was used.)
So it seems that netcdf needs to be included in the RPM dependencies.
@alaniwi, What install type did you use? Going to try to reproduce the problem.
cc @alaniwi Update on issue from Sean Arms:
"That is just a warning that the TDS could not find the netCDF-C library and should not prevent the TDS from starting up or running properly. If one wishes to have the netCDFSubsetService return netCDF-4 files, you need to link against the netCDF-C library (currently the only way to write netCDF-4 files). If you would like to specify where the C library lives, you can do so in threddsConfig.xml:
If you do not want netCDF-4 files returned from the NetcdfSubsetService, then it is safe to ignore the message.
That said, I'm not sure why the stack trace is dumping to the log file. Is the TDS failing to start all together?
Cheers,
Sean"
@William-Hill , how was this resolved? Was something changed in the xml config file?
@pchengi I didn't make any changes. The issue is still marked as open. Has the problem been reproduced in test installs?
@alaniwi , can you please let me know what I need to do to reproduce this issue? If this is not an issue now, I'd like to close this issue.
I am getting the following error in
/esg/content/thredds/logs/serverStartup.log
followed by a long list of jar files (snipped).
and the traceback