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.
I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs?
Adrian
On 24 March 2015 at 01:31, Adrian Reber adrian@lisas.de wrote:
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.
I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs?
Oh crap I didn't see this til now. Did anyone help you on this? If not can we work on this tomorrow (Thursday?)
Adrian
infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
On Wed, Mar 25, 2015 at 07:29:24PM -0600, Stephen John Smoogen wrote:
On 24 March 2015 at 01:31, Adrian Reber adrian@lisas.de wrote:
> > The xml-rpc interface does not work right now. I get > > > > Error checking in.A Connection closed before checkin complete.A 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. I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs?
Oh crap I didn't see this til now. Did anyone help you on this? If not can we work on this tomorrow (Thursday?)
I have not. Btw Adrian, I've been meaning to ask, did you try running MM2 (more precisely the tried to test xmlrpc endpoint) locally?
Pierre
On Thu, Mar 26, 2015 at 08:51:38AM +0100, Pierre-Yves Chibon wrote:
On Wed, Mar 25, 2015 at 07:29:24PM -0600, Stephen John Smoogen wrote:
On 24 March 2015 at 01:31, Adrian Reber adrian@lisas.de wrote:
> > The xml-rpc interface does not work right now. I get > > > > Error checking in.A Connection closed before checkin complete.A 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. I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs?
Oh crap I didn't see this til now. Did anyone help you on this? If not can we work on this tomorrow (Thursday?)
I have not. Btw Adrian, I've been meaning to ask, did you try running MM2 (more precisely the tried to test xmlrpc endpoint) locally?
I have found the problems with the xmlrpc endpoint by changing the report_mirror client to print out a stack trace. This told me where the errors in report_mirror were. Right now I am preparing the pull request for review and then report_mirror should work again.
Adrian
infrastructure@lists.fedoraproject.org