Hi beloved members of the Community!
It is very common in the daily life of IRIS or Health Connect users that it is necessary to install new instances or update the ones they already have and in many cases it is not these same users who carry out the installation, but rather systems personnel who often do not take into account the particularities of the assignment of permissions necessary for the installation.
An incorrect assignment of permissions will cause a series of erroneous operations that will produce a feeling of uncertainty and distrust in users that is later very difficult to solve. To avoid these problems, InterSystems provides users with the filecheck function that will allow us to review the permissions of all the files in the standard IRIS / Health Connect installation.
How does filecheck work?
Well, it couldn't be simpler, you just need to run the following command in a terminal on your server:
iris filecheck <instance>Replacing the <instance> with the name of the instance you are working with, the command will check the filecheck.isc configuration file located in the /mgr path of your installation and line by line it will check the permissions assigned to each file against those indicated on the line. Let's take a look inside that file:
filecheck.isc 1
[InstallDir]
dr-x------ irisowner irisowner /usr/irissys/
[RegistryDir]
drwxr-xr-x irisowner irisowner /home/irisowner/irissys/
/home/irisowner/irissys/
-rwxr-xr-x irisowner irisowner ISCAgent
-r-xr-xr-x irisowner irisowner ISCAgentUser
-rw-r--r-- irisowner irisowner Registry.XML
-rwxr-xr-x irisowner irisowner iris
-rw-r--r-- irisowner irisowner iris.reg
-rwxr-xr-x irisowner irisowner irisdb
-rwxr-xr-x irisowner irisowner irissession
-rwxr-xr-x irisowner irisowner libicudata.so
-rwxr-xr-x irisowner irisowner libicudata.so.69
-rwxr-xr-x irisowner irisowner libicudata.so.69.1
-rwxr-xr-x irisowner irisowner libicui18n.so
-rwxr-xr-x irisowner irisowner libicui18n.so.69As you can see, the file contains the permissions that each file must have for its correct operation.
In case you cannot find the filecheck.isc file you can always recreate it by running the following command:
iris filecheck <instance> updateAgain replacing the <instance> with the name of your instance. With this command the file will be regenerated.
With the file correctly regenerated, you can run the filecheck command again without any problem, which, once the review of the files is finished, will leave you again in the /mgr path a file called filecheck.log with the result of the review. Let's see what this log file looks like:
Expected Database Permission *rwx****** doesn't match current dr-xr-xr-x for /usr/irissys/mgr/irislib/
Expected Database Permission *rwx****** doesn't match current dr-xr-xr-x for /usr/irissys/mgr/enslib/
Expected Stream Permission *rwx****** doesn't match current dr-xr-xr-x for /usr/irissys/mgr/irislib/stream
Expected Stream Permission *rwx****** doesn't match current dr-xr-xr-x for /usr/irissys/mgr/enslib/stream
As you can see, it is a fairly descriptive log indicating the permissions it expects to find on certain routes and the permissions actually assigned to that route.
You can take a look at the documentation here . I hope you find it useful!
Open Exchange.png)
.png)
.png)
.png)