Other problem resolved, still Kernal Dead...this is the log excerpt also if you look at the bottom in bold, it is from an earlier session that timed out, and it appears to have thought it was still running....
12:24:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:24:22.526 JupyterHub proxy:301] Checking routes
12:29:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:29:22.526 JupyterHub proxy:301] Checking routes
12:34:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:34:22.526 JupyterHub proxy:301] Checking routes
12:39:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:39:22.526 JupyterHub proxy:301] Checking routes
12:44:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:44:22.526 JupyterHub proxy:301] Checking routes
12:49:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:49:22.525 JupyterHub proxy:301] Checking routes
[I 2020-02-26 12:51:24.284 JupyterHub log:158] 302 GET /bi/v1/jupyter/notebooks/new?kernel_name=python3 -> /bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 (@::ffff:172.18.0.1) 1.23ms
[I 2020-02-26 12:51:24.468 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 -> /bi/v1/jupyter/hub/login?next=/bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 (@::ffff:172.18.0.1) 116.38ms
[I 2020-02-26 12:51:24.556 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/login?next=/bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 -> /bi/v1/jupyter/hub/ibmcalogin?next=%2Fbi%2Fv1%2Fjupyter%2Fhub%2Fnotebooks%2Fnew%3Fkernel_name%3Dpython3 (@::ffff:172.18.0.1) 1.40ms
[W 2020-02-26 12:51:24.827 JupyterHub base:311] Invalid cookie token
[I 2020-02-26 12:51:24.831 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/ibmcalogin?next=%2Fbi%2Fv1%2Fjupyter%2Fhub%2Fnotebooks%2Fnew%3Fkernel_name%3Dpython3 -> /bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 (xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@::ffff:172.18.0.1) 198.41ms
[I 2020-02-26 12:51:25.034 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/notebooks/new?kernel_name=python3 -> /bi/v1/jupyter/hub/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/caload/notebooks/new?kernel_name=python3&trust=jupyter (xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@::ffff:172.18.0.1) 117.56ms
[I 2020-02-26 12:51:25.269 JupyterHub dockerspawner:452] Container 'ca_jupyter-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw' is gone
[I 2020-02-26 12:51:25.276 JupyterHub spawner:643] Setting env CULL_TIMEOUT to 3600
[I 2020-02-26 12:51:25.394 JupyterHub dockerspawner:540] Created container 'ca_jupyter-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw' (id: a47be9d) from image ca_jupyter_server_instance:latest
[I 2020-02-26 12:51:25.394 JupyterHub dockerspawner:557] Starting container 'ca_jupyter-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw' (id: a47be9d)
[I 2020-02-26 12:51:27.677 JupyterHub base:726] User xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw took 2.524 seconds to start
[I 2020-02-26 12:51:27.678 JupyterHub proxy:242] Adding user xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw to proxy /bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/ =>
http://172.18.0.4:888812:51:27.680 - info: [ConfigProxy] Adding route /bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw ->
http://172.18.0.4:888812:51:27.681 - info: [ConfigProxy] 201 POST /api/routes/bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw
[I 2020-02-26 12:51:27.687 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/caload/notebooks/new?kernel_name=python3&trust=jupyter -> /bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/caload/notebooks/new?kernel_name=python3&trust=jupyter&redirects=1 (xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@::ffff:172.18.0.1) 2578.06ms
[I 2020-02-26 12:51:27.693 JupyterHub log:158] 200 GET /bi/v1/jupyter/hub/api (@172.18.0.4) 0.94ms
[I 2020-02-26 12:51:28.271 JupyterHub log:158] 302 GET /bi/v1/jupyter/hub/api/oauth2/authorize?client_id=jupyterhub-user-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw&redirect_uri=%2Fbi%2Fv1%2Fjupyter%2Fuser%2FxQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw%2Foauth_callback&response_type=code&state=[secret] -> /bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/oauth_callback?code=[secret]&state=[secret] (xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@::ffff:172.18.0.1) 38.63ms
[I 2020-02-26 12:51:28.489 JupyterHub log:158] 200 POST /bi/v1/jupyter/hub/api/oauth2/token (
xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@172.18.0.4) 99.93ms
[I 2020-02-26 12:51:28.593 JupyterHub log:158] 200 GET /bi/v1/jupyter/hub/api/authorizations/token/[secret] (
xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw@172.18.0.4) 58.98ms
12:54:22.525 - info: [ConfigProxy] 200 GET /api/routes
[I 2020-02-26 12:54:22.602 JupyterHub proxy:301] Checking routes
[I 2020-02-26 11:25:50.828 JupyterHub log:158] 307 DELETE /bi/v1/jupyter/shutdown/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw (@172.18.0.4) 1.15ms[I 2020-02-26 11:25:50.901 JupyterHub proxy:264] Removing user xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw from proxy (/bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw/)11:25:50.903 - info: [ConfigProxy] Removing route /bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw11:25:50.904 - info: [ConfigProxy] 204 DELETE /api/routes/bi/v1/jupyter/user/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw[I 2020-02-26 11:25:50.911 JupyterHub dockerspawner:628] Stopping container ca_jupyter-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw (id: 8df3a54)[W 2020-02-26 11:26:00.902 JupyterHub base:892] User xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw: server is slow to stop[I 2020-02-26 11:26:00.903 JupyterHub log:158] 200 DELETE /bi/v1/jupyter/hub/shutdown/xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw (@172.18.0.4) 10071.31ms[I 2020-02-26 11:26:01.811 JupyterHub dockerspawner:634] Removing container ca_jupyter-xQWVnb25VSzp1Ojc4YmJlZjRjOTljZWE2NDBiNGIwODcxYzM0Y2FiOWUw (id: 8df3a54)/opt/conda/lib/python3.6/site-packages/sqlalchemy/orm/persistence.py:1066: SAWarning: DELETE statement on table 'servers' expected to delete 1 row(s); 0 were matched. Please set confirm_deleted_rows=False within the mapper configuration to prevent this warning.------------------------------
Kurt Blevins
Aegon UK
------------------------------
Original Message:
Sent: Tue February 25, 2020 03:03 PM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
Looking at the logs, it appears to be CORS related:
"Blocking Cross Origin WebSocket Attempt. Origin: http://win000176:9300"
It's definitely odd that it would stop working all of a sudden... would you mind checking the variable "Gateway URI" in your cognos configuration? This is what is compared to the browser's Origin header for added security.
For example, if you navigate to "http://win000176:9300" to reach Cognos, but the Gateway URI parameter is set to something different, a cross-origin error will occur. We just need to make sure the Gateway URI matches "http://win000176:9300". Hope that helps.
------------------------------
ROBERT MCAULEY
------------------------------
Original Message:
Sent: Tue February 25, 2020 09:19 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
I have attached a file, out of the blue it stopped working, 3 different browsers, 3 different errors... kernel starts and dies..
I did a complete uninstall of jupyter as well as docker, same exact thing....not sure this product was ready to go to market.
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Tue February 18, 2020 02:56 PM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
Hey Kurt,
For the DNS issue, I don't suppose you have an internal DNS server in your organization, do you?
If so, there's a way in Docker Desktop for you to configure it.
If you right-click the docker icon on the bottom right corner -> Settings -> Daemon and switch the toggle button from "basic" to "advanced", you should be able to add the DNS server. My config now looks like:
{
"registry-mirrors": [],
"insecure-registries": [],
"debug": true,
"experimental": false,
"dns": ["8.8.8.8", "<custom DNS server IP here>"]
}
Docker should restart after you save that config. You may need to run the `start.bat` script to launch the notebook server again, although it should come back up on its own once Docker restarts.
For the Docker shutting down problem, I personally haven't experienced it before, but I'll run some tests on my own Windows 10 machine and get back to you.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Mon February 17, 2020 06:29 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
Hi Rob,
I don't see my previous post so will say that again... 2 fails and 1 & 3 work. Also, noticed this on Friday, when I log off the machine, docker shuts down and is not available. Kind of strange, good thing CA does not do that...
Cheers,
Kurt
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Fri February 14, 2020 12:21 PM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
Hi Kurt,
Let's try an experiment to see where the DNS issue is. Can you try the following:
1) On your jupyter box, try pinging your Cognos box by hostname (hopefully this works)
2) On your jupyter box, enter the jupyter docker container (docker exec -it -u 0 ca_jupyter_hub bash) and try pinging your Cognos box by hostname (I assume this will fail)
3) On your jupyter box, enter the jupyter docker container, and try pinging any public domain (Hopefully this works)
If 1 fails, it's most likely a networking problem between your two boxes (could be related to the different gateway servers)
If 2 fails but 1 & 3 passes, the DNS server in your jupyter box isn't being used by the docker container, and it's defaulting to google's DNS server (8.8.8.8)
If 2 & 3 fails, but 1 passes, it looks like DNS isn't working at all within the docker container.
Let me know what comes from this experiment. Unfortunately these Docker DNS issues aren't always easy to diagnose. Once we get a clear picture of where it's failing, we can look into a solution together.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Fri February 14, 2020 09:54 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
Hi Robert,
Update for you, finally got them to talk to each other, but I can't use the name of the Server, I have to put the IP address in the Dispatcher for External ….. It took some start/stops/builds /restart/Cognos refresh the setting in systems environ. The only the I can come up with that might be a cause is the machines are on different gateway servers, which would be strange, since I could ping either machine.
Thanks for you help!
Cheers,
Kurt
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Thu February 13, 2020 10:20 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
found this in the cogserver.log file: 2020-02-13T15:14:01.767+0000 ERROR com.ibm.bi.platform.commons.web.BIResponseWrapper [Default Executor-thread-213] qylyMd8d9lyl4Cjdqw4Cdvq4wM24hdh4dwq4M84h qylyMd8d9lyl4Cjdqw4Cdvq4wM24hdh4dwq4M84h NA 10.33.68.135 57626 LoginUser-953366295 AggAAAAEok5eAAAAAAoAAACxYciKk0j4GT/6FAAAAFTHdgspBHtAMHLJ73Fp0AZWK4nWBwAAAFNIQS0yNTYgAAAATQ7VjyPvwEqy+mts/1AaJjD+mdYpGL7/KpXhArWqlzY= /v1/jupyter/hub/notebooks/new bi-service 8364 HttpServletResponseCode for /bi/v1/jupyter/hub/notebooks/new is in error: 500
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Thu February 13, 2020 09:22 AM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
You may have already done this, but from the Cognos homepage under manage -> configuration -> system -> environment, can you verify that the jupyter service location is set to http://azewsev000118:8000? This is the URL that the analytics server will attempt to reach when creating a new notebook. If this is properly set and you still get that endless spinner, we should take a look at the docker logs on your windows box. To get the logs, you would need to run the command "docker logs ca_jupyter_hub", where ca_jupyter_hub is the name of the docker container. Let me know what you find.
ps: You won't need to restart the analytics service after updating the jupyter service location in the manage panel
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Thu February 13, 2020 09:02 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
I did think of that and have tried: ws://AZEWSEV000118:8000 port 8000 is listening, The jupyter box is pingable from the analytics server. But the best I get is a spinning blue circle when I say new Notebook, and sadly nothing is the cogserver.log file give me any idea what it is doing. Right it has been spinning for 1 hour, and not even timed out. I have also restarted analytic services, and stopped and started the jupyter service.
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Thu February 13, 2020 07:59 AM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
Right, so if I understand your question correctly, the variable HOST_NAME within config.conf should not include the protocol by which the browser
communicates with your windows 10 jupyter server. It should just be the name of that box since the installation script will prepend the appropriate protocol (it will actually be WS/WSS instead of HTTP/HTTPS).
You won't be needing IIS or webserver on this box. The docker container ca_jupyter_hub is listening on port 8000 by default. Not sure if I've properly answered your question.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Thu February 13, 2020 06:02 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
That was part of the question, since Analytics 11.1.5 is not on the same box, this Win 10 box does not have IIS or websever set up on it, as the link in the environment settings needs to point to http:// is that more missing documentation?
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Wed February 12, 2020 11:27 AM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
That looks great!
You would just need to open dist/scripts/windows/config.conf and set the fully qualified name of your windows machine there.
This URL is going to tell the browser how to reach your jupyter server on windows 10 (needed for the python kernel connection).
Will look into updating our documentation - thank you for the feedback Kurt, it's much appreciated.
Regards,
Rob
------------------------------
ROBERT MCAULEY
Original Message:
Sent: Wed February 12, 2020 10:56 AM
From: Kurt Blevins
Subject: Jupyter Windows 10 Analytics 11.1.5
That might have been a big GOTCHA.... switched to Unix Containers, and almost works. Guessing the below as this is not where 11.1.5 is installed and
IIS or Liberty is not running on this machine.
Cheers,
Kurt
Successfully tagged ca_jupyter_viewer:2020-02-12_15-52-13
SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.
Starting CA Jupyter server
Starting CA Jupyter Docker containers
HOST_NAME is not set in config.conf. Aborting.
------------------------------
Kurt Blevins
Aegon UK
Original Message:
Sent: Wed February 12, 2020 10:25 AM
From: ROBERT MCAULEY
Subject: Jupyter Windows 10 Analytics 11.1.5
One thing that came to mind is that Docker Desktop is instructed to use Windows containers. The jupyter server
requires that docker use linux containers.
If you right click on the docker icon on the bottom right corner, there should be an option for switching to linux containers.
You can also re-install docker desktop, and just make sure not to check the option "use windows containers instead of linux containers".
Let me know if that helps (this gotcha definitely warrants a place in our documentation).
Regards,
Rob
------------------------------
ROBERT MCAULEY