-
Notifications
You must be signed in to change notification settings - Fork 115
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
Trying to run this image on Openshift but getting the permission error. #48
Comments
Hi, thanks for raising the above issue with me. Could you please provide some more information to help me investigate. What image are you using? Has the image been customised in any way? What command are you using to start the container? |
I think openshift uses a dynamically generated UID to run the container and hence - right now I am failing on the starting the rsyslog in iib_manage.sh sudo /usr/sbin/rsyslogd I did one customization is to change access to the /var/mqsi/ directly and it worked. RUN chgrp -R 0 /var/mqsi/ && The dynamically generated user id doesnt have access to run rsyslog Sourcing profile | ---------------------------------------- |
With regards to your /var/mqsi edits, I am not sure that changing the group ownership to be root is a good idea, as the iibuser (or any other member of mkbrkrs) would not be able to run anything. You would have to run everything as the root user! I am not sure that I can easily make a change to get this working since it is the OpenShift infrastructure that is causing the issue. Unfortunately, we do not currently support running on OpenShift, but we do support running on Kubernetes and IBM Cloud Private. Alternatively, you might like to try our ace-docker image (https://github.com/ot4i/ace-docker), which is our latest offering (IIB version 11 renamed to App Connect Enterprise version 11), engineered for the cloud. It has the same support as the iib-docker image in terms of Kubernetes / IBM Cloud Private, but you may not have the same issues as it doesn't use sudo to start the syslog (or any other command). |
In case you've not seen it, this closed issue may also be of interest: #25 |
Failed to open file /var/mqsi/registry/BIP15063/HASharedWorkPath with error Perm
ission denied
BIP2113E: Integration node internal error: diagnostic information ''Permission d
enied'', '13', ''/var/mqsi/registry/BIP15063/HASharedWorkPath''.
An internal software error has occurred in the integration node. Further messag
es will indicate the effect of this error on the integration node's transactions
.
Shutdown and restart the integration node. If the problem continues to occur, t
hen restart the system. If the problem still continues to occur contact your IB
M support center.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and
ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbr
krs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support
center.
Node MYNODE does not exist...
Creating node MYNODE
Failed to open file /var/mqsi/registry/MYNODE/HASharedWorkPath with error Permis
sion denied
Failed to open file /var/mqsi/registry/MYNODE/HASharedWorkPath with error Permis
sion denied
BIP8081 An exception was caught while processing the command, 'Unable to format
an ImbException message for output, ImbException message number is BIP2113'.
The text was updated successfully, but these errors were encountered: