docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Hi Chris,

Let's take a look at the Docker logs to see what went wrong with your kernel :-) 

This is what you'd need:

1) Start a new notebook in Cognos

2) On CentOS: docker ps -a (so you can find the name of your running notebook container - it should look like ca_jupyter-<some alpha-numeric string>)

3) On CentOS: docker logs <name of your running notebook container>

This will give you the logs of your currently running notebook. If there's a kernel error, my bet is there will be an error message there.

I tried reproducing your issue in my own environment, but I wasn't able to unfortunately. Would you be able to share the exact version of the jupyter notebook kit that you installed? I would like to take a closer look.

As for getting the version of your kernel, you can check the ipykernel package version using:

1) on CentOS: docker ps -a (to get the name of your notebook container once again - it should look like ca_jupyter-<some alpha-numeric string>)

2) on CentOS: docker exec -it <name of your container> bash

3) Within the docker container now: conda list | grep ipykernel

As for getting the list of your running kernels, unfortunately there isn't a command that allows you to do that as the kernels are managed internally by the notebook. 

Regards,
Rob

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Hi Chris,

Let's take a look at the Docker logs to see what went wrong with your kernel :-) 

This is what you'd need:

1) Start a new notebook in Cognos

2) On CentOS: docker ps -a (so you can find the name of your running notebook container - it should look like ca_jupyter-<some alpha-numeric string>)

3) On CentOS: docker logs <name of your running notebook container>

This will give you the logs of your currently running notebook. If there's a kernel error, my bet is there will be an error message there.

I tried reproducing your issue in my own environment, but I wasn't able to unfortunately. Would you be able to share the exact version of the jupyter notebook kit that you installed? I would like to take a closer look.

As for getting the version of your kernel, you can check the ipykernel package version using:

1) on CentOS: docker ps -a (to get the name of your notebook container once again - it should look like ca_jupyter-<some alpha-numeric string>)

2) on CentOS: docker exec -it <name of your container> bash

3) Within the docker container now: conda list | grep ipykernel

As for getting the list of your running kernels, unfortunately there isn't a command that allows you to do that as the kernels are managed internally by the notebook. 

Regards,
Rob

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Hi Chris,

Let's take a look at the Docker logs to see what went wrong with your kernel :-) 

This is what you'd need:

1) Start a new notebook in Cognos

2) On CentOS: docker ps -a (so you can find the name of your running notebook container - it should look like ca_jupyter-<some alpha-numeric string>)

3) On CentOS: docker logs <name of your running notebook container>

This will give you the logs of your currently running notebook. If there's a kernel error, my bet is there will be an error message there.

I tried reproducing your issue in my own environment, but I wasn't able to unfortunately. Would you be able to share the exact version of the jupyter notebook kit that you installed? I would like to take a closer look.

As for getting the version of your kernel, you can check the ipykernel package version using:

1) on CentOS: docker ps -a (to get the name of your notebook container once again - it should look like ca_jupyter-<some alpha-numeric string>)

2) on CentOS: docker exec -it <name of your container> bash

3) Within the docker container now: conda list | grep ipykernel

As for getting the list of your running kernels, unfortunately there isn't a command that allows you to do that as the kernels are managed internally by the notebook. 

Regards,
Rob

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Hi Chris,

Let's take a look at the Docker logs to see what went wrong with your kernel :-) 

This is what you'd need:

1) Start a new notebook in Cognos

2) On CentOS: docker ps -a (so you can find the name of your running notebook container - it should look like ca_jupyter-<some alpha-numeric string>)

3) On CentOS: docker logs <name of your running notebook container>

This will give you the logs of your currently running notebook. If there's a kernel error, my bet is there will be an error message there.

I tried reproducing your issue in my own environment, but I wasn't able to unfortunately. Would you be able to share the exact version of the jupyter notebook kit that you installed? I would like to take a closer look.

As for getting the version of your kernel, you can check the ipykernel package version using:

1) on CentOS: docker ps -a (to get the name of your notebook container once again - it should look like ca_jupyter-<some alpha-numeric string>)

2) on CentOS: docker exec -it <name of your container> bash

3) Within the docker container now: conda list | grep ipykernel

As for getting the list of your running kernels, unfortunately there isn't a command that allows you to do that as the kernels are managed internally by the notebook. 

Regards,
Rob

Kind Regards,

docker inspect <ID> | grep IP

docker inspect <ID> | grep HOST

docker inspect <ID> | grep Port

All gives me the expected information of my environment, so I don't think this is the issue.

When I look into the kernel.json:
kernel.json:
{
"argv": [
"/opt/anaconda3/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3",
"language": "python"

But my /opt:

drwx--x--x. 4 root root 28 Dec 29 04:24 containerd
drwxrwxr-x. 3 root root 20 Dec 29 04:33 ibm
drwxr-xr-x. 2 root root 6 Oct 30 2018 rh

Any hints how and what I can test with the Python-3 is weolcome.

Kind Regards,

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello Robert,

Thank you for your help. We found a similar suggestion.
Our Gateway URI parameter: http://my-cognos:80/ibmcognos/bi/v1/disp. So, we tried to access Cognos using http://my-cognos:80/ibmcognos/bi/.

It seems to get further. In the Notebook the kernel doesn't gives immediately an error, but stucks on connecting to kernel. After a couple of minutes, it gives a timeout error. In the docker logs there is no Cross Origin message.

When the timeout occurs in the console log of the browser, we see WebSocket connection to: 'ws:my-cognos/ibmcognos/bi/v1/Jupiter/user/….'failed. Error during WebSocket handshake. Unexpected response code: 502.

The response code varies. It can be 400 and 502.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello Robert,

Thank you for your help. We found a similar suggestion.
Our Gateway URI parameter: http://my-cognos:80/ibmcognos/bi/v1/disp. So, we tried to access Cognos using http://my-cognos:80/ibmcognos/bi/.

It seems to get further. In the Notebook the kernel doesn't gives immediately an error, but stucks on connecting to kernel. After a couple of minutes, it gives a timeout error. In the docker logs there is no Cross Origin message.

When the timeout occurs in the console log of the browser, we see WebSocket connection to: 'ws:my-cognos/ibmcognos/bi/v1/Jupiter/user/….'failed. Error during WebSocket handshake. Unexpected response code: 502.

The response code varies. It can be 400 and 502.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello Robert,

Thank you for your help. We found a similar suggestion.
Our Gateway URI parameter: http://my-cognos:80/ibmcognos/bi/v1/disp. So, we tried to access Cognos using http://my-cognos:80/ibmcognos/bi/.

It seems to get further. In the Notebook the kernel doesn't gives immediately an error, but stucks on connecting to kernel. After a couple of minutes, it gives a timeout error. In the docker logs there is no Cross Origin message.

When the timeout occurs in the console log of the browser, we see WebSocket connection to: 'ws:my-cognos/ibmcognos/bi/v1/Jupiter/user/….'failed. Error during WebSocket handshake. Unexpected response code: 502.

The response code varies. It can be 400 and 502.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs

Hello,

We ran into the same problem on our environment. I found this thread by googling for "Cognos Jupiter Blocking Cross Origin API request". We also use the 11.1.5 version.

Right now, Firefox gives the same error. So, switching from Chrome to Firefox is not a solution anymore.

We tried a lot of combinations using IP address and fully qualified domain names in the configuration, but we always get this error. We also modified the hosts files on the servers and included the other machine.

Our Jupyter Server is running on CentOS 7.8, and the Cognos Server is running on Windows 2012.

Does anyone have any suggestion? It seems to be a network and browser related error, but I have no idea how to fix this error.

Regards,

Balazs