-
Notifications
You must be signed in to change notification settings - Fork 494
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
rData download 503 error #4729
Comments
@FASposito thanks for opening this issue. https://data.aussda.at/api/info/version indicates that you're running Dataverse 4.6.2 right now. You might want to try upgrading to see if it helps or not. If there's anything interesting in server.log, please email it to [email protected]. You could attach it here but I'm concerned there might be some details about your installation that we wouldn't want to expose publicly. For others, I asked Frank to create this issue after reading his post at https://groups.google.com/d/msg/dataverse-community/QAX3LaMsbjI/jHrf089QAgAJ I can easily replicate the "HTTP Status 503 - Service Unavailable" error by following the instructions above, which put me on this URL: https://data.aussda.at/api/access/datafile/189?format=RData&gbrecs=true |
Thanks. Unfortunately our systems administrator is out of the office for an extended period so we don't have access to any server logs at the moment. I'll see if I can find a workaround to access the logs in the meantime. |
@FASposito is your sysadmin back? Any news? 😄 |
Hi Phil, Unfortunately he's still away. We're developing a new workflow in the meantime and will post the logs once we have them. |
@FASposito no rush! Thanks! Have a good weekend! |
just a bump that we get this on our test dataverse (4.9.4) as well. turns out our test server was pointing at a test rserver which was missing the haven package. all is well. |
Some data files cause an HTTP 503 error when attempting download in rData format. For example: https://data.aussda.at/file.xhtml?fileId=189&version=3.0
The text was updated successfully, but these errors were encountered: