Most functions under File app are not working

Get Help
1

Hi,

We are running OOD 3.1.7 on one of our HPC clusters and noticed that most functions under File app are not working. i.e. Upload, Copy/Move, Delete won’t work but New File and New Directory are working fine. Any idea where we can start troubleshooting? Thank you!

P.S. we are using the same OOD version on other clusters and there have been no issues.

P.S.S. We’ve done some configuration changes on the dashboard but haven’t touched file app so not sure if that’s related.

-GZ

2

Is there anything in the logs that jump out? I wonder if there’s something small, like a typo, in the config change somehow causing this.

3

Thanks for the suggestion. I did not see anything related in the logs. In fact, I did a inspect on the element and noticed that those buttons (e.g. upload) do not have any event associated with it. So guess those buttons are not actually functioning?

If we want to look into the config files related to files app, what specific ones should we start? I did a quick check and didn’t notice anything obvious wrong.

4

The various settings for files can be found in the Customizations section of our docs in a few areas. You can use the Table of Contents on the side of the page to see some of them scattered throughout the page, but here’s a direct link to the Upload section:

I was mainly curious if you’d set anything like FILE_UPLOAD_MAX=0 but even if you had, that would not remove the event associated with clicking the upload button. This sounds like the assets did not compile correctly for the app and therefore some JS is missing. And thinking on it, this seems especially likely if the form functions fine for New Directory and New File which don’t need any JS.

You can check by doing a forced refresh on the page with the dev tools open and see if the application-1234556.js shows up or if it is a 404 in which cas it is missing and the culprit.

Is this a production server or test? If it’s production there’s a safer way than just issuing bin/setup to just build the assets and hopefully resolve the missing JS.

If it’s just a test or dev server:

cd /var/www/ood/apps/sys/dashboard
bin/setup

But, if this is production you will likely want to do a more targeted fix and try to resolve this by only trying to rebuild the assets and serve them correctly as the user running apache:

cd /var/www/ood/apps/sys/dashboard
# remove the old assets to ensure no conflicts
sudo -u apache RAILS_ENV=production bin/rails assets:clobber
# build off the frozen lock file to ensure we keep dependencies stable
sudo -u apache RAILS_ENV=production bin/yarn install --frozen-lockfile
# rebuild the assets using rails
sudo -u apache RAILS_ENV=production bin/rails assets:precompile
# restart OOD to get the new assets in memory
sudo systemctl restart ondemand

Hopefully this is not a production system as that may be a bit trickier, but the above should work to only target the asset rebuild.

5

Thank you so much for those information! Yeah, we finally tracked down all the changes to the files.html.erb file in layouts folder, in which we have linked the following config into files app but it was accidentally removed while we are doing cluster transfer:

<%= render partial: 'layouts/config' %>

So the files app cannot be initialized with the right config.

After adding the line back everything is working as expected! Very nice to learn those restarting process (especially for production server)!

1 Like