Hi:
Yes we have seen this problem. (Assuming this is not an issue with first loading the dataset). The likely chain of events is that ERDDAP is doing a dataset update and for a variety of reasons now can not access the dataset (this is presuming it worked for a while), so throws that message. We have found two things cause this:
1. The volume disappears on the Linux system.
2. Access to the volume is temporarily very busy, so access for the dataset fails.
Next time it happens, can you check that you can actually access the dataset, check the settings ,setup.xml to see the times that have been set for when to stop a reload. ( search for the part that has like "<loadDatasetsMinMinutes>15</loadDatasetsMinMinutes> “ and read through e settings there). Then look at log.txt for when ERDDAP first started the update and follow through on other references to try and get some idea of how long it is taking. For example, if a user happens to be making heavy use of the dataset as the update starts, it may fail. One thing you can also do is adjust how often that datasets needs to be updated. Depending on how you add data to the dataset, you might increase the time, and set a flag when an actual datastet update occurs.
Just the kind of thing that needs tracking through a lot of logs, which is painful but other than the two reasons above we have not seen this.
HTH,
-Roy