[webkit-dev] bugs.webkit.org and trac.webkit org down?
skyul at company100.net
Thu Aug 9 06:00:26 PDT 2012
I can't access bugs.webkit.org again from Korea.
On Thu, Aug 9, 2012 at 9:51 PM, Peter Beverloo <peter at chromium.org> wrote:
> On Thu, Aug 9, 2012 at 12:49 PM, Mark Rowe <mrowe at apple.com> wrote:
>> On 2012-08-09, at 04:22, Peter Beverloo <peter at chromium.org> wrote:
>> On Thu, Aug 9, 2012 at 11:41 AM, Mark Rowe <mrowe at apple.com> wrote:
>>> On 2012-08-09, at 03:14, Peter Beverloo <peter at chromium.org> wrote:
>>> On Thu, Aug 9, 2012 at 11:09 AM, Mark Rowe <mrowe at apple.com> wrote:
>>>> On 2012-08-09, at 02:41, Osztrogonac Csaba <oszi at inf.u-szeged.hu>
>>>> > Hi,
>>>> > bugs.webkit.org and trac.webkit.org is unavailable again. :(
>>>> > Could you check it, please?
>>>> This is caused by a problem on a host that I don't have sufficient
>>>> privileges on to be able to address the issue myself. I've pinged people
>>>> that should be able to resolve the issue, but given that it's currently 3am
>>>> in California it may be a few hours before they're awake and fixing it.
>>> Thank you. Is there any way an on-call or monitoring system could be set
>>> up? While it fortunately occurs much less frequently nowadays than it did
>>> earlier in the year, it --please excuse my directness-- is unacceptable for
>>> a project the size of WebKit to have critical infrastructure unavailable
>>> like this for several hours. Even though it's 3am in California, there are
>>> many contributors in Asia and Europe who are severely impacted by this.
>>> We have people online virtually 24x7 that are capable of investigating
>>> and addressing issues with the webkit.org infrastructure. I'm one such
>>> person. This particular case is an unfortunate combination of events: a
>>> configuration error on a subset of the new hardware that webkit.org was
>>> recently migrated to has unintentionally limited the number of people that
>>> can access the host that is currently experiencing problems, and the person
>>> that such issues are escalated to is currently on vacation. It's an
>>> unfortunate combination, but also one that is unlikely to repeat.
>>> One thing we should look in to is improving the process for reporting
>>> issues with webkit.org infrastructure. webkit-dev isn't an ideal way to
>>> report issues that our monitoring system hasn't noticed as there's no
>>> separation between the regular discussion and more urgent issues, so the
>>> emails can be overlooked.
>> I see. Thank you for the insight, and I hope the access issues get sorted
>> out. I presume this is something Bill or Lucas will be able to pick up?
>> Hopefully the remaining downtime won't be more than three or four hours,
>> Bill is the one that's on vacation, and Lucas is in the same boat that I
>> am as far as access to the host in question. I managed to track down
>> someone else with sufficient access though, and they've fixed the issue
>> that was impacting bugs.webkit.org and trac.webkit.org.
> Awesome, cheers!
> - Mark
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev