Job Scheduling Problems Linux
I'm having an issue with the job-scheduling when I start a job via shell and I'm hoping somebody can give me some tips or had this issue before:
I'm changing the server from Solaris to Linux.
On solaris a job was started in the following way:
root> su - job100
job100> $BSE/rc.startjob_job100 import_data
(Note: In this script the job is started via the session ttaad5203m000)
The job started, was then shortly in the state "Running" and then updated the last and next runtime and was in the state "Waiting" for the next minute, cause this is the given period for this job.
And the job ran every minute and in between it was in the "Waiting" state. Everything was as expected.
Now on the new Linux server the job runs once, updates the times, then is in the state "Waiting" but runs never again!? It remains in "Waiting"- state forever.
This way to start a periodically job cannot longer be used in our new environment. But why?
I checked some logs and the processes but nothing unusual.
Shure we can set it up as job daemon but the question remains:
Why is this mechanism broken?
The help of the field "Suspend Job Until Next Execution" clearly states:
Out of curiosity I changed the field "Suspend Job Until Next Execution" from "Yes" to "No". Then I set the next running date in the near future. Then I started the job via the script.
Normaly it should execute the job at the given time, then it should set the job status to "Free" and update the next running time according to the interval and then exit the bshell.
But it also remains in the state "Waiting" and never executes anything. The bshell process never ends. !?!? Very curious...
we're on HP-UX and we use 'cron' to start our Jobs instead of the baan scheduler. Maybe that's an option for you?
Yeah. I forgot to say that because I wanted to hold it short,
but I sure use the cron to start all jobs.
Even for the one I mentioned with interval 1 minute and external planing turned off. So in case of an error I only have to make sure the old process is gone and the status is free again. The cron will restart the job the next minute and I don't have to take care of it. ;)
I did crawl through inforxtreme too, but just tips how to debug or to create dbs.logs .
Thank you all for your self-sacrificing help.
|All times are GMT +2. The time now is 10:18.|
©2001-2017 - Baanboard.com - Baanforums.com