ok we have a few different things happening: 1) httpd on the jenkins master is randomly (though not currently) flaking out and causing visits to the site to return a 503. nothing in the logs shows any problems.
2) there are some github timeouts, which i tracked down and think it's a problem with github themselves (see: https://status.github.com/ and scroll down to 'mean hook delivery time') 3) we have one spark job w/a strange ivy lock issue, that i just retriggered (https://github.com/apache/spark/pull/4964) 4) there's an errant, unkillable pull request builder job ( https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28574/console ) more updates forthcoming. On Fri, Mar 13, 2015 at 12:04 PM, shane knapp <skn...@berkeley.edu> wrote: > we just started having issues when visiting jenkins and getting 503 > service unavailable errors. > > i'm on it and will report back with an all-clear. >
