Author |
Message |
John Natale
Joined: 13 Sep 2000 Posts: 107
|
|
Remote Job Output |
|
Hello,
When I run a job remotely I get an output file but it's always empty
File: C:\24x7\Output\12\12_20141002133607.out
Time: 2-Oct-2014 01:36:07 PM
Size: 0 bytes
====================================================
File content empty
But run same job locally and there is output in the file
Thanks,
John
|
|
Thu Oct 02, 2014 1:48 pm |
|
 |
John Natale
Joined: 13 Sep 2000 Posts: 107
|
|
|
|
hmmm .... interesting
A JAL job returns output
|
|
Thu Oct 02, 2014 2:22 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
What kind of a job isn't returning an output?
|
|
Thu Oct 02, 2014 6:30 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
I am having the same issue. Tried run program or batch file and tried script, both are not giving me any output.
trying to run "cmd /c dir" on a Windows 7 PC
|
|
Tue Dec 20, 2016 2:04 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Which scheduler version are you running?
Are you referring to a remote job?
If yes, can you see the output file on the remote system?
|
|
Tue Dec 20, 2016 2:53 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
I am running trial download. 24x7 Scheduler Multi-platform Edition, version is 5.3. If I write output to a text file, I can see it on the remote system, but I do not see any other output files on the remote system.
|
|
Tue Dec 20, 2016 3:56 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Do you have the tracing option (Options dialog - Log tab - Trace Enabled check box) enabled in the agent's settings? If not, please enable it and try again.
|
|
Tue Dec 20, 2016 4:11 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
enable the option, still no output that I can find on remote or local.
Where does the output save on the remote agent?
File: C:\PROGRA~2\24x7_Scheduler\Output\9\9_20161220162316.out
Time: 20-Dec-2016 04:23:16 PM
Size: 0 bytes
=====================================================
[File content is empty]
|
|
Tue Dec 20, 2016 5:30 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
May I know the job command/script being tested? Did the job complete successfully? Expected to produce any output? Does the test job have id 9?
|
|
Tue Dec 20, 2016 5:34 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
I have run "cmd /c dir" and cmd /c "timeout 60". These have both completed with exit code 0. Yes there should be output for dir. Yes the ID is 9.
|
|
Tue Dec 20, 2016 5:39 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
I don't see anything wrong there except the suspicious location of the installed 24x7 software. On your test system the security policies may prevent programs from writing to files in Program Files folder or its subfolders. I recommend reinstalling the software and selecting C:\24x7 home folder.
|
|
Tue Dec 20, 2016 6:20 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
Reinstalled to C:\24x7 folder, and same issue.
|
|
Wed Dec 21, 2016 4:16 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
Ok reinstalled onto some 2008 R2 servers with no admin restrictions, now I amd getting the message below -
An error occurred while executing automation script: Line 1: missing ; before statement
|
|
Wed Dec 21, 2016 5:33 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Please enable tracing options in the agent's settings. If running in desktop mode, it can be found in Tools -> Options menu > Log tab -> Trace Enabled option. After that rerun the test job and check what appears in the debug.log file in the agent's home folder c:\24x7. Do you see there any errors? Job output? anything else relevant to the issue?
|
|
Wed Dec 21, 2016 6:02 pm |
|
 |
wanbaugj
Joined: 20 Dec 2016 Posts: 8 Country: United States |
|
|
|
Ok, so the "missing ;" issue I think was related to exit code validation option having an incorrect value, I had "0]". Removed the bracket and now I am back to empty output.
Here's the debug log.
2016-12-22 12:37:35,936 [RMI TCP Connection(6)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Authenticating user xxxx
2016-12-22 12:37:35,936 [RMI TCP Connection(6)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: D:\24x7_Scheduler\userchk.exe
2016-12-22 12:37:36,014 [RMI TCP Connection(6)-10.200.114.115] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Starting job=TEST, runtime id=414
2016-12-22 12:37:36,014 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2016-12-22 12:37:36,014 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: D:\24x7_Scheduler\userchk.exe
2016-12-22 12:37:36,061 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [cmd /c dir] in work directory [null]
2016-12-22 12:37:36,061 [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-22 12:37:36,061 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2016-12-22 12:37:36,061 [Thread-7] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
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:
2016-12-22 12:37:36,201 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2016-12-22 12:37:36,201 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2016-12-22 12:37:36,217 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Writing output file C:\Users\NODCBA~1\AppData\Local\Temp\24x7_414.tmp
2016-12-22 12:37:36,217 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - Completed job=TEST, runtime id=414
2016-12-22 12:37:36,232 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - transferFileFromAgent: start
2016-12-22 12:37:36,232 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl - file : C:\Users\NODCBA~1\AppData\Local\Temp\24x7_414.tmp
2016-12-22 12:37:36,248 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.javascript.JavaScriptCommand - Start: execFileDelete
2016-12-22 12:37:36,248 [Job #9 - TEST] DEBUG com.softtreetech.jscheduler.business.runner.javascript.JavaScriptCommand - File: C:\Users\NODCBA~1\AppData\Local\Temp\24x7_414.tmp
|
|
Thu Dec 22, 2016 2:44 pm |
|
 |
|