New post
Question
· Nov 13, 2019

'Failed to access iris.lck file'

#InterSystems IRIS for Health

Hi I am getting this message for some databases but not for others:  This database is mounted as read-only due to 'Failed to access iris.lck file'! and not for others on Google Cloud community non-health edition. 

For example this default database displays the message: Name    IRISLIB Directory    /usr/irissys/mgr/irislib/

But this default database does not:  Name    IRISSYS Directory    /ISC/dur/mgr/

I have loaded IHS FOIA RPMS and am getting the message and <PROTECT> errors when running programs. Permissions on disk look ok to me, changed to the same as the default databases.  Insight on how to permissions working and get <PROTECT> errors to not happen? 

-- IV

Discussion (3)0
Log in or sign up to continue
Robert Cemper · Nov 13, 2019

by default IRISLIB is always read-only mounted as it holds most of system methods, utilities, compiles, ...
all code that just executes but not changes during runtime  and that you should not try to change

differently, IRISSYS holds all dynamic system data that can change during runtime and therefore requires read-write access
As configurations, namespace tables, .....

Though with system management privileges you may change this.
But I'd recommend not to touch it unless you are an in-depth IRIS expert.

0 0
Ignacio Valdes · Nov 13, 2019

Thank you for the response.  The solution was that the directory group had to be set to 52773.  This doesn't appear in the ISC permissions guide. There are contradictions between what was pre-setup in the cloud instance and the permissions guide: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_using_unix

It refers to irisowner irisusr which does not appear in /etc/passwd or /etc/group and the actual databases themselves seem to be usually set to owner:group 51773 52773 which also doesn't appear in /etc/passwd or /etc/group.

0 0