Re: [Labs-l] Changes to cron on tools
On 03/24/2014 04:43 PM, Marc A. Pelletier wrote: AT THE END OF THAT WEEK: any crontabs you may have had on tools-login or tools-bastion will be moved to the new server, and 'crontab' will be made to use the new system exclusively. You have no intervention to make; this will be done automatically. This had not been yet done to give everyone the time to perform the switch manually (and because I had limited availability), but will take place this Thursday, May 1. (That is, tomorrow). I will try take the time to manually inspect the edited crontabs for everyone to make any obvious fixes but please be aware that I cannot make more than a cursory inspection. If you notice issues in your scheduled cron jobs, simply examine the automatically modified crontab for correctness. -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
Re: [Labs-l] Changes to cron on tools
It could be nice to have original crontabs kept somewhere for manual inspection of the automatically prefixed version later. On May 1, 2014 1:33 AM, Marc-André Pelletier mpellet...@wikimedia.org wrote: On 03/24/2014 04:43 PM, Marc A. Pelletier wrote: AT THE END OF THAT WEEK: any crontabs you may have had on tools-login or tools-bastion will be moved to the new server, and 'crontab' will be made to use the new system exclusively. You have no intervention to make; this will be done automatically. This had not been yet done to give everyone the time to perform the switch manually (and because I had limited availability), but will take place this Thursday, May 1. (That is, tomorrow). I will try take the time to manually inspect the edited crontabs for everyone to make any obvious fixes but please be aware that I cannot make more than a cursory inspection. If you notice issues in your scheduled cron jobs, simply examine the automatically modified crontab for correctness. -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
Re: [Labs-l] Changes to cron on tools
Or people could do what I do, and place the crontab in a file and call crontab location of file. Makes it really easy to restore the crontabs, if it ever is lost. On Apr 30, 2014, at 1:38 PM, Marc-André Pelletier mpellet...@wikimedia.org wrote: On 04/30/2014 01:37 PM, Liangent wrote: It could be nice to have original crontabs kept somewhere for manual inspection of the automatically prefixed version later. I was planning to leave it in the tools' homes. I had not yet settled on a name yet but it'll be: ~/crontab.backup -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
Re: [Labs-l] Changes to cron on tools
On Mon, Mar 24, 2014 at 9:13 PM, Marc A. Pelletier m...@uberbox.org wrote: It will, by offloading that work to tools-sumbit. Funny - writing HTML forms, I too type sumbit *every. single. time.* ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
[Labs-l] Changes to cron on tools
Hey all, We've had difficulty in the past with cron jobs not running for a number of reasons (the primary being an overloaded bastion because of bots running on it), so I made a few changes to how cron is to be used in the future to vastly improve reliability: a) cron for tools will now be executed from a different, dedicated server that serves only that purpose. This will insulate the bastions from running cron jobs, and vice-versa. b) the 'crontab' executable will edit the crontabs /on that host/ directly (so there will be no need to change how you're doing thing); regardless of which bastion you run it from. (So, from tools-login or tools-dev, crontab will access the same schedule). c) crontabs will be automatically edited to add a prefix to send your jobs to the grid with reasonable default values unless the entry already invokes jsub, jstart or qsub. If the crontab program does that, it will tell you so that you can inspect and edit the entries and adapt them to your needs. Those three measures will result in considerably more reliable execution of scheduled jobs, as well as improved performance on the bastion hosts. FOR THE NEXT WEEK OR SO: both systems will be available at the same time. You can use the new system on the submit host by using 'xcrontab' rather than 'crontab' to set or edit your crontab. Be aware that /both/ schedules will be executed unless you also remove your bastion crontab. AT THE END OF THAT WEEK: any crontabs you may have had on tools-login or tools-bastion will be moved to the new server, and 'crontab' will be made to use the new system exclusively. You have no intervention to make; this will be done automatically. -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
Re: [Labs-l] Changes to cron on tools
I assume that means it should make tools-login more stable as well, since the crontab will auto adapt crontab entries to use jsub and not login. On Mar 24, 2014, at 4:43 PM, Marc A. Pelletier m...@uberbox.org wrote: Hey all, We've had difficulty in the past with cron jobs not running for a number of reasons (the primary being an overloaded bastion because of bots running on it), so I made a few changes to how cron is to be used in the future to vastly improve reliability: a) cron for tools will now be executed from a different, dedicated server that serves only that purpose. This will insulate the bastions from running cron jobs, and vice-versa. b) the 'crontab' executable will edit the crontabs /on that host/ directly (so there will be no need to change how you're doing thing); regardless of which bastion you run it from. (So, from tools-login or tools-dev, crontab will access the same schedule). c) crontabs will be automatically edited to add a prefix to send your jobs to the grid with reasonable default values unless the entry already invokes jsub, jstart or qsub. If the crontab program does that, it will tell you so that you can inspect and edit the entries and adapt them to your needs. Those three measures will result in considerably more reliable execution of scheduled jobs, as well as improved performance on the bastion hosts. FOR THE NEXT WEEK OR SO: both systems will be available at the same time. You can use the new system on the submit host by using 'xcrontab' rather than 'crontab' to set or edit your crontab. Be aware that /both/ schedules will be executed unless you also remove your bastion crontab. AT THE END OF THAT WEEK: any crontabs you may have had on tools-login or tools-bastion will be moved to the new server, and 'crontab' will be made to use the new system exclusively. You have no intervention to make; this will be done automatically. -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
Re: [Labs-l] Changes to cron on tools
On 03/24/2014 04:51 PM, Mr. Maximilian Doerr wrote: I assume that means it should make tools-login more stable as well It will, by offloading that work to tools-sumbit. -- Marc ___ Labs-l mailing list Labs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l
