Adminstartion UI not accessible from local

[gouravsukhija]

I am not able to access the admin UI from my local laptop even after exposing the port number 4414.

<.0.7/server/bin$ mqsilist DOCKER -e Exec_Grp_Common BIP1877I: REST API 'nw_services_oms_v1' on integration server 'Exec_Grp_Common' is running. BIP1273I: Shared library 'nw_common_subflows' is deployed to integration server 'Exec_Grp_Common'. BIP8071I: Successful command completion.

And even rest api is not accessible.

Command used to expose the port.

docker run -d --name iib10_common -p 4414:4414 dtr.nwie.net/dgs/iibv10.0.0.7base:Common

Any leads would be appreciated

[s-rogers]

Hi - what platform are you running your docker host on? On Windows using docker-machine you need to do an additional port forward from the VirtualBox vm hosting the docker machine to access it on your host

[gouravsukhija]

On Mon, Mar 6, 2017 at 5:08 AM Sam Rogers notifications@github.com wrote:

Hi - what platform are you running your docker host on? On Windows using docker-machine you need to do an additional port forward from the VirtualBox vm hosting the docker machine to access it on your host

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ot4i/iib-docker/issues/29#issuecomment-284354125, or mute the thread https://github.com/notifications/unsubscribe-auth/ARrV_YMiEaZH-LYnWC5ySHUxLCJx5dwCks5ri9ssgaJpZM4MSoZ1 .

Can you please send the steps to do it. My docker host is on linux.

[s-rogers]

If your docker host is on Linux, and you are on the host trying to access 4414 then I'm not sure why you are seeing an issue. If you are remotely accessing your Linux host, there might be firewall settings that need changing to allow you to access 4414 remotely. Other than that, it is worth checking your syslog in the container to check that the web admin actually started correctly - you should see a message stating it is listening on port 4414. You could confirm this inside the container using "netstat -a".

[gouravsukhija]

yes the webadmin message is fine. The broker is running fine. Even there is one service running inside the container on port 7800 which is running fine as well.

Let me know what can be the next step.

On Tue, Mar 7, 2017 at 6:16 AM, Sam Rogers notifications@github.com wrote:

If your docker host is on Linux, and you are on the host trying to access 4414 then I'm not sure why you are seeing an issue. If you are remotely accessing your Linux host, there might be firewall settings that need changing to allow you to access 4414 remotely. Other than that, it is worth checking your syslog in the container to check that the web admin actually started correctly - you should see a message stating it is listening on port 4414. You could confirm this inside the container using "netstat -a".

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ot4i/iib-docker/issues/29#issuecomment-284693694, or mute the thread https://github.com/notifications/unsubscribe-auth/ARrV_dJ3IFDRVmG0CbycuAS8Us9IF84Iks5rjTyegaJpZM4MSoZ1 .

[vinodmurgod]

Hi, I am new to the docker.... I followed the exact steps as mentioned in the read me file. I was able to successfully run the container. Below is the command i used "docker run --name myNode -e LICENSE=accept -e NODENAME=MYNODE -P iibv10image -p 4414:4414"

docker run --name myNode -e LICENSE=accept -e NODENAME=MYNODE -P iibv10image -p 4414:4414

Below are the log files: [root@vm-centos69 ~]# docker exec node1 tail -f /var/log/syslog Jul 12 16:35:20 c74af4eb03c9 rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted. Jul 12 16:35:20 c74af4eb03c9 rsyslogd-2145: activation of module imklog failed [try http://www.rsyslog.com/e/2145 ] Jul 12 16:35:20 c74af4eb03c9 rsyslogd: rsyslogd's groupid changed to 104 Jul 12 16:35:20 c74af4eb03c9 rsyslogd: rsyslogd's userid changed to 101 Jul 12 16:35:20 c74af4eb03c9 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] Jul 12 16:35:20 c74af4eb03c9 IIB[89]: IBM Integration Bus v10008 (MYNODE) [Thread 89] (Msg 1/1) BIP8873I: Starting the component verification for component 'MYNODE'. Jul 12 16:35:20 c74af4eb03c9 IIB[111]: IBM Integration Bus v10008 (MYNODE) [Thread 111] (Msg 1/1) BIP2001I: The IBM Integration Bus service has started at version 10008; process ID 116. Jul 12 16:35:21 c74af4eb03c9 IIB[116]: IBM Integration Bus v10008 (MYNODE) [Thread 116] (Msg 1/1) BIP2866I: IBM Integration Bus administration security is inactive. Jul 12 16:35:22 c74af4eb03c9 IIB[116]: IBM Integration Bus v10008 (MYNODE) [Thread 152] (Msg 1/1) BIP9153I: The MQTT pub/sub broker has started successfully, configured to listen on port 11883. Jul 12 16:35:24 c74af4eb03c9 IIB[116]: IBM Integration Bus v10008 (MYNODE) [Thread 167] (Msg 1/1) BIP3132I: The HTTP Listener has started listening on port '4414' for 'WebAdmin http' connections.

My System Set up is - Host Machine is Windows. Virtual Box: Centos 6.9 => in Centos 6.9, i am running Docker and IIB container is running.

So here, under which browser (Centos OS, Windows ) i should be viewing the IIB Admin Page ?

Can any one throw some light..

[s-rogers]

When running inside a VM on Windows you may need to port forward 4414 of the VM to your Windows host

[vinodmurgod]

I am using Bridge Adapter and hence ports and network is shared. Is there any other problem ?

[vivekbisengrk]

Hi Vinod, Sudo is missing in front of your command if you are running inside the VM of Oracle . Please try once. However after complete execution and making the container running . I am facing the issue in accessing the url with the mentioned port number 4414 inside the VM itself.

[s-rogers]

@vivekbisengrk @vinodmurgod are you still having issues accessing the webUI in a running container?

[dcb-robinson]

Looks like this isn't an issue anymore, hence closing