Page 1 of 1

FAILED TO EXECUTE DUE TO USER ENVIRONMENT

Posted: 20 Sep 2010 3:38
by fileal2
Hi,

I'm receiving an error regarding job submission on a CTM 6.3.01 Agent on Linux.. here is the sysout of the failed jobs:

20100917 132349 Failed to submit job.
20100917 132349 Found empty sysout file.
20100917 132349 Possible cause of problem:
1. Job submission aborted due to error in executing '/bin/su'.
2. Job submission aborted due to error in Autoedit variables.
login. STDOUT -->>
login. STDERR -->>
/softs/ControlM/ctm/ctm_agent/ctm/sysout/CMD.LOG_0056dv_00002: Permission denie\ d.


and the jobs logs show this:


17/09/10 13:23:48 SL5105 SUBMITTED TO suora120
17/09/10 13:24:19 TR5101 STARTED AT 20100917132348 ON suora120
17/09/10 13:24:19 TR5120 JOB STATE CHANGED TO Executing
17/09/10 13:24:49 TR5100 ENDED AT 20100917132449. OSCOMPSTAT -2. RUNCNT 2
17/09/10 13:24:49 TR5112 JOB FAILED TO EXECUTE DUE TO USER ENVIRONMENT
17/09/10 13:24:49 TR5134 ENDED NOTOK
17/09/10 13:24:49 TR5120 JOB STATE CHANGED TO Analyzed
17/09/10 13:24:49 SL5120 JOB STATE CHANGED TO Post processed

Also, these are jobs that were beeing submitted successfully and the system administrator is telling me that nothin has been changed.

Anyone care to help?!?!?

Thx in advance..

Posted: 20 Sep 2010 6:56
by Banshee06
I would run the job manually on the server and see if it will run.

Posted: 20 Sep 2010 9:51
by fileal2
Yes it runs..

And also if I do as root...
su -user -c script

...it runs fine.

Posted: 22 Sep 2010 12:37
by rahulsehgal
check if the owner given in the job definition has the permission to execute the script...

Because this issue comes when the owner of the job doesnot have permission to execute the job or it has expired, thanks.

Regards,
Rahul Sehgal

Posted: 22 Sep 2010 4:48
by philmalmaison
are you sure about the path ???

/softs/ControlM/ctm/ctm_agent/ctm/sysout/CMD.LOG_0056dv_00002: Permission denie\ d.

because it should better be /softs/ControlM/ctm_agent/ctm/sysout

regards
Philmalmaison

Posted: 23 Sep 2010 8:26
by ctmnick
Hi
can re-set the fail over logs for Userid and try again.

nick.

Posted: 23 Sep 2010 10:32
by Ross_T_Boss
The owner of the job also needs to have permissions to write to the control-m sysout directory. Usually this means adding the job owner id to the control-m owners group, or opening up the permissions on the sysout directory to allow any user access.

In a prod environment group access is the way to go.

Posted: 23 Sep 2010 3:52
by fileal2
Thank you for your replies..

Somehow the permissions on the agents directories got corrupted. I ended up re-installing the agent and it works fine now..

Re: FAILED TO EXECUTE DUE TO USER ENVIRONMENT

Posted: 27 Aug 2015 10:47
by jagdishn78
Hello,

I also facing the same issue.

26/08/2015 19:00:02 TR5100 ENDED AT 20150826190002. OSCOMPSTAT -2. RUNCNT 1
26/08/2015 19:00:02 TR5112 JOB FAILED TO EXECUTE DUE TO USER ENVIRONMENT
26/08/2015 19:00:02 TR5169 Message from Agent: /export/home/ctmuser/ctminstall/Solaris/ctm/sysout/GIS_Batch.LOG_003tee_00001
26/08/2015 19:00:04 TR5140 EMAIL TO controlmescar@enwl.co.uk;ControlM-Team@enwl.co.uk PERFORMED
26/08/2015 19:00:04 TR5134 ENDED NOTOK
...

Sysout :

20150826 190001 Failed to submit job.
20150826 190001 Found empty sysout file.
20150826 190001 Possible cause of problem:
1. Job submission aborted due to error in executing '/bin/sh'.
2. Job submission aborted due to error in Autoedit variables.
login. STDOUT -->>
login. STDERR -->>


Please help.

Which folder of ctm agent need to be given permission ?
we have below permissions is in place.

drwxr-xr-x 2 ctmuser oinstall 2 Aug 26 09:34 cm
drwx------ 2 ctmuser oinstall 2 Aug 26 09:34 onstmt
drwxr-xr-x 7 ctmuser oinstall 12 Aug 26 09:34 JRE
drwxr-xr-x 2 ctmuser oinstall 5 Aug 26 09:34 hcu
drwxr-xr-x 2 ctmuser oinstall 9 Aug 26 09:34 toolbox
drwxr-xr-x 2 ctmuser oinstall 9 Aug 26 09:34 scripts
drwxr-xr-x 7 ctmuser oinstall 65 Aug 26 09:34 exe
drwxr-xr-x 2 ctmuser oinstall 4 Aug 26 16:15 pid
drwxr-xr-x 2 ctmuser oinstall 5 Aug 26 16:15 locks
drwxr-xr-x 7 ctmuser oinstall 36 Aug 26 16:15 data
drwxr-xr-x 2 ctmuser oinstall 4 Aug 26 19:00 runtime
drwxr-xr-x 2 ctmuser oinstall 39 Aug 26 19:00 proclog
drwxr-xr-x 2 ctmuser oinstall 3 Aug 26 19:00 sysout
drwx------ 2 ctmuser oinstall 2 Aug 26 19:00 procid
drwx------ 2 ctmuser oinstall 3 Aug 26 19:00 backup
drwx------ 2 ctmuser oinstall 2 Aug 26 19:00 status
drwxr-xr-x 2 ctmuser oinstall 2 Aug 27 08:17 temp
drwxr-xr-x 2 ctmuser oinstall 4 Aug 27 09:31 dailylog


Thanks in Advance.

Regards,
Jagdish