How do you run that job as "synchronous" or "asynchronous"? What kind of job is it? In any case there should be both "start" and "finish" messages in the main log. The "finish" message on the remote agent is just a copy of the main message. If you run it as a script, you can turn on tracing on the remote agent (Tools/Options/Log/Trace enabled). This will cause the script tracing to be written to the script.log file and be also visible in the trace window and the Log Viewer. : Last night we encountered for the first time a strange problem. Our main 24x7 : scheduler submitted a job on a remote 24x7 agent machine to run. The : definition of the job has a semaphore file being created before and after : the job. The before file was there, but the after file and any remnants of : the job were nowhere to be found. : We had many other jobs in our job stream that ran on this remote machine. The : problem job ran earlier in the day during testing. The problem job ran : fine this morning after I came in and recreated the trigger file for the : problem job. : What I was wondering is there any logging that we can turn on on the remote : machine that will show what happen to this problem job? Most of the : entries in the log viewer on the remote machine show a finish messages, : but no job start messages or error messages.
|