OOM killer on bapp02 again

[Pierre-Yves Chibon]

On Tue, Mar 17, 2015 at 10:52:24PM +0100, Adrian Reber wrote:
> On Mon, Mar 16, 2015 at 01:38:41PM +0100, Pierre-Yves Chibon wrote:
> > One point where you might be of great help is with testing the xml-rpc endpoint.
> > It should be 100% backward compatible (but I let you guess what the keyword is
> > in that sentence :)).
> 
> The xml-rpc interface does not work right now. I get
> 
> Error checking in.  Connection closed before checkin complete.  Please try again later.
> 
> There is no error in the error_log on mm-frontend01 and the access_log
> just says:
> 
> 10.5.126.88 - - [17/Mar/2015:21:51:13 +0000] "POST /mirrormanager2/xmlrpc HTTP/1.0" 200 326 "-" "xmlrpclib.py/1.0.1 (by www.pythonware.com)"
> 
> I don't know where to look for more error/debug messages.

Something we could do for quick testing is setting the application in debug mode
(this is only for testing and we should make sure to remove it afterward).

in the wsgi: /var/www/mirrormanager2.wsgi
set: application.debug = True
then restart apache.

This might give us more clue as to what's going on.


Thanks a lot for your help testing this :)

Pierre
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150318/f982a9c4/attachment.sig>