Overriding the -logconfigloc parameter for the metadata configured SAS/CONNECT® Spawner does not work


To override the setting of the -logconfigloc startup parameter for a metadata configured CONNECT Spawner in SAS 9.4, you should be able to edit the ./ConnectSpawner_usermods.sh file and set -logconfigloc to the following new value: 

USERMODS_OPTIONS=(-shell -logconfigloc /..../Lev?/ConnectSpawner/logconfig.trace.xml)

However, this override does not work because the ./ConnectSpawner.sh sets the default -logconfigloc after the $USERMODS_OPTIONS in the CONNECT Spawner's launch command. See the highlighted change. 

For example:

CMD_OPTIONS=" -sspi  $USERMODS_OPTIONS"
....

nohup $CNCTCMD $CMD_OPTIONS ..... -logconfigloc $CONFIGDIR/logconfig.xml -sasspawnercn "$SPWNNAME" > $LOGSDIR/connectspawner_hostname_console.log 2>&1 &

Workarounds

You can use either of these workarounds:

Workaround 1:

  1. Backup ./ConnectSpawner.sh (.bat for Microsoft Windows).
  2. Edit it to change the value of the -logconfigloc parameter in two locations.

Workaround 2:

  1. Backup ./ConnectSpawner.sh.
  2. Edit it by changing the placement of the -logconfigloc option in the two launch commands. Make your overrides in the ./ConnectSpawner_usermods.sh (or .bat for Windows).

For example:

nohup $CNCTCMD ..... -logconfigloc $CONFIGDIR/logconfig.xml $CMD_OPTIONS -sasspawnercn "$SPWNNAME" > $LOGSDIR/connectspawner_hostname_console.log 2>&1 &

nohup $CNCTCMD ... -service $CONNPORT -logconfigloc $CONFIGDIR/logconfig.xml $CMD_OPTIONS -mgmtPort "$MGMTPORT" -sascmd $SASCMD > $LOGSDIR/connectspawner_hostname_console.log 2>&1 &