Starting and stopping LSF in SAS

1) Login as root on all your host machine (Note: if your environment has configured to use lsf account id then use that)
2) Ensure LSF state is clean.
# /etc/rc3.d/S99lsf stop
Stopping the LSF subsystem
# sleep 20
# /etc/rc3.d/S99lsf status
Show status of the LSF subsystem
lim is stopped...
res is stopped...
sbatchd is stopped...

3) Start LSF on each node . Check status after 70 seconds before moving to next node.

# /etc/rc3.d/S99lsf start
# sleep 70
# /etc/rc3.d/S99lsf status

4) Check if bhosts shows atleast 2 nodes 'ok' and ProcessManager in EGO using commands

Login using your id on the host that has process manager and run following commands to verify whether the lsf is up:
. /lsf/conf/profile.lsf
lsid
bhosts
egosh service list

Comments

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps. Open SMC -> Expand Servers -> Expand In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT. So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log. Any suggestions? Answer: Please do the following: 1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop 2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`: if [ -n ""$TKPATH"" ]; then unset TKPATH fi if [ -n ""$TK_PATHLIST"" ]; then unset TK_PATHLIST fi 3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start The above code change in ObjectSpawner.sh should fix the issue.

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login 14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...

SAS Platform Admin Blog

Search This Blog