Hi Jerzy,
This does look like a DNS problem. There are a couple of things we could try to narrow down the issue.
1) We should take a look at the websocket request coming from the browser. If you open the Network tab, then open a new notebook, you should see a websocket request start up, and then fail. The hostname should correspond to the same hostname as your jupyter server.
2) If the hostname is correct, DNS resolution is most likely not working. You could try building the jupyter server with its public IP instead of its hostname to see if that fixes your issue. To change this value, open up <install-directory>/dist/scripts/unix/config.conf and find the entry for HOST_NAME. By default, this uses your linux's $(hostname). You can modify this to be the Linux machine's IP instead, then rebuild and restart the jupyter server.
Hope that helps,
Rob
------------------------------
ROBERT MCAULEY
------------------------------
Original Message:
Sent: Fri October 04, 2019 10:40 AM
From: Jerzy Konarski
Subject: Jupiter Netbook configuration files
Robert,
I think it's a routing problem. I tried it:
I added Jupiter machine to AD, it did not change the problem of connection to the kernel. As soon as I referenced the Jupyter machine in the DNS, it works. What I find bizzard is that I should have had the same effect with the modification of hosts files. Or it is not enough and there is also the interaction with the browser? But I configured the Jupyter server address in IP.
There is something that I do not understand, but say that it is rather the problem of DNS.
Thank you for your help.
Jerzy
------------------------------
Jerzy Konarski
Original Message:
Sent: Fri October 04, 2019 10:03 AM
From: ROBERT MCAULEY
Subject: Jupiter Netbook configuration files
Hey Jerzy,
We typically observe kernel connection issues if there is a gateway in front of CA that is not configured properly to route the websocket request from the browser.
If you have an apache gateway, you can follow section 4 of this document:
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_config_ish_with_ssl.html#task_d1m_35h_x1b__apache_gateway_step
If you have an IIS gateway, you can follow section 6 d of this document:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html
Let me know if that helped, or if you aren't using a gateway at all.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Thu October 03, 2019 04:26 PM
From: Jerzy Konarski
Subject: Jupiter Netbook configuration files
Hi,
I spoke too fast, Notebook start effectively, but is not connected to kernel.
The strange thing is that it does not work at all when I use the Jupyter server IP address, the connection works when I use (manage / environment) Jupyter server logical name. :( I really do not understand.
The other server - the one that is in AD - works fine, but my client does not want to put Linux servers in AD.
------------------------------
Jerzy Konarski
Original Message:
Sent: Thu October 03, 2019 02:18 PM
From: ROBERT MCAULEY
Subject: Jupiter Netbook configuration files
Not a problem Jerzy.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Thu October 03, 2019 02:03 PM
From: Jerzy Konarski
Subject: Jupiter Netbook configuration files
Thanks for this answer,
My URI for external applications was http://win2012r2-cog11:9300/bi/v1/disp. I puted the fully qualified domain name into, and ...
IT WORK, great,
BIG THANKS Robert
jerzy
------------------------------
Jerzy Konarski
Original Message:
Sent: Thu October 03, 2019 11:09 AM
From: ROBERT MCAULEY
Subject: Jupiter Netbook configuration files
That looks like the Jupyter server is attempting to reach Cognos at:
host=win2012r2-cog11
port=9300
At first glance, that host name looks incorrect. The Jupyter server relies on a variable within your Cognos Configuration called "Dispatcher URI for External Applications". If you can, please update that variable with the fully qualified domain name of your Cognos server. There's no need to restart the jupyter server, however you would need to restart Cognos.
Let me know if that works for you,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Thu October 03, 2019 10:57 AM
From: Jerzy Konarski
Subject: Jupiter Netbook configuration files
Hi Robert,
I have informed all ID's, but It change nothing to my problem. And the my problem is the following. I instaled Jupiter on CentOS Linux and it work fine, one one condition : my jupiter server must be part of Active Directory.
It is completely impossible for me to run the link between CA server and Jupe server if both are not referenced in AD.
I filled in the hosts files, I can ping one server from an other, but when I try to create a notebook I have a message :
"Internal Server Error
Sorry! Something went wrong - Please review your Notebook configuration in the administration panel or contact your CA administrator."
When I look in Jupiter log I have messages like :
upyterHub __init__:111] Error connecting to Cognos Analytics (ConnectionError occurred). Arguments:
(MaxRetryError("HTTPConnectionPool(host='win2012r2-cog11', port=9300): Max retries exceeded with url: /bi/v1/me (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8de5435eb8>: Failed to establish a new connection: [Errno -2] Name or service not known',))",),)
;
[W 2019-10-03 14:40:00.310 JupyterHub web:1669] 500 GET /bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 (::ffff:10.0.4.205): Error connecting to Cognos Analytics (ConnectionError occurred). . Contact CA Administrator for details.
And I do not know what to do to solve the problem, realy
------------------------------
Jerzy Konarski
Original Message:
Sent: Thu October 03, 2019 07:04 AM
From: ROBERT MCAULEY
Subject: Jupiter Netbook configuration files
Hi Jerzy,
1) The files within ../scripts are Dockerfiles that are used to build the docker images for the jupyter server. The variable NB_USER is for the
non-root user within the containers, "ca_user". DOCKER_GROUP_UID is the UID of the docker group on your host machine, in order to give
ca_user the permissions to use the docker socket on the host machine.
2) It is advisable to create ca_user, otherwise anyone opening a notebook in Cognos will have root privileges in that Docker container. Does the error message cause the build to fail by any chance?
3) The "hostname" parameter is used to ensure proper routing to the host machine. Feel free to modify this value if your network situation requires it.
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Wed October 02, 2019 04:22 AM
From: Jerzy Konarski
Subject: Jupiter Netbook configuration files
Hello,
I ask myself a lot of questions about the installation of Notebook.
1. Has anybode an idea what are the files that are in the ... / scripts folder for ?
- Dockerfile_hub (NB_USER and DOCKER_GROUP_UID settings ),
- Dockerfile_server-instance,
- Dockerfile_viewer
2. Is it necessery (or advisable) to creat linux user "ca_user" ? I have the message "directory /home/ca_user..." not exist when I execute build.sh script.
It is the most important. If anyone has answers that would be great
------------------------------
Jerzy Konarski
------------------------------
#CognosAnalyticswithWatson