AutoSys Workload Automation

Hi folks,  Anybody seen this before?  Even though the job went success, I get an "<Aborted, Signal 6>" for all users except autosys.

  437 LINUX ANY 11.3.6 SP1

<font "courier="" new"="">

Job Name                                                         Last Start           Last End             ST Run/Ntry Pri/Xit________________________________________________________________ ____________________ ____________________ __ ________ _______asys_c_test                                       08/03/2017 08:55:06  08/03/2017 08:55:06  TE 680013/1 6        Status/[Event]  Time                 Ntry ES  ProcessTime           Machine  --------------  --------------------- --  --  --------------------- ----------------------------------------  STARTING        08/03/2017 08:55:06    1  PD  08/03/2017 08:53:32   testmachine  RUNNING         08/03/2017 08:55:06    1  PD  08/03/2017 08:53:33   testmachine    <Executing at WA_AGENT>  SUCCESS         08/03/2017 08:55:06    1  PD  08/03/2017 08:53:33   testmachine  TERMINATED      08/03/2017 08:55:06    1  PD  08/03/2017 08:53:33       <Aborted, Signal 6>

Looks like someone signaled a 6 but the code gracefully shuts down.

What’s the command? Talk to the app  owner.

Steve C.

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

command: env > /tmp/env-envadm.out

Ok that is poor design.

command: env

std_out_file: /path/filename

std_err_file: /path/filename

Steve C.

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

yep, agreed,  I've tried that too.  No mater what command I execute, success or failure, I get the real status,  then the second status, terminated, aborted signal 6.  Not sure were the second signal is coming from,  and only happens if not using autosys as owner

Try

command: /bin/true

also look at autosyslog -J job -t A or S for spool

either its an issue with agent or you have authorization software not playing nice.. like eiam or something..

Steve C.

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

Is user 'autosys' local and others ex: envadm, coming from LDAP or AD, and you use LikeWise or other software to authenticate these external users? Please check the /var/log/messages log from around the time the job terminates. It appears the auth software is intercepting the agent process (cybspawn) with a signal 6. I'd use strace on Linux to latch on to the cybspawn process id for the corresponding job and see where the signal 6 is coming from. 

1. Start a 'sleep 100' job as envadm user.

2. Once the job goes to running, get the cybspawn process id (ps -fu envadm|grep [c]yb) for the job.

3. Execute, `strace -a -p <pid of cybspawn> -o /tmp/cyb.txt`

4. When the job finishes and terminates, the strace will exit too. Forward the /tmp/cyb.txt log to us for review.

Thanks,

Chandru

Will give this a try and report back.  Thanks

Hi Chandru,  You were correct.  Added the ID's to ignore-user file and corrected the issue.  Thanks