stop redirecting stderr for cron jobs

RESOLVED WONTFIX

Status

P2
minor
RESOLVED WONTFIX
8 years ago
7 years ago

People

(Reporter: rhelmer, Assigned: rhelmer)

Tracking

Trunk
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

8 years ago
The cron job for bug 629054 wasn't found to be failing until right before release day, because we are redirecting stderr for the "pyjob" cronjob wrapper function.

Bug 651201 provided a temporary workaround (print placeholder text so crond sends email if exit code !=0), but the real fix here is to not redirect stderr.

I don't know how noisy the current cron jobs are on stderr for non-critical-error scenarios, so this bug should include fixing of these if necessary.
Assignee: nobody → rhelmer
(Assignee)

Updated

8 years ago
Priority: -- → P2
(Assignee)

Updated

8 years ago
Assignee: rhelmer → nobody
(Assignee)

Comment 1

8 years ago
I can't think of a simple incremental way to do this without changing the way we do logging. Since we have a workaround in place now to get email if cron jobs are failing, I think this is not super urgent; we should investigate the way we do logging as part of 1.9.
Target Milestone: 1.7.8 → 1.9
Assignee: nobody → rhelmer
Target Milestone: 1.9 → ---
(Assignee)

Updated

8 years ago
Severity: normal → minor
Component: Socorro → General
Product: Webtools → Socorro
(Assignee)

Updated

7 years ago
Component: General → Backend
QA Contact: socorro → backend
(Assignee)

Comment 2

7 years ago
I'd rather just keep this in mind for the new crontabber system than try to shoehorn more into the existing shell/python system.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.