-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Fixity checks running #8
Comments
Lea Ann: Working on getting the code running where I can create a fileset locally to run the task. Rob suspects this is an issue with production fedora setup, but we need to get this running locally to see if it's an application error or an issue with the configuration on prod Created a rake task and cron job to run fixity checks on a regular basis. We may or may not need that code to be merged. |
https://gitlab.com/notch8/cal-state-hyrax/-/merge_requests/12 |
I didn't see the link to the gitlab pr before I created the rake tasks above. (no cron job though) I'll see what happens on their prod server with the tasks I've created before determining/discussing whether we need to add the cron job and task from the pr. conversation with david about testing this work on prod is happening in slack. |
Chron job: #17 |
Error found on the server: $ cat /var/log/hyrax/fixitycheck.log
2023-11-26 03:21:01+00:00 bundler: command not found: rails
Install missing gem executables with `bundle install`
failure
2023-11-27 03:18:01+00:00 bundler: command not found: rails
Install missing gem executables with `bundle install`
failure |
Script to create works / bypass broken forms ( a = AdminSet.find <admin set ID>
50.times do |i|
Dataset.create(title: ["test #{i}"], campus: ['Sacramendo'], admin_set_id: a.id, depositor: "[email protected]")
end |
The PR for this was merged on Aug 8 |
David will review and test and provide feedback |
Story
Links to: https://github.com/csuscholarworks/scholarworks/issues/58
Acceptance Criteria
/etc/cron.daily/hyrax_fixity_check.sh
uses the full path to therails
executable (/usr/local/bin/rails
)1hyrax_0
,hyrax_1
)calstate:all_files_fixity_check
rake task leverages theHyrax::FileSetFixityCheckService
2 (see example diff below)Example diff
1
cron
tasks run in a limited environment and don't have access to the "normal"$PATH
, thus the full path is required. Without it, it throws errors like this2 Currently, the rake task is configured to run on every version of every file every day. This is not desired behavior. The
Hyrax::FileSetFixityCheckService
has logic built in to wait X amount of time before checking the same file againTesting Instructions
ssh
into the production server (e.g.hyrax_0
)cron
task automatically runs overnight/var/log/hyrax/fixitycheck.log
file to see if the task ran successfullyYYYY-MM-DD
for yourgrep
ping convenienceThe text was updated successfully, but these errors were encountered: