Closed
Bug 786748
Opened 13 years ago
Closed 13 years ago
[staging] adjust socorro submitter test tool
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: bburton)
References
Details
(Whiteboard: [push interrupt])
Right now stage has this entry in /etc/cron.d/socorro:
*/3 * * * * socorro /data/socorro/application/scripts/crons/cron_submitter.sh crash-reports.allizom.org 1000 > /dev/null 2>&1
This should instead be:
*/3 * * * * socorro /data/socorro/application/scripts/crons/cron_submitter.sh crash-reports-dev.allizom.org 1000 > /dev/null 2>&1
| Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-webops → bburton
| Assignee | ||
Comment 1•13 years ago
|
||
Pushed live with puppet
notice: /File[/etc/cron.d/socorro]/content:
--- /etc/cron.d/socorro 2012-07-31 16:53:53.000000000 -0700
+++ /tmp/puppet-file20120829-18486-10hvkuw-0 2012-08-29 11:28:04.000000000 -0700
@@ -9,7 +9,7 @@
00 17 * * * socorro /data/socorro/application/scripts/crons/cron_modulelist.sh
05 21 * * 2 socorro /data/socorro/application/scripts/crons/cron_create_partitions.sh
-*/3 * * * * socorro /data/socorro/application/scripts/crons/cron_submitter.sh crash-reports.allizom.org 1000 > /dev/null 2>&1
+*/3 * * * * socorro /data/socorro/application/scripts/crons/cron_submitter.sh crash-reports-dev.allizom.org 1000 > /dev/null 2>&1
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•13 years ago
|
||
Confirmed it ran
Aug 29 11:30:01 socorroadm CROND[20862]: (socorro) CMD (/data/socorro/application/scripts/crons/cron_submitter.sh crash-reports-dev.allizom.org 1000 > /dev/null 2>&1)
Updated•13 years ago
|
Whiteboard: [push interrupt]
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•