Closed Bug 969234 Opened 12 years ago Closed 12 years ago

[stage] please deploy log rotation hotfix for browserid train-2013.10.09

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jrgm, Assigned: gene)

Details

Gene please build an rpm as noted below, and build stage stacks with that RPM. SHA: d915ec0b4efca9ebe4b555df841edfe7b3887074 Repo: https://github.com/mozilla/persona Branch: train-2013.10.09 L10N SVN revistion: r121508 This contains the fixes to do log rotation with winston on that branch. https://github.com/mozilla/persona/pull/4090/files It adds two (optional) configuration settings: - winston_logging_maxsize (default 0 [disabled]) - winston_logging_maxfiles (default 10, but moot if no maxsize) We can chat about what the appropriate values for these should be, if you want.
Oops, cloning doesn't preserve 'assigned-to'. Assign to Gene now.
Assignee: nobody → gene
Status: NEW → ASSIGNED
Stack 0207 is up and DNS has been pointed to it.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I'll note one quirk of this log rotation: since the browserid and verifier daemons fork of worker processes with the logfile file handle open, these workers will continue to hold on to the logfile after the parent process has rotated to a new logfile. So basically one or more logfiles will continue to use disk space even after the file has been deleted.
Okay, looks good. Asking for prod stacks in bug 970466.
You need to log in before you can comment on or make changes to this bug.