i assume you have your tds cache pointing to /usr/local/threddsCache?
make sure that its writeable by the user running tomcat.
stop tomcat, delete /usr/local/threddsCache and restart tomcat.
also send threddsConfig.xml next time.
Mohamed, In the featureCollectionScan.log, there are multiple occurences of this error, so it seems as if perhaps the makeFmrcInv function failed. I have no idea what this means or how to fix it.
[2014-01-14T14:53:54.264+0000] ERROR ucar.nc2.ft.fmrc.Fmrc: /var/www/vhosts/opendap.co-ops.nos.noaa.gov/htdocs/netcdf/last7days/lsofs/.*fields.forecast.*\.nc: makeFmrcInv failed java.lang.RuntimeException: com.sleepycat.je.EnvironmentFailureException: (JE 4.0.92) /usr/local/threddsCache/collection This environment's log file has no root. Since the root is the first entry written into a log at environment creation, this should only happen if the initial creation of the environment was never checkpointed or synced. Please move aside the existing log files to allow the creation of a new environment LOG_INTEGRITY: Log information is incorrect, problem is likely persistent. Environment is invalid and must be closed. at ucar.nc2.ft.fmrc.Fmrc.makeFmrcInv(Fmrc.java:332) at ucar.nc2.ft.fmrc.Fmrc.update(Fmrc.java:239)
On Tue, Jan 14, 2014 at 10:51 AM, Unidata THREDDS Support <address@hidden> wrote:
Your Ticket has been received, and a Unidata staff member will review it and reply accordingly. Listed below are details of this new Ticket. Please make sure the Ticket ID remains in the Subject: line on all correspondence related to this Ticket.
Ticket ID: NPU-258487 Subject: 9 of 12 featureCollections failing after upgrade from 4.2 to 4.3 Department: Support THREDDS Priority: Normal Status: Open
Please let us know how we can assist you further.
Unidata User Support
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.