|
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
rockenfeller
Joined: 23 Oct 2008 Posts: 16 Country: United States |
|
Disable on Error - Yes, but status remains Active on Error. |
|
(Environment)
Windows Server 2003
24x7 Version 3.5.2 running as a Windows Service
I have a synchronous job scheduled to execute a .NET console application every few minutes. It returns an exit code 0 upon successful execution. Other exit codes would indicate an error. The successful exit code information is configured in the job. It is also configured to automatically disable itself on error.
It appears to be working in my error testing trials. The console application has its own error reporting mechanism. The initial error was reported and logged. There were no subsequent errors, which indicates that the application did not execute. Therefore, the job should have been disabled.
I logged into the 24x7 instance via Remote Control with the expectation that the 24x7 instance disabled the job. Instead, the instance indicated that the job was still active. The recent job logs were not available via Remote Control.
Next, I logged into the actual machine where the service instance is hosted. I was able to view the logs there. They indicated the job was disabled, but the status indicates it is active.
Why is that? It seems counter-intuitive.
I used the the following procedure via Remote Control to re-enable the job:
1. Disable the job
2. Save Remote
3. Enable the job
4. Save Remote
On a separate note, Disable on Error does not seem to work when I schedule the job as asynchronous.
|
|
Thu Apr 09, 2009 9:08 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7907
|
|
|
|
It sounds like the error doesn't' bubble up all the way. Let's find out where it gets stuck.
Please check whether this job is set to run detached. If yes, uncheck the detached property and try to fail the job. Check if it gets disabled in this mode.
|
|
Thu Apr 09, 2009 10:02 pm |
|
|
rockenfeller
Joined: 23 Oct 2008 Posts: 16 Country: United States |
|
|
|
The job is not detached.
|
|
Thu Apr 09, 2009 10:05 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7907
|
|
|
|
All right. Does the job have 'Restart if it fails' property set?
Please post fragment of the job log indicating job start, job error, then related scheduler messages about disabling the job
|
|
Thu Apr 09, 2009 10:21 pm |
|
|
rockenfeller
Joined: 23 Oct 2008 Posts: 16 Country: United States |
|
|
|
No, the Restart if it fails property is not set.
Here is the log:
4/13/2009 9:33:53.147000 0 200 0 Blah Job started.
4/13/2009 9:34:01.687000 1 200 0 Blah Process finished with exit code 1
4/13/2009 9:34:01.707000 2 200 0 Blah Job failed. Exit code does not satisfy exit code condition.
4/13/2009 9:34:01.737000 1 200 0 Blah Job has been disabled!
The job is getting disabled, which is great. But, its status is not getting reflect as such.
One other observation... If I run the 24x7 standalone application when the Windows service is disabled, the job status explicitly changes to disabled on error.
|
|
Mon Apr 13, 2009 5:15 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7907
|
|
|
|
So it is when the scheduler is run as a service then the job is not disabled. Right?
I'd like to clarify one thing. When you run it as a standalone application, do you still use the Remote Control to connect to the server, or use the application GUI directly on the server? I'm after the visual appearance of the disabled state. In other words, trying to figure out whether you don't see the job appearing disabled in the Remote Control, or it doesn't get disabled when you run as a service, e.g. visual vs. actual.
|
|
Mon Apr 13, 2009 7:28 pm |
|
|
rockenfeller
Joined: 23 Oct 2008 Posts: 16 Country: United States |
|
|
|
It is when the job is run as a Windows Service when the job does not appear to be disabled. The behavior suggests that the job has been disabled, but it isn't reflected as such visually. That could be either the disabled job icon not appearing over the job or the textual representation (job is active) under the job's properties.
When I run it as a standalone, the Windows Service is disabled. I use the application GUI on the server.
|
|
Mon Apr 13, 2009 7:35 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7907
|
|
|
|
Thank you.
I suspect this is a bug. I'll research this more and get back to you when more information is available.
|
|
Mon Apr 13, 2009 7:44 pm |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|