Question: 404 error when trying to view history
0
matthias.desmet • 150 wrote:
Hi there,
Lately I have been experiencing some issues with the viewing of histories on our local Galaxy instance.
Let me sketch the situation:
- I have several histories with running jobs, one job generated too much data and I went over my data limit.
- I deleted and purged some older histories to free up disk space
- I deleted and purged the offending dataset from my current history
Since the deletion of said dataset, the history it was in is no longer readable. The interface reports the following:
{
"agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4",
"url": "https://galaxy/history/view_multipl/api/histories/964b37715ec9bd22/contents?dataset_details=0aab0e4c25198ad8%2C4a56addbcc836c23%2C92b83968e0b52980",
"options": {
"data": {
"dataset_details": "0aab0e4c25198ad8,4a56addbcc836c23,92b83968e0b52980"
},
"silent": true,
"parse": true,
"emulateHTTP": false,
"emulateJSON": false
},
"xhr": {
"readyState": 4,
"responseText": "{\"err_msg\": \"objectstore, _call_method failed: get_filename on , kwargs: {}\", \"err_code\": 404001}",
"responseJSON": {
"err_msg": "objectstore, _call_method failed: get_filename on , kwargs: {}",
"err_code": 404001
},
"status": 404,
"statusText": "Not Found",
"responseHeaders": {
"Connection": "keep-alive\r",
"Transfer-Encoding": "Identity\r",
"Date": "Mon, 25 Jan 2016 08:21:16 GMT\r",
"Server": "nginx/1.8.0\r",
"Content-Type": "application/json\r",
"Vary": "Accept-Encoding\r",
"X-Frame-Options": "SAMEORIGIN\r",
"Cache-Control": "max-age=0,no-cache,no-store\r"
}
},
"source": [],
"user": {
"username": "redacted",
"quota_percent": 1,
"total_disk_usage": 909093453,
"nice_total_disk_usage": "867.0 MB",
"email": "redacted",
"is_admin": true,
"tags_used": [
"exome",
"hg19"
],
"model_class": "User",
"id": "f2db41e1fa331b3e"
}
}
Could this be some kind of bug in the API? I noticed several posts here with similar issues, and I think the cause could be the same.
System info:
- Galaxy release 15.10, run from .venv with 2 uwsgi workers
- Ubuntu 14.04.3
Thanks!
Matthias
Hi, Matthias
Can you log out, close your browser, and log back in please: it may be the history is trying to get 'dataset_details' for the purged dataset because the browser's sessionStorage has saved it as expanded (shown with details) in the history panel.