hi,
I have some cron submissions to the grid from the account wikisource-bot where the notifications of cron submission are sent to all users of the account.
what are the means to manage those notifications. * to have them sent to one specified user alone, rather than all users of the account? * to have them culled or written to a file?
Thx. Billinghurst
On Thu, Feb 15, 2018 at 5:12 PM, billinghurst billinghurstwiki@gmail.com wrote:
hi,
I have some cron submissions to the grid from the account wikisource-bot where the notifications of cron submission are sent to all users of the account.
what are the means to manage those notifications.
- to have them sent to one specified user alone, rather than all users of
the account?
- to have them culled or written to a file?
I assume these alerts are messages from the cron server about failures to jstart the job on the grid at the scheduled time? If your crons are actually starting grid jobs as expected I think that's the only way that cron would know that the job had output to standard out/standard error to email to you.
You can check out this little tutorial on cron email related things https://www.nixtutor.com/linux/sending-email-alerts-through-cron/ for some ideas. I'm not 100% sure if the "| mail" or ">/dev/null" style parts will actually work as expected in Toolforge. Our cron stuff is a bit abnormal in that the `crontab` program that you interact with on a bastion does some processing of the crontab data before saving it to a remote server (ping tools-cron-01.tools.eqiad.wmflabs at the moment). This pre-processing probably won't understand either of these unix shell constructs.
Can we back up a half step and talk about the root issues?
* What kinds of errors are you being alerted to and can they be fixed?
* Why do you want to only notify some of the tool maintainers when things are failing? Are you mixing many different things under a single tool? Would it be easier to manage these special jobs from another tool account designated for the purpose?
Bryan
On 16/02/2018 02:04, Bryan Davis wrote:
I assume these alerts are messages from the cron server about failures to jstart the job on the grid at the scheduled time?
- Why do you want to only notify some of the tool maintainers when
things are failing? Are you mixing many different things under a single tool? Would it be easier to manage these special jobs from another tool account designated for the purpose?
I actually get an email every time cron runs along the line of "Your job 1234567 ("XYZ") has been submitted", so not just failures messages.
On Thu, Feb 15, 2018 at 5:12 PM, billinghurst
what are the means to manage those notifications.
- to have them sent to one specified user alone, rather than all
users of
the account?
~/.forward (as the tool) works for me.
KTC
On Fri, Feb 16, 2018 at 1:48 PM, Katie Chan ktc@ktchan.info wrote:
On 16/02/2018 02:04, Bryan Davis wrote:
I assume these alerts are messages from the cron server about failures to jstart the job on the grid at the scheduled time?
- Why do you want to only notify some of the tool maintainers when
things are failing? Are you mixing many different things under a single tool? Would it be easier to manage these special jobs from another tool account designated for the purpose?
I actually get an email every time cron runs along the line of "Your job 1234567 ("XYZ") has been submitted", so not just failures messages.
Adding a `-quiet` argument to your jsub command should stop that message. By default jsub prints a notice to standard out on submission, but -quiet stops that.
Bryan