Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Batches

If the batch cron job stops working

First, check the log file in log/whenever_cron.log to see if there are any error messages. If there aren't the lock file might be stuck. To ensure the batch job doesn't run more than one job at a time there is a lock file tmp/pids/batch_ingest.*. Delete the matching files and wait for the next run of the cron job.

Matterhorn

Ingest service reports as WARNING on Avalon's about/health page

When an ingest fails, it may leave the Matterhorn service in a bad state until subsequent ingests succeed. If you know that was not caused by a Matterhorn issue, you can bring its status back to OK by sanitizing the service:

1. Goto: http://MATTERHORN_URL:PORT
2. Login using credentials (IU: Test+server+documentation)
3. Goto: http://MATTERHORN_URL:PORT/docs.html?path=/services
4. Submit the sanitize form with serviceType=org.opencastproject.ingest&host=http://MATTERHORN_URL:PORT

Tomcat

Another Tomcat from a different repo was installed and replaced the old one

In Avalon 5.x and priors, we use a specific version of Tomcat from nul-repo. If a different version (for example one from epel) was installed, it will cause problems. To revert:

  • Move old logs: /usr/local/tomcat/logs /usr/local/tomcat/logs.old
  • Downgrade tomcat to 7.0.32-1.el6 from nul_public: sudo yum downgrade tomcat --disablerepo=epel

  • Restore server.xml, tomcat-users.xml and web.xml in fedora/WEB-INF with a working versions from github or another server

  • Restart Tomcat

  • No labels