search

ibm-messaging / mq-container

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

Ibmmq start failure #488

Open ALekseiMokhov opened 2 years ago

ALekseiMokhov commented 2 years ago

Given: Linux mint, docker, script: docker run \ --env LICENSE=accept \ --env MQ_QMGR_NAME=QM1 \ --env MQ_ENABLE_METRICS=true \ -p 1414:1414 \ -p 9443:9443 \ --detach \ --env DEBUG=true \ ibmcom/mq It stopped running one day, in logs I see last strings: 2021-12-17T11:10:01.978Z MQ version: 9.2.4.0 2021-12-17T11:10:01.978Z MQ level: p924-L211105.DE 2021-12-17T11:10:01.978Z MQ license: Developer full logs - https://pastebin.com/AyLAn8RB

After I stop. remove it, run it again &again I made some hypothesises: 1) It sometimes starts withought detach mode normally; 2) If I write localhost in -p command(-p 127.0.0.1:9443:9443) it 's chances to succeed increases; 3) I did not change any firewall settings since the first container run; Any suggestions? How could I run it with a predictable result?

ALekseiMokhov commented 2 years ago

Inside container I see no failures, and curl shows like: bash-4.4$ curl http://localhost:9443 curl: (7) Failed to connect to localhost port 9443: Connection refused

arthurbarr commented 2 years ago

As per the docs, dspmq error code 72 is a "Queue manager name error". From the logs, it doesn't look like it's even trying to start the web server, as the queue manager fails to start (though note I think you need to use HTTPS for the web server). I don't know why "QM1" is giving a name error, though I wonder if there's a permissions error in the filesystem, which is preventing it from reading an INI file. If you run the container with --env DEBUG=true, it will print out the file permissions, which might be helpful.