Closed EPNSED closed 3 years ago
I see two things -
you're running unreleased code, so there are no claims that things are in a working state with whichever commit you built yourself
the data objects listed are all in an INTERMEDIATE state (as denoted by the ?
in the ils
output) and will not be available for opening/reading/writing by any client.
We will not be able to reproduce what you're seeing unless we know which code you're running - can you share the git commit SHAs of:
Of course, please also include if you've made any changes before compiling.
Hi @trel Here is the SHAs
[neranjan@arclogin02 irods_client_icommands]$ git rev-parse --verify HEAD
befe37b0b1e1ce5df38973ab281e19d522d1622c
[neranjan@arclogin02 irods]$ git rev-parse --verify HEAD
ee116cbc7cf90f6b0960e596b0b7ebf97877393b
[neranjan@arclogin02 irods_rule_engine_plugin_logical_quotas]$ git rev-parse --verify HEAD
67e8641707a9f9bbdf0ce7db35db4ad4c3b936f4
Question, any hint why data objects are in INTERMEDIATE state? How to avoid this?
The intermediate states have not yet been released - they are landing in 4-2-stable now and will be included in 4.2.9.
They'll land in master at the same time and be first released there with 4.3.0.
You're running intermediate intermediate code :)
:) Ok, We will try 4.2.8 then. Thanks for looking into this
We are setting up a new irods instance (v. 4.3.0) Setup seems to be working, however, when we enable logical quotas we are getting "Logical Quotas Policy: Insufficient privileges" when we try to use iput command
The above command resulted in the following error in the log files
We set the logical quota using the following method
We create start_monitoring_collection.r with the following content
then execute the rule with the following command
irule -r irods_rule_engine_plugin-logical_quotas-instance -F start_monitoring_collection.r
Some more info that might help
What could be the issue here?