Author |
Message |
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Currently using version 3.4.16 enterprise wide across 10 sites and 50+ servers so upgrading will be pretty infrequent to say the least if it involves server reboots. At which version did this functionality improve ? and what about stopping jobs run using "run now" ? On a general package upgrade topic are the product version release notes/changelogs available online ? Thanks Jim : In recent versions of the scheduler jobs can be stopped/paused/resumed : directly from the Job Queue Monitor. If you are running an old version : please consider upgrading.
|
|
Tue Feb 08, 2005 11:09 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Restarting computers is recommended after install but it is not required. The upgrade takes less then a minute to run so that the downtime is really minimal. It can be even done silently from a batch file or other automated program. To explore these options check Silent install topic. To stop/start 24x7 service from command line before and after install use NET STOP "24x7 Scheduler" and then NET START "24x7 Scheduler" The quickest way to find changes in any particular version is to run a search on this message board with "changes in x.x.x" in the message text "all words" where you replace x.x.x with a number of the version of the interest. Below is a list of links describing all changes since 3.4.16 ********** Versions 3.4.23 and 3.4.24 included some enhancements and internal changes in the Java API layer to make 24x7 Scheduler Windows version compatible with the Java API in 24x7 Scheduler Java Edition and also enhancements in 24x7 Web-based Management Console (JSP version) changes in 3.4.22 http://www.softtreetech.com/cgi_bin/config.cgi?read=5570 changes in 3.4.21 http://www.softtreetech.com/cgi_bin/config.cgi?read=5495 changes in 3.4.19 and 3.4.20 http://www.softtreetech.com/cgi_bin/config.cgi?read=5335 changes in 3.4.18 http://www.softtreetech.com/cgi_bin/config.cgi?read=5082 changes in 3.4.17 http://www.softtreetech.com/cgi_bin/config.cgi?read=4759 ********** : Currently using version 3.4.16 enterprise wide across 10 sites and 50+ : servers : so upgrading will be pretty infrequent to say the least if it involves server : reboots. : At which version did this functionality improve ? and what about stopping : jobs run using "run now" ? : On a general package upgrade topic are the product version release : notes/changelogs : available online ? : Thanks : Jim
|
|
Tue Feb 08, 2005 11:38 am |
|
|
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Hi again - thanks for the info. I have installed 24x7 from scratch (one full and one remote agent only) on two servers recently (in our testbench)and certainly, in at least the case of the remote agent install the server required a reboot after configuring the agent to run as a service :( - all instances are currently on NT4-SP6a Is there anyway to tell in advance whether an upgarde to an existing installation will in fact require a reboot ? Thanks, Jim : Restarting computers is recommended after install but it is not required. The : upgrade takes less then a minute to run so that the downtime is really : minimal. It can be even done silently from a batch file or other automated : program. To explore these options check Silent install topic. To : stop/start 24x7 service from command line before and after install use NET : STOP "24x7 Scheduler" and then NET START "24x7 : Scheduler" : The quickest way to find changes in any particular version is to run a search : on this message board with "changes in x.x.x" in the message : text "all words" where you replace x.x.x with a number of the : version of the interest. : Below is a list of links describing all changes since 3.4.16 : ********** : Versions 3.4.23 and 3.4.24 included some enhancements and internal changes : in the Java API layer to make 24x7 Scheduler Windows version compatible with : the Java API in 24x7 Scheduler Java Edition and also enhancements in 24x7 : Web-based Management Console (JSP version) : changes in 3.4.22 : http://www.softtreetech.com/cgi_bin/config.cgi?read=5570 : changes in 3.4.21 : http://www.softtreetech.com/cgi_bin/config.cgi?read=5495 : changes in 3.4.19 and 3.4.20 : http://www.softtreetech.com/cgi_bin/config.cgi?read=5335 : changes in 3.4.18 : http://www.softtreetech.com/cgi_bin/config.cgi?read=5082 : changes in 3.4.17 : http://www.softtreetech.com/cgi_bin/config.cgi?read=4759 : **********
|
|
Tue Feb 08, 2005 9:53 pm |
|
|
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Forgot to ask in last post - what about stopping "run now" jobs within 24x7 ? or was the implication that the stop/start service was the mechanism ? or is this just an aid to upgarding th e software without needing a reboot? Jim : Hi again - thanks for the info. : I have installed 24x7 from scratch (one full and one remote agent only) on : two : servers recently (in our testbench)and certainly, in at least the case of the : remote agent install the server required a reboot after configuring the agent : to : run as a service :( - all instances are currently on NT4-SP6a : Is there anyway to tell in advance whether an upgarde to an existing : installation : will in fact require a reboot ? : Thanks, : Jim
|
|
Tue Feb 08, 2005 9:56 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
Re: Stopping Jobs - in queue and "run now& |
|
If you are upgrading an existing installation of the same major version (for example, going from 3.4.0 to 3.4.25) then reboot is not required and you can ignore the setup program prompt to reboot, you can choose "reboot later" option. Here is some background info, the upgrade is cumulative, can be used for any version 3.0.0 and later and because of that the setup program doesn't really know for sure whether the reboot is really needed or not, it only knows if it needs to replace some locked files which can be done after reboot only. Now, when you change service settings in the 24x7 Tools/Options menu it also prompts you to reboot if you use LocalSystem account for the service. If you can see and start the service manually from the Services applet then you can ignore that prompt as well. By the way, the service can be installed using setup program run with /SERVICE command line switches. In any case save method without restarting computer is the following: 1. If 24x7 Scheduler service is running stop it 2. If stop 24x7 Event Server service is running stop it 3. If 24x7 Scheduler GUI or other 24x7 GUI running close it 4. If you use 24x7 Web-based console (ASP version) and the web server is running on the same computer stop IIS Admin service 5. If you have 24x7 extension agent installed, stop SNMP service 6. Run the upgrade 7. Restarted previously stopped services Regarding stopping of Run Now jobs. If you pick Test Mode for the run you cannot kill the job from within 24x7 GUI because the job is run in the foreground and the GUI is "frozen" during job run. If you pick Normal mode (e.g. run in the background using job queue) then you can kill it using Queue Monitor just as you can kill any other background job. : Forgot to ask in last post - what about stopping "run now" jobs : within 24x7 ? or was the implication that the stop/start service : was the mechanism ? or is this just an aid to upgarding th e software without : needing a reboot? : Jim
|
|
Tue Feb 08, 2005 10:54 pm |
|
|
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Thanks for the detailed and very usefull information which has resolved most of my earlier concerns. The only question I have remaining on this topic is how do you actually select to run the "run now" job candidate as "test" or "normal" mode ? Jim : If you are upgrading an existing installation of the same major version (for : example, going from 3.4.0 to 3.4.25) then reboot is not required and you : can ignore the setup program prompt to reboot, you can choose "reboot : later" option. Here is some background info, the upgrade is : cumulative, can be used for any version 3.0.0 and later and because of : that the setup program doesn't really know for sure whether the reboot is : really needed or not, it only knows if it needs to replace some locked : files which can be done after reboot only. : Now, when you change service settings in the 24x7 Tools/Options menu it also : prompts you to reboot if you use LocalSystem account for the service. If : you can see and start the service manually from the Services applet then : you can ignore that prompt as well. By the way, the service can be : installed using setup program run with /SERVICE command line switches. : In any case save method without restarting computer is the following: 1. If : 24x7 Scheduler service is running stop it : 2. If stop 24x7 Event Server service is running stop it : 3. If 24x7 Scheduler GUI or other 24x7 GUI running close it : 4. If you use 24x7 Web-based console (ASP version) and the web server is : running on the same computer stop IIS Admin service : 5. If you have 24x7 extension agent installed, stop SNMP service : 6. Run the upgrade : 7. Restarted previously stopped services : Regarding stopping of Run Now jobs. If you pick Test Mode for the run you : cannot kill the job from within 24x7 GUI because the job is run in the : foreground and the GUI is "frozen" during job run. If you pick : Normal mode (e.g. run in the background using job queue) then you can kill : it using Queue Monitor just as you can kill any other background job.
|
|
Wed Feb 09, 2005 12:11 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Sorry, I forgot to mention that if you run "silent" setup with /NORESTART option then it will not attempt to restart the computer after installation is complete : Thanks for the detailed and very usefull information which has resolved most : of my earlier concerns. : The only question I have remaining on this topic is how do you actually : select to run the "run now" job candidate as "test" or : "normal" mode ? : Jim
|
|
Wed Feb 09, 2005 12:27 pm |
|
|
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Thanks Again, Still don't understand how to :- The only question I have remaining on this topic is how do you actually select to run the "run now" job candidate as "test" or "normal" mode as mentioned in your earlier response on this subject ?? Jim : Sorry, I forgot to mention that if you run "silent" setup with : /NORESTART option then it will not attempt to restart the computer after : installation is complete
|
|
Wed Feb 09, 2005 12:41 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
Re: Stopping Jobs - in queue and "run now& |
|
You are probably using old version of 24x7, which doesn't support that feature. Recent versions prompt you how to run a job when you click the Run Now button or press CTRL+R. In your version you can trigger job run without blocking the GUI using "24x7 /JOB [job]" command from the DOS prompt or from the Run box in the Windows Start Menu. Replace [job] with the actual job id or name. : Thanks Again, : Still don't understand how to :- : The only question I have remaining on this topic is how do you actually : select to run the "run now" job candidate as "test" or : "normal" mode as mentioned in your earlier response on this subject : ?? : Jim
|
|
Wed Feb 09, 2005 12:47 pm |
|
|
Jim Maxwell
Joined: 12 Feb 2004 Posts: 73
|
|
Re: Stopping Jobs - in queue and "run now& |
|
O.K. - Thanks If I upgrade only the server hosting the Master Sheduler can I keep the Remote Agent Systems as they are ? Jim : You are probably using old version of 24x7, which doesn't support that : feature. Recent versions prompt you how to run a job when you click the : Run Now button or press CTRL+R. : In your version you can trigger job run without blocking the GUI using : "24x7 /JOB [job]" command from the DOS prompt or from the Run : box in the Windows Start Menu. Replace [job] with the actual job id or : name.
|
|
Wed Feb 09, 2005 12:57 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
Re: Stopping Jobs - in queue and "run now& |
|
Hm... probably, but there is no guarantee. : O.K. - Thanks : If I upgrade only the server hosting the Master Sheduler can I keep the : Remote Agent Systems as they are ? : Jim
|
|
Wed Feb 09, 2005 1:36 pm |
|
|
|