Skip to main content

Process Manager 9.1 jobs are in Waiting state

Issue:

We have several jobs on waiting status in IBM Platform Process Manager 9.1.

Solution:

IBM support team suggested us to add the parameter below to avoid creating new login shell for the submission users for each job triggered from PPM side:

JS_SU_NEW_LOGIN=false

You can find this configuration in js.conf file located at /pm/conf.

bash-4.1$ grep JS_SU_NEW_LOGIN js.conf
JS_SU_NEW_LOGIN=false
# Default is JS_SU_NEW_LOGIN=true

Side effects:

There is one downside of using this parameter, that it will not get user's $HOME/.profile sourced so any environment variables set there will not be seen in job execution environment. PPM submission to LSF is by default using "su - username -c 'command' " and the dash here implies user login is invoked souring the $HOME/.profile file. When we added JS_SU_NEW_LOGIN=false to our Test environment, it broke some jobs for user that depended on variables defined in user $HOME/.profile. We resolved it by sourcing those variables in application scripts.

Other symptoms for this issue:

PPM try to send the job to LSF but exits with code 125.
This code is related to when "su " command fails because of a shell issue.

Other solutions tried but failed:

Moving the flow instance from active to finished:
$ cd /pm/work/storage/flow_instance_storage/active/
$ ls -l 387532.dat
rw-r--r--. 1 sas sas 6354 Feb 16 00:00 387532.dat
$mv 387532.dat ../finished/

Comments

Post a Comment

Popular posts from this blog

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...
2 comments
Read more

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.
1 comment
Read more

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...
3 comments
Read more