Permissions Issue on LASR Server

[KirSinc]

Hi,

We're experiencing unexpected errors that were not present yesterday when trying to run a LOGISTIC statement on a table sitting on the LASR server.

Here is the code:

options set=SAS_HADOOP_JAR_PATH='/opt/sas/hadoop_jars';

options set=SAS_HADOOP_CONFIG_PATH='/opt/sas/hadoop_xml_files';

options set=GRIDHOST='YULEDASASAMGTA001.atledadc1.eda.equifax.com';

options set=GRIDINSTALLLOC='/opt/TKGrid_REP';

options set=GRIDRSHCOMMAND="/usr/bin/ssh -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o PubkeyAuthentication=no ";

%let port=10013;

libname lasr sasiola tag='ERSDB' port=&port. verbose=yes;

proc imstat ;

  table lasr.dev_sample_final;

  logistic target= &column. / link=logit;

  run;

quit;

This Error:

824       

 825          table lasr.dev_sample_final;

826          logistic target= awsc011010 / link=logit;

827          run;

 ERROR: You have insufficient permission to perform the requested operation on table ERSDB.DEV_SAMPLE_FINAL.

828    

But, we loaded the table and there is only one person using this server & port.

[DougWielenga]

I'm not sure if this helps or not, but we have seen this insufficient permission problem with IMSTAT when the GRIDRSHCOMMAND variable is used without using -q to suppress ssh output, such as ssh banners.  LASR interprets the output as data it is looking for to determine permissions, and throws the permission error when it doesn't adhere to what is expected. 

Are you using GRIDRSHCOMMAND to specify an external ssh such as /usr/bin/ssh or a 3rd party ssh such as Centrify?  If so, ensure the command includes -q such as the following example:

  option set=GRIDRSHCOMMAND='/usr/bin/ssh -q'; 

Hope this helps!

Doug

[KirSinc]

Hi Doug,

Thanks for the recommendation. We'll test that out and let you know how it goes.

Cheers!

Kirby