Closed Bug 1167017 Opened 10 years ago Closed 10 years ago

crontabber locking not working in AWS stage

Categories

(Socorro :: Backend, task)

Product:
Socorro
Component:
Backend
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: rhelmer)

References

Details

We're getting multiple copies of crontabber running in stage - there should only be one. Currently it uses our own old janky lock implementation, maybe we should take this opportunity to move it to flock instead?
So the reason it's not working is because /var/lock/socorro doesn't exist - it's enough to just fix that I guess.
Status: NEW → ASSIGNED
Ah this is similar to bug 1162085 - /var/lock is a symlink to /run/lock now, and /run is wiped on reboot.
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/b33cc01f076149a301d5bd99ac2698421958c007 fix bug 1167017 - persist /var/lock/socorro on reboot https://github.com/mozilla/socorro/commit/3de89baaf1a7db78850d7358217104b2617c6c80 Merge pull request #2802 from rhelmer/bug1167017-persist-var-lock-socorro-on-reboot fix bug 1167017 - persist /var/lock/socorro on reboot
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.