topic Re: saspy not connecting in jupyter in Administration and Deployment

saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 06:02:54 GMT

I have saspy (3.6.5) installed in JupyterLabs connecting to a remote instance of SAS via SSH.

Now the weird thing is that when I start python from the command line, it connects and establishes a session with my SAS instance, however when I try from a jupyter notebook it won't connect.

When I copy the ssh command that is presented in the Jupyter output it connects, but when I try to run it in a cell, it just hangs until I terminate it.

Anyone have any ideas?

Other potentially relevant information:

JupyterLab v 2.1.3

Python 3.7.6

SAS 9.4 M6 running under Centos 7

JupyterLab running in a docker container under Ubuntu 18.04.4 LTS

thanks in advance.

Re: saspy not connecting in jupyter

gwootton — Fri, 19 Feb 2021 14:17:51 GMT

I was able to get around this by setting up passwordless ssh between my container and the remote host:
In container, run ssh-keygen
Copy contents of .ssh/id_rsa.pub in container and add them to .ssh/authorized_keys on remote host.
In your host statement, specify the connecting user (i.e. sasdemo@compute.demo.sas.com)

Re: saspy not connecting in jupyter

sastpw — Fri, 19 Feb 2021 14:48:37 GMT

Hey, my first thought on this is that wherever Jupyter is running, or what id it's running as, isn't the same as where this works when you run from a command line. Passwordless ssh isn't set up the same where Jupyter is running, as in your command line example. I do see you said the following:

JupyterLab running in a docker container under Ubuntu 18.04.4 LTS

So, that makes me think this is the issue. Can you verify that from the command line, inside that container, as the user that the jupyter process is running as, can ssh to the remote machine using that command line which works form your terminal?

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 16:19:41 GMT

The command line is inside the docker container, running as the same user as jupyter.

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 16:22:00 GMT

I have passwordless ssh set up between the container and the vm, and it does connect.

Re: saspy not connecting in jupyter

sastpw — Fri, 19 Feb 2021 16:29:36 GMT

And there's no prompting, like for the machine to be added to the known_hosts file or anything?

Can you run python in the container, same as jupyter, but from the command line and try to connect w/ saspy? If you can ssh, w/out prompting for anything, then saspy should work, if you're configuration is the same.

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 16:32:26 GMT

No prompting. The screen shot of the command line connection in the OP is from the cli inside the container.

That's what has me stumped. It works from python at the cli but not from the notebook.

Re: saspy not connecting in jupyter

sastpw — Fri, 19 Feb 2021 16:41:09 GMT

ok. Using the same user that jupyter is running? And what about current directory, is there something that could be picked up out of your current dir, running from the command line when it works, that maybe isn't there in the jupyter case? Are you using python environments, and maybe you're not using the same one in both cases?

What's different? It sounds like you're saying your running from the same machine, as the same user, w/ the same python environment with the same pw/less ssh setup, and it works one way but not the other. So, something is different between the two environments. But I can't look, so I'm just kinda guessing.

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 16:48:37 GMT

I appreciate your help.

Same environment, same user, not using virtual environments (unless python is using one without me knowing).

The notebook is connecting to the SAS compute instance, as when I hit the stop button I'm forced to terminate the sas session, it's just not getting the process id like the cli version.

Re: saspy not connecting in jupyter

sastpw — Fri, 19 Feb 2021 16:56:12 GMT

ok, gotcha. Still, somethings different. If you'd like, I can set up a teams meeting with you this afternoon, If you can share your screen, maybe I can see something that's causing the difference, or we can debug it some and see what we turns up.

Tom

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 18:40:06 GMT

Thanks for the offer.

Would you have time on Tuesday for the teams call (i'm on pacific time), I'm tied up the rest of the day and on Monday.

Re: saspy not connecting in jupyter

sastpw — Fri, 19 Feb 2021 18:46:22 GMT

Sure, no problem. Send me an email, tom.weber@sas.com, and I'll set up a meeting invite. I'm EST, so let me know what time works for you and I'll set it up.

Thanks,

Tom

Re: saspy not connecting in jupyter

pwsegal — Fri, 19 Feb 2021 21:45:53 GMT

Solved.

Turns out that in my docker image (that I did not build), jupyter was running as a different user.

Once I copied the public keys over to the correct directory, it all works now.

Thanks to all those who chimed in to help.

Re: saspy not connecting in jupyter lab

pkm_edu — Thu, 25 Aug 2022 20:56:56 GMT

import saspy
import pandas as pd
sas = saspy.SASsession(cfgname='winlocal')
w_class = sas.sasdata("CLASS","SASHELP")
w_class.describe()

We failed in getConnection
The application could not log on to the server "localhost:0". Integrated Windows authentication failed.
SAS process has terminated unexpectedly. RC from wait was: 4294967290
SAS Connection failed. No connection established. Double check your settings in sascfg_personal.py file.

Attempted to run program C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe with the following parameters:['C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe', '-classpath', 'C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.svc.connection.jar;C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\log4j.jar;C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.security.sspi.jar;C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.core.jar;C:\\Users\\Pradip.Muhuri\\Anaconda3\\Lib\\site-packages\\saspy\\java\\saspyiom.jar', 'pyiom.saspy2j', '-host', 'localhost', '-stdinport', '52557', '-stdoutport', '52558', '-stderrport', '52559', '-zero', '-lrecl', '1048576', '']

Be sure the path to sspiauth.dll is in your System PATH

No SAS process attached. SAS process has terminated unexpectedly.
Invalid response from SAS on inital submission. printing the SASLOG as diagnostic

Issue: Our IT staff has added the path to sspiauth.dll in the System PATH. I don't know why I am getting the above error in this laptop, although saspy and SAS in Juputer Lab work fine in my other laptop.

Any help toward resolving the issue would be appreciated. Thanks,

Below is some background information.

 %put &sysvlong;
9.04.01M6P110718
 %put &sysscpl;
X64_10PRO

C:\Program Files\SASHome\SASDeploymentManager\9.4\products\privatejre__99572__wx6__xx__sp0__1\bin\java.exe
C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe


Name: saspy Version: 4.3.2
Name: SAS-kernel Version: 2.4.10
Python 3.9.12

#Content of sascfg_personal.py
SAS_config_names=['winlocal']
SAS_config_options = {'lock_down': False,
                      'verbose'  : True
                     }
SAS_output_options = {'output' : 'html5'}
# Configuration Definitions
default  = {'saspath'  : '/opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_u8'
            }
ssh      = {'saspath' : '/opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_en',
            'ssh'     : '/usr/bin/ssh',
            'host'    : 'remote.linux.host', 
             'encoding': 'latin1',
            'options' : ["-fullstimer"]
            }
# build out a local classpath variable to use below for Windows clients   CHANGE THE PATHS TO BE CORRECT FOR YOUR INSTALLATION 
cpW  =  "C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.svc.connection.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\log4j.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.security.sspi.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.core.jar"
cpW += ";C:\\Users\\Pradip.Muhuri\\Anaconda3\\Lib\\site-packages\\saspy\\java\\saspyiom.jar"

winlocal = {'java'      : 'C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe',
            'encoding'  : 'windows-1252',
            'classpath' : cpW
            }
winiomlinux = {'java'   : 'java',
            'iomhost'   : 'linux.iom.host',
            'iomport'   : 8591,
            'encoding'  : 'latin1',
            'classpath' : cpW
            }

winiomwin  = {'java'    : 'java',
            'iomhost'   : 'windows.iom.host',
            'iomport'   : 8591,
            'encoding'  : 'windows-1252',
            'classpath' : cpW
            }

winiomIWA  = {'java'    : 'java',
            'iomhost'   : 'windows.iom.host',
            'iomport'   : 8591,
            'encoding'  : 'windows-1252',
            'classpath' : cpW,
            'sspi'      : True
            }

Re: saspy not connecting in jupyter lab

gwootton — Fri, 26 Aug 2022 14:18:20 GMT

This topic is solved, so you may want to create a new topic. This SAS Note discusses a similar error (The application could not log on to the server "localhost:0". Integrated Windows authentication failed.) in Enterprise Miner.

Problem Note 55227: SAS® Enterprise Miner(tm) Workstation displays the error "The application could not log on to the server "localhost:0" when you create a project
https://support.sas.com/kb/55/227.html

Re: saspy not connecting in jupyter lab

sastpw — Fri, 26 Aug 2022 15:46:10 GMT

Yes, you should create a new post for your issue here rather than add to an old solved one that isn't really related to your issue.

But, take a look at #6 here: https://sassoftware.github.io/saspy/troubleshooting.html#iom-specific-errors

That's likely to be the problem and solution!

Re: saspy not connecting in jupyter lab

sastpw — Fri, 26 Aug 2022 15:48:46 GMT

Also, FWIW, I see you're providing your own classpath in your config file. You shouldn't be doing that, as it could cause problems if it's not all exactly right. See the doc here: https://sassoftware.github.io/saspy/configuration.html#attn-as-of-saspy-version-3-3-3-the-classpath-is-no-longer-required-in-your-configuration-file

Thanks,

Tom

Re: saspy not connecting in jupyter lab

pkm_edu — Fri, 26 Aug 2022 18:30:30 GMT

Hello,

Sorry for not asking the question in a new post.

1) Could you please send me the link where I should post for this particular topic?
2) Do I need any revisions to my sascfg_personal.py below?
3) Any further thoughts?

Thanks,

Pradip

****************************************************
# Here is the content of my sascfg_personal.py
SAS_config_names=['winlocal']

SAS_config_options = {'lock_down': False,
'verbose' : True
}

SAS_output_options = {'output' : 'html5'}

# Configuration Definitions

default = {'saspath' : '/opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_u8'
}

ssh = {'saspath' : '/opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_en',
'ssh' : '/usr/bin/ssh',
'host' : 'remote.linux.host',
'encoding': 'latin1',
'options' : ["-fullstimer"]
}

# build out a local classpath variable to use below for Windows clients CHANGE THE PATHS TO BE CORRECT FOR YOUR INSTALLATION
cpW = "C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.svc.connection.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\log4j.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.security.sspi.jar"
cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94518__prt__xx__sp0__1\\deploywiz\\sas.core.jar"
cpW += ";C:\\Users\\Pradip.Muhuri\\Anaconda3\\Lib\\site-packages\\saspy\\java\\saspyiom.jar"

winlocal = {'java' : 'C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe',
'encoding' : 'windows-1252',
'classpath' : cpW
}

winiomlinux = {'java' : 'java',
'iomhost' : 'linux.iom.host',
'iomport' : 8591,
'encoding' : 'latin1',
'classpath' : cpW
}

winiomwin = {'java' : 'java',
'iomhost' : 'windows.iom.host',
'iomport' : 8591,
'encoding' : 'windows-1252',
'classpath' : cpW
}

winiomIWA = {'java' : 'java',
'iomhost' : 'windows.iom.host',
'iomport' : 8591,
'encoding' : 'windows-1252',
'classpath' : cpW,
'sspi' : True
}

Re: saspy not connecting in jupyter lab

sastpw — Fri, 26 Aug 2022 18:59:11 GMT

No problem, it's just that adding to some old post wont get visibility and is confusing. I think you just click 'Start New Topic' to create one of these posts. There's not a SASPy category here, I think they want that to go into the Programming->Developers area, but it really doesn't matter. FWIW, you can get direct help on SASPy by opening an issue on the SASPy github site. But since I'm here 🙂

Since you only seem to be using local SAS on your PC, the only required content of your sascfg_personal.py file would be:

```

SAS_config_names=['winlocal']

winlocal = {'java' : 'C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe',
'encoding' : 'windows-1252',
}

```

Did you resolve your etc/hosts file, assuming the problem was #6 in the troubleshooting guide for IOM specific errors?

Re: saspy not connecting in jupyter lab

pkm_edu — Fri, 26 Aug 2022 23:29:30 GMT

Hi Tom,

Thanks for your continued support.

I have further revised the content of my sascfg_personal.py as shown below. It is still throwing errors as before.
Any help would be appreciated.

********************** Error *****************************************88
We failed in getConnection
The application could not log on to the server "localhost:0". Integrated Windows authentication failed.
SAS process has terminated unexpectedly. RC from wait was: 4294967290
SAS Connection failed. No connection established. Double check your settings in sascfg_personal.py file.
************************************************************************************************

# sascfg_personal.py

# https://sassoftware.github.io/saspy/configuration.html#attn-as-of-saspy-version-3-3-3-the-classpath-is-no-longer-required-in-your-configuration-file

# I have added C:\\Program Files\\SASHome\\SASFoundation\\9.4\\core\\sasexte to my system PATH as well.
# Are the following two lines of Python code redundant here?

import os
os.environ["PATH"] += ";C:\\Program Files\\SASHome\\SASFoundation\\9.4\\core\\sasext"

# There are three main parts to this configuration file as stated in the abobe link.

# Part 1. SAS_config_names

SAS_config_names=['winlocal']

# Part 2. SAS_config_options are required unless you want to change a default. No such options added to this file.

# Part 3 Configuration definitions
default = {'saspath' : '/opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_u8'
}

winlocal = {'java' : 'C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe',
'encoding' : 'windows-1252'
}

# Is the following code chunk part of Part 3 and required here? If yes, does this code snippet require revision?

winiomwin = {'java' : 'java',
'iomhost' : 'windows.iom.host',
'iomport' : 8591,
'encoding' : 'windows-1252'
}