1186478 - http://jenkins1.qa.scl3.mozilla.com/view/UI/ returns a white page

Status: RESOLVED FIXED

(Infrastructure & Operations :: MOC: Problems, task)

Description

[Johan Lorenzo [:jlorenzo]]

The IP can be ping, the server reponds but returns a white page.

Comment 1

[:Atoll]

:jlorenzo, could you run 'curl -v URL' and post the entire result here? It either does, or doesn't, include the Jetty/Jenkins HTTP headers, and that'll help clarify where the issue lies.

MOC, can you help us get this bug to the right team? QA Jenkins is to the best of my knowledge neither Systems nor Webops, so I'm not sure where to send this.

Comment 2

[:Eli Perelman]

~ curl -v http://jenkins1.qa.scl3.mozilla.com/
* Hostname was NOT found in DNS cache
*   Trying 10.22.73.155...
* Connected to jenkins1.qa.scl3.mozilla.com (10.22.73.155) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.37.1
> Host: jenkins1.qa.scl3.mozilla.com
> Accept: */*
>
< HTTP/1.1 500 Server Error
< Date: Wed, 22 Jul 2015 16:44:16 GMT
* Server Jetty(winstone-2.8) is not blacklisted
< Server: Jetty(winstone-2.8)
< X-Content-Type-Options: nosniff
< X-Frame-Options: sameorigin
< X-Frame-Options: sameorigin
< Expires: 0
< Cache-Control: no-cache,no-store,must-revalidate
< X-Hudson-Theme: default
< Content-Type: text/html;charset=UTF-8
< X-Hudson: 1.395
< X-Jenkins: 1.596.2
< X-Jenkins-Session: f26ac4c5
< X-Hudson-CLI-Port: 44898
< X-Jenkins-CLI-Port: 44898
< X-Jenkins-CLI2-Port: 44898
< X-Frame-Options: sameorigin
< Content-Length: 13
< Set-Cookie: JSESSIONID.b8b55bc5=12bhniuxtj3we1rptkkwqj2z9n;Path=/;HttpOnly
< Connection: close
<





* Closing connection 0
    %

Comment 3

[:Atoll]

Yeah, the X-Hudson and X-Jenkins headers there indicate that Jenkins itself is, at least, serving the HTTP response - so something is configured wrong or broken within Jenkins.

Comment 4

[Vinh Hua [:vinh]]

(In reply to Richard Soderberg [:atoll] from comment #1)
> :jlorenzo, could you run 'curl -v URL' and post the entire result here? It
> either does, or doesn't, include the Jetty/Jenkins HTTP headers, and that'll
> help clarify where the issue lies.
> 
> MOC, can you help us get this bug to the right team? QA Jenkins is to the
> best of my knowledge neither Systems nor Webops, so I'm not sure where to
> send this.


:davehunt - do you know what component this bug should be in?

Comment 5

[Johan Lorenzo [:jlorenzo]]

Fixed by a reboot of Jenkins, thanks to ashish. The error he found was:
> Caused by: java.lang.OutOfMemoryError: PermGen space

Comment 6

[:Atoll]

Note that the Internet seems to think that Jenkins has some sort of memory leak with classloaders and custom classes, so this may require a semi-regular restart. Consider updating Jenkins if it isn't a recent release, on the chance that they've fixed it.