OnDemand dashboard formatting

See above screenshot. This is what I get immediately after logging in to OnDemand. I’ve cleared cookies/cache and this doesn’t fix the issue. Happens on both Firefox and Chrome (latest versions).

Can you show us what the output of your web browsers console (in dev tools)? There’s likely some error there where it can’t get the right css or something.

looks like it can’t find
https://ondemand.jhuapl.edu/pun/sys/dashboard/assets/application-05ef8da03b5b8811283da1170e2a07bc5865b21764af5054129db60afff5f593.css (500 error)

https://ondemand.jhuapl.edu/pun/sys/dashboard/assets/application-18125fdd4c5a8c2d98bbdf28ac71fb721d5dd0d75aa85d8f90387e1d927303a4.js (404 error)

Yea, what’s this output look like: /var/www/ood/apps/sys/dashboard/public/assets/.sprockets*.

It’s likely that you have two or more hidden .sprockets* files there. You’ll want to keep the only valid one and remove the others.

The valid one is a json file pointing to other valid files in that assets directory. So here’s an example of a container I have. I can just grep for a real filename ( 5a71c15 in this case) in my sprockets file and see that it’s there.

[jeff@d37e91cf5ad8 assets]$ ls -lrt
total 1076
-rw-r--r--. 1 root root   1457 Mar 23  2020 OpenOnDemand_stack_RGB-e9b21db6a659867fbf0ac60241622ebed7f74029c0498f09c72689c024011874.svg.gz
-rw-r--r--. 1 root root   3386 Mar 23  2020 OpenOnDemand_stack_RGB-e9b21db6a659867fbf0ac60241622ebed7f74029c0498f09c72689c024011874.svg
-rw-r--r--. 1 root root   2204 Mar 23  2020 OpenOnDemand_powered_by_RGB-cb3aad5ff5350c7994f250fb334ddcc72e343233ce99eb71fda93beddd76a847.svg.gz
-rw-r--r--. 1 root root   5610 Mar 23  2020 OpenOnDemand_powered_by_RGB-cb3aad5ff5350c7994f250fb334ddcc72e343233ce99eb71fda93beddd76a847.svg
-rw-r--r--. 1 root root   8983 Oct  8 14:45 turbolinks-697c499a81d3d7b23e98838ee9f9945412ff5caaddde17f7918d78f4997ae7a6.js.gz
-rw-r--r--. 1 root root  38274 Oct  8 14:45 turbolinks-697c499a81d3d7b23e98838ee9f9945412ff5caaddde17f7918d78f4997ae7a6.js
-rw-r--r--. 1 root root  41622 Oct 16 13:38 application-5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966.css.gz
-rw-r--r--. 1 root root 225095 Oct 16 13:38 application-5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966.css
-rw-r--r--. 1 root root 158652 Oct 16 13:38 application-2892928d592ea7a524d987c85a5e6b8bc2786aa8fd5a4bffe6c4158ea39020a9.js.gz
-rw-r--r--. 1 root root 586669 Oct 16 13:38 application-2892928d592ea7a524d987c85a5e6b8bc2786aa8fd5a4bffe6c4158ea39020a9.js
drwxr-xr-x. 2 root root   4096 Oct 16 13:40 font-awesome
drwxr-xr-x. 2 root root   4096 Oct 16 13:41 bootstrap
[jeff@d37e91cf5ad8 assets]$ grep -c 5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966 .sprockets-manifest-4e3406f5e610f427665890e47e6127ee.json 
1

Also you may have to do this for the other ruby apps as well (/var/www/ood/apps/sys/{file-editor,activejobs,myjobs}, so I’d check in on their UI too.

not quite sure which one to delete?

[root@aplcdhen01 ~]# ls -lart /var/www/ood/apps/sys/dashboard/public/assets/
total 1116
-rw-r--r-- 1 root root   8983 Aug 18 18:00 turbolinks-697c499a81d3d7b23e98838ee9f9945412ff5caaddde17f7918d78f4997ae7a6.js.gz
-rw-r--r-- 1 root root  38274 Aug 18 18:00 turbolinks-697c499a81d3d7b23e98838ee9f9945412ff5caaddde17f7918d78f4997ae7a6.js
-rw-r--r-- 1 root root  11864 Aug 18 18:00 .sprockets-manifest-c47593093860eba73c09e1d0ed80d2d5.json
-rw-r--r-- 1 root root   1457 Aug 18 18:00 OpenOnDemand_stack_RGB-e9b21db6a659867fbf0ac60241622ebed7f74029c0498f09c72689c024011874.svg.gz
-rw-r--r-- 1 root root   3386 Aug 18 18:00 OpenOnDemand_stack_RGB-e9b21db6a659867fbf0ac60241622ebed7f74029c0498f09c72689c024011874.svg
-rw-r--r-- 1 root root   2204 Aug 18 18:00 OpenOnDemand_powered_by_RGB-cb3aad5ff5350c7994f250fb334ddcc72e343233ce99eb71fda93beddd76a847.svg.gz
-rw-r--r-- 1 root root   5610 Aug 18 18:00 OpenOnDemand_powered_by_RGB-cb3aad5ff5350c7994f250fb334ddcc72e343233ce99eb71fda93beddd76a847.svg
-rw-r--r-- 1 root root  41622 Aug 18 18:00 application-5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966.css.gz
-rw-r--r-- 1 root root 225095 Aug 18 18:00 application-5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966.css
-rw-r--r-- 1 root root 158543 Aug 18 18:00 application-3fc53ea0ca03e3320863c528880444b4b88d3149634098bd67b0d8944c47ae80.js.gz
-rw-r--r-- 1 root root 586412 Aug 18 18:00 application-3fc53ea0ca03e3320863c528880444b4b88d3149634098bd67b0d8944c47ae80.js
-rw-r--r-- 1 root root  11460 Oct 30 20:20 .sprockets-manifest-74a72d59f647ac594923114b54fef409.json
drwxr-xr-x 2 root root   4096 Nov  4 13:08 bootstrap
drwxr-xr-x 4 root root   4096 Nov  4 13:09 ..
drwxr-xr-x 2 root root   8192 Nov  4 13:09 font-awesome
drwxr-xr-x 4 root root   4096 Nov  4 13:09 .

Yea that’s why I gave the grep example. grep for something like 5a71c15dc32e52ce12816788532d4913b76b0ddb742b75f7c58bfce4e8555966 (the real checksum filename of your application.js) in the sprockets files. You should see one file has it and the other doesn’t.

1 Like

Actually, you can just go by the file date. You see one is Oct 30 and the other is Aug 18th. The Oct 30th is likely the bad one. You can just rename if you’re more comfortable with that, any name other than .sprockets-manifest-*.json should be OK.

Thanks for the quick responses!

1 Like