Description of problem: When trying to submit a bugreport via abrt the following message shows up and no bugreport is created: " XML-RPC Fault(-509): Unable to make sense of XML-RPC response from server. XML-RPC response too large. Our limit is 524288 characters. We got 733402 characters. Use XMLRPC_TRACE_XML to see for yourself " Where can I find XMLRPC_TRACE_XML? Version-Release number of selected component (if applicable): abrt-1.1.14-1.fc13.x86_64 How reproducible: with the particular bugreport: always (it didn't submit it successfully)
XMLRPC_TRACE_XML is environment variable, just set it as $ export XMLRPC_TRACE_XML=1 and start daemon manually than you will be able to see more information $ service abrtd stop $ abrtd -dvvv
OK. During the reporting process when it checks for duplicate reports it realizes that that bug was already reported [663184]. Then it makes the following XML-RPC CALL: <?xml version="1.0" encoding="UTF-8"?>\r\n <methodCall>\r\n <methodName>bugzilla.getBug</methodName>\r\n <params>\r\n <param><value><string>663184</string></value></param>\r\n </params>\r\n </methodCall>\r\n result: 663184 duplicate of 543165 next XML-RPC CALL: <?xml version="1.0" encoding="UTF-8"?>\r\n <methodCall>\r\n <methodName>bugzilla.getBug</methodName>\r\n <params>\r\n <param><value><string>543165</string></value></param>\r\n </params>\r\n </methodCall>\r\n and apparently the response to this call is to big as there are quiet a few entries there: https://bugzilla.redhat.com/show_bug.cgi?id=543165 abrtd: XML-RPC Fault(-509): Unable to make sense of XML-RPC response from server. XML-RPC response too large. Our limit is 524288 characters. We got 733402 characters. Use XMLRPC_TRACE_XML to see for yourself abrtd: Warning(':1.296'): XML-RPC Fault(-509): Unable to make sense of XML-RPC response from server. XML-RPC response too large. Our limit is 524288 characters. We got 733402 characters. Use XMLRPC_TRACE_XML to see for yourself Is this limit (524288 characters) specified in a config file somewhere? grep 524288 abrt.conf didn't show something.
this limitation comes from xmlrpc-c or bugzilla. Firstly I will reassign it to xmlrpc-c. Feel free to reassign back to abrt bug if its not in xmlrpc.
limit is in xmlrpc-c and can/must be increased by a call to | xmlrpc_limit_set(XMLRPC_XML_SIZE_LIMIT_ID, <new-limit>) see (xmlrpc-c/base.h).
Enrico thanks for you quick reply. Christoph could you try this build if it helps? http://koji.fedoraproject.org/koji/taskinfo?taskID=2700827
rpm -qa abrt\* abrt-libs-1.1.14-1.fc13.x86_64 abrt-addon-python-1.1.14-1.fc13.x86_64 abrt-plugin-runapp-1.1.14-1.fc13.x86_64 abrt-gui-1.1.14-1.fc13.x86_64 abrt-desktop-1.1.14-1.fc13.x86_64 abrt-plugin-bugzilla-1.1.14-1.fc13.x86_64 abrt-plugin-logger-1.1.14-1.fc13.x86_64 abrt-1.1.14-1.fc13.x86_64 abrt-addon-kerneloops-1.1.14-1.fc13.x86_64 abrt-addon-ccpp-1.1.14-1.fc13.x86_64 # ls -1 abrt-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-addon-ccpp-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-addon-kerneloops-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-addon-python-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-desktop-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-gui-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-libs-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-plugin-bugzilla-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-plugin-logger-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm abrt-plugin-runapp-1.1.14-0.13.g2259.dirty.fc13.x86_64.rpm # rpm -U * package abrt-libs-1.1.14-1.fc13.x86_64 (which is newer than abrt-libs-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-1.1.14-1.fc13.x86_64 (which is newer than abrt-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-addon-ccpp-1.1.14-1.fc13.x86_64 (which is newer than abrt-addon-ccpp-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-addon-kerneloops-1.1.14-1.fc13.x86_64 (which is newer than abrt-addon-kerneloops-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-addon-python-1.1.14-1.fc13.x86_64 (which is newer than abrt-addon-python-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-gui-1.1.14-1.fc13.x86_64 (which is newer than abrt-gui-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-plugin-bugzilla-1.1.14-1.fc13.x86_64 (which is newer than abrt-plugin-bugzilla-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-plugin-logger-1.1.14-1.fc13.x86_64 (which is newer than abrt-plugin-logger-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-plugin-runapp-1.1.14-1.fc13.x86_64 (which is newer than abrt-plugin-runapp-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed package abrt-desktop-1.1.14-1.fc13.x86_64 (which is newer than abrt-desktop-1.1.14-0.13.g2259.dirty.fc13.x86_64) is already installed Do I have to remove the current abrt installation first?
yes please, I've used bad numbering :-/
With your build the error didn't arise and an entry was successfully submitted to rhbz. Thanks!
your welcome, fix will be in next release
abrt-1.1.17-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/abrt-1.1.17-1.fc14
abrt-1.1.17-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/abrt-1.1.17-1.fc14
abrt-1.1.17-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.