Resque admin panel

If a file doesn't get characterized correctly the first thing to do is check the resque admin panel. There you can view failures and restart jobs. If you see a clear stack trace pointing to a bug this may not help, but if you see a vague error about "deadlock?" this might work. Restart the job and then check the site to see whether the derivatives came through.

1. ssh to the machine
2. edit /opt/sufia-project/current/config/initializers/resque_admin.rb
3. Add 'return true' before the end of the method
4. Save the file and restart the application
5. Navigate in the browser to, e.g., hydra.chemheritage.org/admin/queues
6. Make sure to change the initializer back when you are done

This process will improve once we have admin users in place; you'll just be able to log in and navigate straight to this page.

What version of fedora is running?

...