Closed Bug 1173845 Opened 10 years ago Closed 10 years ago

funsize schedulers are failing to start

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1173960

People

(Reporter: kmoir, Assigned: kmoir)

Details

nagios-releng Thu 09:20:24 PDT [4050] buildbot-master89.bb.releng.scl3.mozilla.com:procs - funsize-scheduler is CRITICAL: PROCS CRITICAL: 0 processes with regex args /builds/funsize/bin/funsize-scheduler (http://m.mozilla.org/procs+-+funsize-scheduler) nagios-releng Thu 09:20:24 PDT [4051] buildbot-master94.bb.releng.use1.mozilla.com:procs - funsize-scheduler is CRITICAL: PROCS CRITICAL: 0 processes with regex args /builds/funsize/bin/funsize-scheduler (http://m.mozilla.org/procs+-+funsize-scheduler) The log (/builds/funsize/scheduler.log) show this Traceback (most recent call last): File "/builds/funsize/bin/funsize-scheduler", line 5, in <module> from pkg_resources import load_entry_point File "/builds/funsize/lib/python2.7/site-packages/distribute-0.6.24-py2.7.egg/pkg_resources.py", line 2707, in <module> working_set.require(__requires__) File "/builds/funsize/lib/python2.7/site-packages/distribute-0.6.24-py2.7.egg/pkg_resources.py", line 686, in require needed = self.resolve(parse_requirements(requirements)) File "/builds/funsize/lib/python2.7/site-packages/distribute-0.6.24-py2.7.egg/pkg_resources.py", line 584, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: markupsafe Investigating
Assignee: nobody → kmoir
I don't think this matters because the work in bug 1172023 is not complete, will ack the nagios alerts
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Sorry for the noise, I thought marking them as downtimed for a week meant they wouldn't alert...seems that the downtime expires as soon as they recover once though.
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.