Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only

  • 1.  Cognos Jupyter server kernel error

    Posted Fri June 05, 2020 12:33 PM
    Hello,
    We have installed Cognos Analytics 11.1.6 and Congnos Jupyter Server in the same severs but we are facing one issue
    When we try to create a new notebook from outside the server we are getting and Kernel Error with this error in the chrome console.

    When we try to create a new notebook from inside the server we are getting a different error, I am not getting the kernel error but chrome console is showing this.

    Docker containers are up and running.
    Please can you advise?

    The server specification are
    Azure Standard D8 v3 (8 vcpus, 32 GiB memory)Windows 10 Enterprise 2019 LTSC• 8 vcpus, 32 GiB memory• Processor: AMD EPYC 7452 32-Core Processor 2.35 GHz• Disk1 (OS): 127GiB• Disk2: 1024 GiB
    Ports: 80 and 8000 are opened


    Thanks

    ------------------------------
    Pablo Patruno
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Cognos Jupyter server kernel error

    Posted Fri June 19, 2020 08:52 AM

    Hi Pablo!

    In my experience Kernal errors happen due to a configuration issue. Usually either you are referencing using inconsistent names (sometimes using fqdn, sometimes just hostname and sometimes even IP addr)...

    First thing is first. Do you have any SSL anywhere? If so, Jupyter needs to be SSL enabled also. https://www.ibm.com/support/pages/how-secure-jupyter-cognos-analytics-1112-3rd-party-certificates ... if you don't have SSL on the GW or Dispatcher, then don't worry. 

    • Do you have a gateway involved? If so lets start by ruling that out! 
    • Change your Gateway URI to match the Dispatcher URI for External Applications: 
    • http://cognosservername:9300/bi/v1/disp
    • Save, restart and retest (access cognos via this URL when retesting: http://cognosservername:9300/bi/v1/disp)
    If this resolves the issue, I would look deeper into your webserver.  


    If you still have a problem, you know (atleast one issue) is present outside of your webserver/gateway config). 

    Then its time to start looking at your references & connectivity.

    You need to make sure the Cognos Server can TELNET to the HOST_NAME and PORT referenced in the Jupyter config.conf file. (IMPORTANT: Not whatever the hostname is for the docker server,  but the exact reference you had explicitly made in the Jupyter config.conf)

    Then, make sure you can get back to cognos from the Jupyter host container. You will need to TELNET from within the container to whatever you have explicitly placed in the Cognos Configuration -  Dispatcher URI for External Applications (IMPORTANT: Not whatever you call the cognos server with usually,  but the exact reference you had explicitly made Dispatcher URI for External Applications ... ie if its FQDN, use FQDN, it it is IP, use IP)...
    Here are the commands to bash in and telnet out: 

    • 1. docker exec -it -u 0 ca_jupyter_hub bash
    • 2. apt-get install iputils-ping
    • 3. Ping IP

    You can also have a gander at this blog on troubleshooting these kinds of errors:  
    https://community.ibm.com/community/user/businessanalytics/blogs/matt-morgan1/2020/06/08/ca-jupyter-troubleshooting-process

    If you have any questions comments or concerns, let me know!


    Matt
    Cognos Technical Analyst

    ------------------------------
    MATT MORGAN
    ------------------------------

    Original Message


  • 3.  RE: Cognos Jupyter server kernel error

    Posted Fri June 19, 2020 03:33 PM
    Hi Pablo,

    A few thoughts:

    I've noticed that Jupyter is very sensitive to the URL you use when accessing Cognos Analytics.

    If you've configured the Gateway URI on your CA server as something like http://10.1.1.5/ibmcognos/bi/v1/disp then for you to successfully access Jupyter your browser URL must match -- in other words you must use http://10.1.1.5/ibmcognos when logging in.  You can't use a URL that uses a server name instead like http://my-cognos-server/ibmcognos  even if my-cognos-server is the same as 10.1.1.5... Jupyter won't connect properly with the server name URL.

    Are you using a Gateway?  If so, there is some specific Jupyter setup you must do (without which you won't be able to access Jupyter via CA).

    Have you tried and verified that your Cognos server can talk to your Jupyter server via the same URL you entered into the Cognos Configuration?  Remote to your CA server, open a browser, and enter that address  (ex:  http://my-jpyter-server:8000).  Do you get a response of "Jupyter has many moons..."?  If so, then you know that your CA server can actually talk to your Jupyter server... if not, then you'll want to correct whatever network settings are preventing that communication.

    ​Finally, looking at the Docker log for your Jupyter process could give you a bit of insight as to what might be going wrong.   The docker logs command has become my go-to for troubleshooting issues like this one.

    Good luck!

    Rich

    ------------------------------
    Richard Chester
    Director of Business Intelligence
    LPA Software Solutions
    ------------------------------

    Original Message


Related Content