Closed peer35 closed 1 year ago
There is a cronjob that runs as user irods:
0 2 * /bin/bash $HOME/.irods/cronjob-revision-cleanup.sh >> $HOME/iRODS/server/log/cronjob-revision-cleanup.log 2>&1
This executes rule:
{{ /etc/irods/irods-ruleset-research/tools/revision-clean-up.r}}
I started this by hand and monitored the process, the system runs out of memory due to process "irodsAgent" while just looping through the records.
Not a critical issue at the moment, because most AIMMS files are static, so will only have one revision.
This is a known issue in the iRODS version used by Yoda 1.2.
Solution is to upgrade Yoda.
Aimms yoda no longer in use
There is a cronjob that runs as user irods:
0 2 * /bin/bash $HOME/.irods/cronjob-revision-cleanup.sh >> $HOME/iRODS/server/log/cronjob-revision-cleanup.log 2>&1
This executes rule:
{{ /etc/irods/irods-ruleset-research/tools/revision-clean-up.r}}
I started this by hand and monitored the process, the system runs out of memory due to process "irodsAgent" while just looping through the records.
Not a critical issue at the moment, because most AIMMS files are static, so will only have one revision.