1123658 - developer.allizom.org is down

Status: VERIFIED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)

Description

[Sebastian Zartner [:sebo]]

Accessing https://developer.allizom.org/ only displays this:

Service Unavailable

The service is temporarily unavailable. Please try again later.

Comment 1

[Eric Shepherd [:sheppy]]

Reassigned to the dev team, since this may be something they need to poke at before ops restarts anything.

Comment 2

[C. Liang [:cyliang]]

I did a graceful restart of Apache on the staging server.  It looks like we hit the MaxClients limit:

   [Mon Jan 19 02:18:16 2015] [error] server reached MaxClients setting, consider raising the MaxClients setting

Comment 3

[Sebastian Zartner [:sebo]]

It's working again now. Thanks!

Would be interesting to know what caused the MaxClients to be reached to avoid this problem in the future.
As the site was not reachable for several days, I assume there were some hanging requests.

Sebastian

Comment 4

[Sebastian Zartner [:sebo]]

Today the server is down again...

Sebastian

Comment 5

[C. Liang [:cyliang]]

Bugzilla@Mozilla 		

    [e-mail]

	

    Home
    New
    Browse
    Search

    [help]
    Reports
    My Dashboard
    Product Dashboard

Mid-air collision detected!

Someone else has made changes to bug 1123658 at the same time you were trying to. The changes made were:

Who 	When 	What 	Removed 	Added
[e-mail] 	2015-01-21 07:20:07 PST 	Whiteboard 	[kanban:https://webops.kanbanize.com/ctrl_board/2/299] 	

Your comment was:

    The main server behind developer.allizom.org is currently downed for a planned P2V migration.  (Please see bug 1078878.)  Email about this was sent out to the mdn-dev mailing list last week (January 14th).   Once the P2V work is done and the new VM is brought up, the developer.allizom.org should work again.
      

You have the following choices:

This will cause all of the above changes to be overwritten.

    Throw away my changes, and revisit bug 1123658

        Home
        New
        Browse
        Search
        Reports
        My Dashboard
        Product Dashboard
        My Bugs
        ACLs (requested by me)
        Any (requested by me)
        CCed to me, open
        Labs all
        LabsOps open
        MOC: Any ES
        MOC: Any Rabbit
        MOC: ES SCL3
        Mozilla Metrics Operations (Assigned to Me)
        Mozilla Metrics Operations NEW
        Open (requested by me)
        Post move ACLs
        test
        WebOps: IT-Managed Tools NEW
        WebOps: Misc
        WebOps: Product Delivery
        WebOps: SSL
        WebOps: SSL/DNS
        Wiki Working Group

        All MOC Incidents (Past 24 Hours)
        CAB ‑ All
        CAB ‑ Approved
        CAB ‑ Pending
        CAB ‑ Pending
        Open MOC Incidents
        p2v Closed
        p2v Open
        Spring Cleaning Closed
        Spring Cleaning Open
        SRE Docs needs‑review
        Triage‑unassigned
        winners‑delegate

Privacy Policy

Comment 6

[C. Liang [:cyliang]]

Gah.  Firefox, sometimes I hate you when you are being laggy.


    The main server behind developer.allizom.org is currently downed for a planned P2V migration.  (Please see bug 1078878.)  Email about this was sent out to the mdn-dev mailing list last week (January 14th).   Once the P2V work is done and the new VM is brought up, the developer.allizom.org should work again.

Comment 7

[Sebastian Zartner [:sebo]]

(In reply to C. Liang [:cyliang] from comment #6)
> The main server behind developer.allizom.org is currently downed for a
> planned P2V migration.  (Please see bug 1078878.)  Email about this was sent
> out to the mdn-dev mailing list last week (January 14th).   Once the P2V
> work is done and the new VM is brought up, the developer.allizom.org should
> work again.

Sorry for bothering you. Looks like I just missed that mail.

Sebastian