|Summary:||XML-RPC(-509): Unable to make sense of XML-RPC response from server.|
|Product:||[Fedora] Fedora||Reporter:||Mikhail Veltishchev <m.velt>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||16||CC:||abrt-devel-list, brentrbrian, dvlasenk, iprikryl, jmoskovc, johannes.postler, kklic, mmilata, mtoman, npajkovs|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-01-12 01:14:53 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Mikhail Veltishchev 2012-04-20 09:54:03 UTC
Description of problem: Cannot submit particular bug report. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Try to submit it via RH Bugzilla 2. Got the error Actual results: Cannot submit crash report Expected results: Report should be submitted successfully. Additional info: --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates fatal: XML-RPC(-509): Unable to make sense of XML-RPC response from server. XML-RPC response too large. Our limit is 1048576 characters. We got 1048780 characters. Use XMLRPC_TRACE_XML to see for yourself (exited with 1)
Comment 1 Mikhail Veltishchev 2012-04-20 09:55:40 UTC
Seems this bug is very similar to #666893.
Comment 2 Nikola Pajkovsky 2012-04-20 10:15:02 UTC
commit 29fc07758fa0aaef5f066091faee56280cf7500e Author: Nikola Pajkovsky <firstname.lastname@example.org> Date: Fri Apr 20 12:13:58 2012 +0200 xmlrpc: rising XMLRPC_XML_SIZE_LIMIT_DEFAULT up to 4 times Signed-off-by: Nikola Pajkovsky <email@example.com>
Comment 3 Johannes Postler 2012-04-28 15:44:37 UTC
I'm experiencing the bug too. Anything I can do to help?
Comment 4 Nikola Pajkovsky 2012-05-04 07:34:22 UTC
*** Bug 818784 has been marked as a duplicate of this bug. ***
Comment 5 Nikola Pajkovsky 2012-05-04 07:36:03 UTC
install nightly builds of btparser, libreport a abrt and test as much as it is possible ;)
Comment 6 Fedora Update System 2012-12-20 08:54:04 UTC
abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18
Comment 7 Fedora Update System 2012-12-20 09:44:38 UTC
abrt-2.0.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.20-1.fc17
Comment 8 Fedora Update System 2012-12-21 01:28:09 UTC
Package abrt-2.0.20-1.fc18, btparser-0.24-1.fc18, libreport-2.0.20-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.20-1.fc18 btparser-0.24-1.fc18 libreport-2.0.20-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20725/abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18 then log in and leave karma (feedback).
Comment 9 Fedora Update System 2013-01-12 01:14:55 UTC
abrt-2.0.20-1.fc18, btparser-0.24-1.fc18, libreport-2.0.20-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2013-02-26 02:36:58 UTC
abrt-2.0.20-1.fc17, btparser-0.24-1.fc17, libreport-2.0.20-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.