WCC: Command in ECLI receives: 17986 Segmentation fault (core dumped) | $ASCmdWrpExe
search cancel

WCC: Command in ECLI receives: 17986 Segmentation fault (core dumped) | $ASCmdWrpExe


Article ID: 116609


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent


Commands in WCC ECLI were failing for all users.
Executing autorep -M ALL in WCC ECLI receives:
/opt/CA/SharedComponents/iTechnology/AutoSysCommandWrapper.sh: line 158: 17985 Done echo "$user 
17986 Segmentation fault (core dumped) | $ASCmdWrpExe


AE: 11.3.6 SP0 (new build of environment, ECLI had never worked)
RedHat Linux 7



The WCC credentialed password needed to be updated.  


Provided an updated AutosyscommandSponsor.exe that comes with AE: 11.3.6 SP7. This gave more detail on the problem with debug on;
TRACE: [0x792e8b40] ThreadedCommand:: Begin - run() 
TRACE: [0x792e8b40] Current Working Directory: [/opt/CA/SharedComponents/iTechnology] 
TRACE: [0x792e8b40] Executing command: [/opt/CA/SharedComponents/iTechnology/AutoSysCommandWrapper.sh] 
TRACE: [0x792e8b40] Send message: [dca1367 
autorep -J ALL -saml "UserSession;Version-1.0;8ed2c5227fda0a35f8a00d9f83a0e27-5b7ae8ad-793a3bf8-45d6" 

TRACE: [0x792e8b40] ThreadedCommand:: End - run() 
TRACE: [0x576beb40] ThreadedCommand:: End - exec() 
TRACE: [0x576beb40] AutoSysCommandISponsor:: Begin - checkForError() 
TRACE: [0x576beb40] CheckForError Data: [COMMAND WRAPPER ERROR CODE: -1 
COMMAND WRAPPER ERROR MESSAGE: Failed to log on using the given credentials. 

ERROR: [0x576beb40] Exception while executing command: [Failed to log on using the given credentials.] <<<<<<<<<<<<<<<<<<<<<<
TRACE: [0x576beb40] AutoSysCommandISponsor:: Return - checkForError() 
The password for the user needed to be updated on the Credentialed Tab, the username was correct. 
Once completed, commands thru ECLI were successful.


Additional Information

Setting debug:

Per doc: https://docops.ca.com/ca-workload-automation-ae/11-4-2/en/release-notes/ca-wcc-release-notes/command-sponsor#CommandSponsor-Logs

Application Logs

If you encounter issues with the CA WCC application itself (when using Enterprise Command Line or Forecast) and Command Sponsor is installed on UNIX, it is possible to debug. Follow these steps:

  1. Add <DebugLevel>ISP_FILE</DebugLevel> under the in <ISponsor> element in the file $IGW_LOC/AutoSysCommandISponsor.conf.
  2. Start iGateway in debug mode: $IGW_LOC/S99igateway debug.
  3. Check the console output.
  4. To leave the debug mode, type Ctrl+C.
  5. Be sure to restart iGateway in background mode: $IGW_LOC/S99igateway start.