SoftTree Technologies SoftTree Technologies
Technical Support Forums
RegisterSearchFAQMemberlistUsergroupsLog in
Remote Job Output
Goto page Previous  1, 2
 
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite View previous topic
View next topic
Remote Job Output
Author Message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6485

Post Reply with quote
Quote:
2016-12-22 12:37:36,061 [Thread-7] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): timeout check not required
2016-12-22 12:37:36,201 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2016-12-22 12:37:36,201 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code: 0
2016-12-22 12:37:36,201 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : output:


This is helpful . It shows that the agent doesn't see job output. That's why it comes back empty.

Now, may I ask you for a favor, can you try a slightly different test? Please set the test job properties to use the same user account that you use for running the agent. I mean the Run As settings in the job properties. Could you please post relevant portion of the agent's debug.log after trying that?
Thu Dec 22, 2016 3:14 pm View user's profile Send private message
wanbaugj



Joined: 20 Dec 2016
Posts: 8
Country: United States

Post Reply with quote
I am using the same account in run as as the agent is running on the remote server. I was running the agent as a service, but I turned that off and now am logged in as the same user in the run as field. Same results.
2016-12-23 10:14:36,169 [RMI TCP Connection(2)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Authenticating user trinity-health\nodcbatch_ctlm
2016-12-23 10:14:36,169 [RMI TCP Connection(2)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: D:\24x7_Scheduler\userchk.exe
2016-12-23 10:14:36,325 [RMI TCP Connection(2)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Starting job=TEST, runtime id=419
2016-12-23 10:14:36,325 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2016-12-23 10:14:36,325 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: D:\24x7_Scheduler\userchk.exe
2016-12-23 10:14:36,372 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [cmd /c dir] in work directory [null]
2016-12-23 10:14:36,372 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - Job RUN_AS_USER value is not the same as the current user. Process will be launched in the a user session.
2016-12-23 10:14:36,372 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2016-12-23 10:14:36,372 [Thread-6] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
2016-12-23 10:14:36,372 [Thread-6] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): timeout check not required
2016-12-23 10:14:36,528 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2016-12-23 10:14:36,528 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code: 0
2016-12-23 10:14:36,528 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : output:
2016-12-23 10:14:36,528 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2016-12-23 10:14:36,528 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2016-12-23 10:14:36,575 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Writing output file C:\Users\NODCBA~1\AppData\Local\Temp\3\24x7_419.tmp
2016-12-23 10:14:36,575 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Completed job=TEST, runtime id=419
2016-12-23 10:14:36,590 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - transferFileFromAgent: start
2016-12-23 10:14:36,590 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - file : C:\Users\NODCBA~1\AppData\Local\Temp\3\24x7_419.tmp
2016-12-23 10:14:36,606 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.javascript.JavaScriptCommand - Start: execFileDelete
2016-12-23 10:14:36,606 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.javascript.JavaScriptCommand - File: C:\Users\NODCBA~1\AppData\Local\Temp\3\24x7_419.tmp
Fri Dec 23, 2016 11:19 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6485

Post Reply with quote
Quote:
I am using the same account in run as as the agent is running on the remote server.

It might be the same account trinity-health\nodcbatch_ctlm but not entered exactly the same way as it appears in the echo %USERDOMAIN%\%USERNAME%. please note that case sensitivity is important to 24x7 when names are compared; 24x7 is a cross-platform solution, and user names are case sensitive on many platforms.


So, because the user name isn't matched, the log shows
Quote:
2016-12-23 10:14:36,372 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - Job RUN_AS_USER value is not the same as the current user. Process will be launched in the a user session.

As a result, the process is started in a separate user session. I speculate that is the root cause of the agent not getting the process output, and as a result, downstream the output is not returned back to the scheduler.

As an option of course you can always send the output to a custom file, for example, change your test job command line to something like cmd /C dir > C:\24x7\Output\my_file.log and then optionally transfer that file back to the scheduler (multiple methods available for that), or append to the same file on each run both cmd /C dir >> C:\24x7\Output\my_file.log or even have a dynamically generated file name so logs don't overwrite on each run cmd /C dir > C:\24x7\Output\my_file_(@T"yyyy-mm-dd hh-mm-ss").log. Here @T"yyyy-mm-dd hh-mm-ss" is a macro-variable supported by 24x7, which in job run time is substituted with a system time value in the format specified.
Sat Dec 24, 2016 10:44 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6485

Post Reply with quote
Have you had a chance to correct the user name and test if that resolves the issue with the empty output?
Thu Jan 05, 2017 11:15 am View user's profile Send private message
Display posts from previous:    
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite All times are GMT - 4 Hours
Goto page Previous  1, 2
Page 2 of 2

 
Jump to: 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

 

Powered by phpBB © 2001, 2005 phpBB Group
Design by Freestyle XL / Flowers Online.