-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
moda_oc_7d_gom failing #35
Comments
Dan has reprocessed the files and flipped the latitude. The dataset is still showing as failed in the status.html, but I don't see any big errors in the DasDds output. Based on this maybe it has something to do with permissions? The files are publicly readable on the hypervisor: [tylar@dune ~]$ ls -lah /mnt/sdb/moda_oc_7d_gom/MODA_2005134_2005140_7D_GOM_OC.nc
-rw-r--r--. 1 dotis imars-common 141M Mar 10 17:17 /mnt/sdb/moda_oc_7d_gom/MODA_2005134_2005140_7D_GOM_OC.nc I just followed these instructions to resolve possible SELINUX issues. The files appear readable in the container:
|
I don't see anything helpful from the erddap logs in docker:
I don't know the importance of |
This issue seems to be similar to this unresolved issue with an older dataset. Note that NFS is no longer a factor here, because these files are on a local drive ( |
found the error in
This could be a larger issue with the setup (or lack of setup) of the |
Yep, that fixed it. http://131.247.136.200:8080/erddap/griddap/moda_oc_7d_gom.graph |
Apparently not. I don't know why we were getting that error. The error did go away after you reoriented, but the way it is now is obviously worse. |
Dataset is failing according to status.html.
DasDds output:
Possible issues from the DasDds output:
java.awt.HeadlessException
This is expected and not related
time variable spacing
DasDds is complaining about the spacing of the time variable being uneven, but this is common and should not be breaking the dataset.
latitude needs to be in ascending order
I think this is the issue. The latitude variable needs to be flipped around.
@dotis: Can we try that and see if the updated files work with ERDDAP?
The text was updated successfully, but these errors were encountered: