Prev: SAS for Linux (Ubuntu)
Next: Windows client connecting to Linux server (SAS/Connect)
From: "S.A. Birl" on 7 Dec 2009 16:41
Hello All:

SAS 9.2
32-bit Linux on SuSE 9

Ive been working SAS Tech Support on this issue, but seem to be running
around in circles lately:

---
One of our users has previously used his Windows machine to connect to our
old Windows SAS server. Now that we're under Linux, this functionality is
broken.

Our local SAS expert told me: 1) User is trying SAS with rsubmittal over
XWin32 2) Expert believes that SAS/Connect is somehow involved, or should be.

Documentation given to me indicates that I need to use sastcpd on the Linux
server in order to get this setup. But Im new to administering SAS, so Im
not sure.

In any event, connection from Windows client to Linux server will mostly
likely need to be tunneled through SSH.
---


SAS Tech Support got me to a point where I can attempt to authenticate, but
authentication fails:

/usr/local/SAS/9.2/SASFoundation/9.2/sas -path
/usr/local/SAS/9.2/SASFoundation/9.2/utilities/src/auth -nodms

NOTE: SAS initialization used:
real time 0.82 seconds
cpu time 0.03 seconds

1? proc permtest;
2? run;
Authentication Test
Enter userid:
sbirl
Enter password:

ERROR: Access denied.Authentication failed.



Other times the error message I would receive from those same 2 commands:



ERROR: The authentication server is not SETUID ROOT. The installation is
incomplete.Authentication failed.



As instructed Ive chown root:root and chmod 4755
/usr/local/SAS/9.2/SASFoundation/9.2/utilities/bin/elssrv
/usr/local/SAS/9.2/SASFoundation/9.2/utilities/bin/sasauth
/usr/local/SAS/9.2/SASFoundation/9.2/utilities/bin/sasperm

and other tests have proven that SetUID is allowed on the filesystem.

Thanks.
Scott Birl
Temple University
 | 
Pages: 1
Prev: SAS for Linux (Ubuntu)
Next: Windows client connecting to Linux server (SAS/Connect)