Logs show agent contacted, scheduler logs show nothing

Here is the scheduler log for about the time
25-Mar-2008 11:02:44 PM 2 null 46 reporttable extract Job finished.
25-Mar-2008 11:02:44 PM 2 null 46 reporttable extract Remote job finished.
26-Mar-2008 12:02:33 AM 2 null 46 reporttable extract Remote job started.
26-Mar-2008 12:02:33 AM 2 null 46 reporttable extract Job started.
26-Mar-2008 12:02:40 AM 2 null 56 Update Dates Remote job started.
26-Mar-2008 12:02:40 AM 2 null 56 Update Dates Job started.
26-Mar-2008 12:02:49 AM 2 null 56 Update Dates Job finished.
26-Mar-2008 12:02:49 AM 2 null 56 Update Dates Remote job finished.
26-Mar-2008 12:03:10 AM 2 null 46 reporttable extract Job finished.
26-Mar-2008 12:03:10 AM 2 null 46 reporttable extract Remote job finished.
26-Mar-2008 12:06:26 AM 2 null 54 pw extract Remote job started.
26-Mar-2008 12:06:26 AM 2 null 54 pw extract Job started.
26-Mar-2008 12:06:29 AM 2 null 54 pw extract Job finished.
26-Mar-2008 12:06:29 AM 2 null 54 pw extract Remote job finished.
26-Mar-2008 12:26:26 AM 2 null 55 cf pw extract Remote job started.
26-Mar-2008 12:26:26 AM 2 null 55 cf pw extract Job started.
26-Mar-2008 12:26:28 AM 2 null 55 cf pw extract Job finished.
26-Mar-2008 12:26:28 AM 2 null 55 cf pw extract Remote job finished.
26-Mar-2008 01:01:48 AM 2 null 46 reporttable extract Remote job started.
26-Mar-2008 01:01:48 AM 2 null 46 reporttable extract Job started.
26-Mar-2008 01:03:22 AM 2 null 46 reporttable extract Job finished.
26-Mar-2008 01:03:23 AM 2 null 46 reporttable extract Remote job finished.
26-Mar-2008 02:02:25 AM 2 null 46 reporttable extract Remote job started.
26-Mar-2008 02:02:25 AM 2 null 46 reporttable extract Job started.
26-Mar-2008 02:02:49 AM 2 null 46 reporttable extract Job finished.

Here is the log on the Master
26-Mar-2008 00:05:39 datablaster-at 47 Reset drivers Agent "IAT" contacted.
26-Mar-2008 00:05:32 datablaster-at 47 Reset drivers Remote job started.

Something is goofy with the time that im missing

The other strange thing and i am not sure it has anything to do with my problem but, when i close the master scheduler it tells me a spawned job is running and will killed. Nothing is running i checked everywhere.

First log seems to be fro m24x7 Scheduler MP Edition; second is from 24x7 Window Edition. Am I correct?

While MP can use Windows version as its remote agent, it doesn't work the other way around, which tells me that you might be running something else on the agent computer, some other 24x7 version or component being contacted by the scheduler, perhaps starting it from a different directory, and that's why you don't see relevant records in the log. Does it make sense?

So now i have a protected Job i unprotect and modify and when when i hit save and its protected again. If i close and restart master its protected again. I have 70 jobs i cant modify for some reason beacuse it wont save my changes to the jobs and locks it as protected no matter how many times I unprotect the job

No they are both Multi platform editions. One is running on windows one on Linux. Its just started acting real weird a couple days ago. The master log i pulled from the HTML logs but it says the same thing as when you hit the LOG button in the program.

Ok i took the Microsoft approach a shut down, rebooted and restarted everything. Its now saving my changes to jobs and protecting thr jobs. Still no idea why its contacting Agent and agent isnt recording it so back to the original problem.

Can i not have two jobs kick off at the same exact time?

On agent the scheduler.log file
26-Mar-2008 12:02:05 PM 2 null 30 IAT File Upload Remote job started.
26-Mar-2008 12:02:05 PM 2 null 30 IAT File Upload Job started.
26-Mar-2008 12:02:27 PM 2 null 30 IAT File Upload Job finished.
26-Mar-2008 12:02:27 PM 2 null 30 IAT File Upload Remote job finished.

On master the HTML log
26-Mar-2008 12:01:27 datablaster-at 30 IAT File Upload Finish message sent.
26-Mar-2008 12:01:26 datablaster-at 30 IAT File Upload Remote job finished.
26-Mar-2008 12:01:04 datablaster-at 30 IAT File Upload Agent "IAT" contacted.
26-Mar-2008 12:01:02 datablaster-at 46 reporttable extract Agent "IAT" contacted.
26-Mar-2008 12:01:00 datablaster-at 46 reporttable extract Remote job started.
26-Mar-2008 12:01:00 datablaster-at 30 IAT File Upload Remote job started.

Let's address one thing a time, in order not to miss anything.

About removing jobs protection status and not saved changed: I'm guessing that you are using either Terminal Client or Remote Desktop. Windows replaces all your file changes after you close your session. That's why when you reconnect you don't see them there. Am I right?

	Quote:
	Can i not have two jobs kick off at the same exact time?

Yes, you can assign them to the same job queue and set them to run in synchronous mode. This way they won't be able to run concurrently.

I have them running in 2 different Job Q's asynch shouldnt that work?

	Quote:
	No they are both Multi platform editions. One is running on windows one on Linux.... Ok i took the Microsoft approach a shut down, rebooted and restarted everything. Its now saving my changes to jobs and protecting thr jobs. Still no idea why its contacting Agent and agent isn't recording it so back to the original problem.

This is good news. Because we can enable tracing options on both sides and check debug.log files after running the remote job. These logs should help us to figure out what is going on.

My wild guess is that the remote job fails to authenticate with the system and that's why it doesn't run or even appear in the scheduler.log file on the agent side. The scheduler somehow is not aware that the job doesn't really start running and it waits forever for the job to complete.

Yeah i agree that its waiting in the log but the monitor shows its running and the on the agent side it never reports anything in the scheduler.log file. Thats just bizzare some how we have tricked the Master scheduler into thinking the job is running. When i kill or terminate the job in the monitor tool and get this
2008-03-26 12:32:20,727 [RMI TCP Connection(2762)-192.168.171.45] ERROR com.softtreetech.jscheduler.business.runner.JobExecutorImpl - killJob: unable to find job with run-time #1994

I am confused the job shows as running but really isnt and when you go to terminate the job in the monitor tool it says its unable to kill it because it doesnt exsist.

I can push the run now button just a minute or two after I realize the agent and master are not on the same page and the job runs fine.

	Quote:
	I have them running in 2 different Job Q's asynch shouldnt that work?

No. The effect is complete opposite to what you want. You don't want them to be able to start at the same time. Right? They are currently completely independent - each queue is like a mini-scheduler.

Last edited by SysOp on Wed Mar 26, 2008 12:53 pm; edited 1 time in total

Quote:

Yeah i agree that its waiting in the log but the monitor shows its running and the on the agent side it never reports anything in the scheduler.log file. Thats just bizzare some how we have tricked the Master scheduler into thinking the job is running. When i kill or terminate the job in the monitor tool and get this
2008-03-26 12:32:20,727 [RMI TCP Connection(2762)-192.168.171.45] ERROR com.softtreetech.jscheduler.business.runner.JobExecutorImpl - killJob: unable to find job with run-time #1994

I am confused the job shows as running but really isnt and when you go to terminate the job in the monitor tool it says its unable to kill it because it doesnt exsist.

I agree, something is not ticking here. Let's review debug.log files.