I have run 4 test cases which are detail below. There is no agent.log but there are several other logs including a master.log on the remote server. In all cases the master log appears to have no errors. I can send you the logs for each test if you need them. Please try these same cases in your environment to see if you get the same results. Also, because I started using your reboot method, the agent now remains running properly and communicates with the master scheduler after the reboot job has tried to run even when the reboot does not happen. Here are the test cases: Test Case 1: -- REBOOT FAILURE Environment: 1. A Windows account was logged on to the client server 2. Job JAL code on Master (runs job scheduler directly): Dim pid, number Run "d:\24x7\24x7.exe /JOB REBOOT", "", pid 3. The REBOOT job referenced in #2 above is a JAL script with the REBOOT statement. Outcome: 1. Server did not reboot 2. Processes running on the client server after the REBOOT job tried to execute: a. two processes called 24x7.exe b. one process called 24x7srv.exe 3. 24x7 master was able to connect to the 24x7 agent properly. 4. Logs written to or produced: a. schedule.log b. script.log c. stat.log d. master.log (no errors found) e. 24x7\Performance Data\142.log was produced Assumed Failure Reason: Job name in JAL script cannot be used. Job Id must be used. Test Case 2: -- REBOOT SUCCESS Environment: 1. A Windows account was logged on to the client server 2. Job JAL code on Master (runs job scheduler directly): Dim pid, number Run "d:\24x7\24x7.exe /JOB 140", "", pid 3. The job id 140 referenced in #2 above is a JAL script with the REBOOT statement. Outcome: 1. Server rebooted properly 2. Processes running on the client server after the REBOOT job tried to execute: a. one processes called 24x7.exe b. one process called 24x7srv.exe 3. 24x7 master was able to connect to the 24x7 agent properly. 4. Logs written to or produced: a. schedule.log b. script.log c. stat.log d. master.log (no errors found) e. 24x7\Performance Data\142.log was produced Assumed Success Reason: Job Id must be used instead of job name. Test Case 3: -- REBOOT FAILURE Environment: 1. A Windows account was NOT logged on to the client server 2. Job JAL code on Master (runs job scheduler directly): Dim pid, number Run "d:\24x7\24x7.exe /JOB 140", "", pid 3. The job id 140 referenced in #2 above is a JAL script with the REBOOT statement. Outcome: 1. Server did not reboot 2. Processes running on the client server after the REBOOT job tried to execute: a. one process called 24x7.exe b. one process called 24x7srv.exe 3. 24x7 master was able to connect to the 24x7 agent properly. 4. Logs written to or produced: a. schedule.log b. script.log c. stat.log d. master.log (no errors found) e. 24x7\Performance Data\140.log and 142.log were produced Assumed Failure Reason: A Windows NT account was not logged on to the client server. Test Case 4: -- REBOOT FAILURE (tried starting the reboot job from a CMD file) Environment: 1. A Windows account was NOT logged on to the client server 2. Job JAL code on Master (runs job scheduler using a Windows NT "CMD" file): Dim pid, number Run "d:\job_scripts\REBOOT.cmd", "", pid 3. Contents of the Windows NT "CMD" file: d:\24x7\24x7.exe /JOB 140 4. The job id 140 referenced in #3 above is a JAL script with the REBOOT statement. Outcome: 1. Server did not reboot 2. Processes running on the client server after the REBOOT job tried to execute: a. one process called 24x7.exe b. one process called 24x7srv.exe 3. 24x7 master was able to connect to the 24x7 agent properly. 4. Logs written to or produced: a. schedule.log b. script.log c. stat.log d. master.log (no errors found) e. 24x7\Performance Data\140.log and 141.log were produced Assumed Failure Reason: A Windows NT account was not logged on to the client server. : Did you check the agent.log file?
|