search

ibm-messaging / mq-container

Container images for IBM® MQ
Apache License 2.0
255 stars 189 forks source link

Web console won't start #404

Open Zeguym opened 4 years ago

Zeguym commented 4 years ago

When i create an instance on docker for windows i got the following error and can not access to the web console :

2020-05-22T14:56:25.801Z Creating queue manager QM1 2020-05-22T14:56:25.801Z Starting web server 2020-05-22T14:56:25.880Z Error 126 starting web server: AMQ5061E: Program 'strmqweb' cannot be run with root privileges. 2020-05-22T14:56:25.881Z Error starting web server: exit status 126

Did i do something wrong ? thanks

punitporwal07 commented 4 years ago

getting same error after attaching persistent volume to my deployment/pod and running image again in generic-k8s-cluster

Error 126 starting web server: AMQ5061E: Program 'strmqweb' cannot be run with root privileges.

plz suggest if you managed to get it fixed ; thanks

arthurbarr commented 4 years ago

Can I please confirm which version of MQ you are using. If it's MQ 9.2, are you using the non-install MQ packages?

arthurbarr commented 4 years ago

Also, the rest of the log would be useful, as it describes a bit more of this sort of information, users, capabilities etc.

Zeguym commented 4 years ago

I finally managed to find the problem recently: I my case i was on docker for windows and the persistent folder was mapped on a windows folder. So, the users credentials was not working on windows file system (now I found the problem it's seems obvious). I switched to WSL2 use a docker volume for persistent data and used the share to access to content if needed. Work like a charm now.

Sorry for the false alert

punitporwal07 commented 4 years ago

Can I please confirm which version of MQ you are using. If it's MQ 9.2, are you using the non-install MQ packages?

@arthurbarr I am running on IBM MQ V9.1.5.0 with Image tag: ibm-mqadvanced-server-dev:9.1.5.0-r1-amd64 .

punitporwal07 commented 4 years ago

Also, the rest of the log would be useful, as it describes a bit more of this sort of information, users, capabilities etc.

here is the log trace as container starts:

`2020-10-29T11:02:15.377Z CPU architecture: amd64 2020-10-29T11:02:15.377Z Linux kernel version: 3.10.0-1062.9.1.el7.x86_64 2020-10-29T11:02:15.377Z Container runtime: kube 2020-10-29T11:02:15.377Z Base image: Red Hat Enterprise Linux 8.1 (Ootpa) 2020-10-29T11:02:15.377Z Running as user ID 0 with primary group 0 2020-10-29T11:02:15.377Z Capabilities (bounding set): chown,dac_override,fowner,fsetid,kill,setgid,setuid,setpcap,net_bind_service,net_raw,sys_chroot,mknod,au dit_write,setfcap 2020-10-29T11:02:15.377Z seccomp enforcing mode: disabled 2020-10-29T11:02:15.377Z Process security attributes: system_u:system_r:spc_t:s0^@ 2020-10-29T11:02:15.378Z No volume detected. Persistent messages may be lost 2020-10-29T11:02:15.508Z Using queue manager name: QM1 2020-10-29T11:02:15.536Z Created directory structure under /var/mqm 2020-10-29T11:02:15.536Z Image created: 2020-03-31T06:57:13+00:00 2020-10-29T11:02:15.536Z Image tag: ibm-mqadvanced-server-dev:9.1.5.0-r1-amd64 2020-10-29T11:02:15.554Z MQ version: 9.1.5.0 2020-10-29T11:02:15.554Z MQ level: p915-ifix-L200325.DE 2020-10-29T11:02:15.554Z MQ license: Developer 2020-10-29T11:02:16.700Z Creating queue manager QM1 2020-10-29T11:02:16.700Z Starting web server 2020-10-29T11:02:16.736Z Error 126 starting web server: AMQ5061E: Program 'strmqweb' cannot be run with root privileges.

2020-10-29T11:02:16.736Z Error starting web server: exit status 126 2020-10-29T11:02:21.555Z Created queue manager 2020-10-29T11:02:21.564Z Removing existing ServiceComponent configuration 2020-10-29T11:02:21.564Z Starting queue manager ` here is a snip from my deployment manifest: image