Question: View all histories returns blank page
1
bcuser30 • 10 wrote:
Running Galaxy 17.09, upon recent restart users remarked that 'view all histories' returns a blank page. There are javascript errors when troubleshooting via browser, but I'm unsure how to interpret. Nothing obvious is displayed in galaxy logs. Is it a particular file that's not found or is it the actual history? I can get to individual histories without issue.
view_multiple:62 GET https://galaxy.*host*/static/scripts/bundled/extended.bundled.js?v=1525805271 404 (Not Found) jquery.migrate.js:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.0 view_multiple:62 GET https://galaxy.*host*/static/scripts/bundled/extended.bundled.js?v=1525805271 404 (Not Found) view_multiple:153 Uncaught TypeError: Cannot read property 'GalaxyApp' of undefined
at view_multiple:153 (anonymous) @ view_multiple:153 view_multiple:264 Uncaught TypeError: Cannot read property 'masthead' of undefined
at HTMLDocument.<anonymous> (view_multiple:264)
at l (jquery.js:3232)
at Object.fireWith [as resolveWith] (jquery.js:3362)
at Function.ready (jquery.js:3582)
at HTMLDocument.h (jquery.js:3617)
Do you see any local changes in the source tree? The client can always be rebuilt with 'make client-production' (or the endpoint of your choice) from the root of the Galaxy repository, but I'm interested why this would have happened seemingly randomly on restart. Any recent server changes at all?
I don't see any evidence of local changes in the source tree. Only recent change was creating a copy to test cluster configuration with. Basically a cp galaxy test-galaxy and updated the galaxy.ini accordingly. The copy uses a separate database. Perhaps there are some references with in test-galaxy that still point to the galaxy location?