bodhi log analysis
Mike McGrath
mmcgrath at redhat.com
Thu Nov 5 15:25:49 UTC 2009
On Thu, 5 Nov 2009, Luke Macken wrote:
> Hey all,
>
> So I wrote a little script this morning to analyze all of bodhi's logs across
> app1-7. The results were quite interesting. Below are some of the top
> offenders, in the format of (# of tracebacks : exception)
>
> # Database issues
> 134 : InterfaceError: connection already closed
> 1773 : OperationalError: terminating connection due to administrator command server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
> 2566 : OperationalError: FATAL: connection limit exceeded for non-superusers
>
> # FAS issues
> 115 : error: 35
> 126 : error: 52
> 236 : error: 6
> 1155 : ServerError: ServerError(https://admin.fedoraproject.org/accounts/, 500, Unknown HTTP Server Response)
> 1320 : error: 7
> 2758 : ServerError: ServerError(https://admin.fedoraproject.org/accounts/, 503, Unknown HTTP Server Response)
> 3539 : error: 18
> 5399 : ServerError: ServerError(https://admin.fedoraproject.org/accounts/, 502, Unknown HTTP Server Response)
>
> The "error: #" messages are from pycurl within the TurboGears JSONFas
> identity/visit layer. PyCurl error descriptions can be found here:
> http://curl.haxx.se/libcurl/c/libcurl-errors.html
>
out of how many total requests did we see these errors?
-Mike
More information about the Fedora-infrastructure-list
mailing list