Modify ↓
Ticket #416 (closed defect: fixed)
0.9.3pre3 fails with "wrong argument count"
Reported by: | [email protected]… | Owned by: | desai |
---|---|---|---|
Priority: | major | Milestone: | Bcfg2 0.9.3 Release |
Component: | bcfg2-client | Version: | |
Keywords: | Cc: |
Description (last modified by desai) (diff)
Trying to upgrade from 0.8.7.2 to 0.9.3pre3 we get the following error.
In the client we see:
[[email protected] gilham]# /usr/sbin/bcfg2 -v Failed to upload probe data Traceback (most recent call last): File "/usr/sbin/bcfg2", line 177, in run proxy.RecvProbeData(Bcfg2.Client.XML.tostring(probedata)) File "<string>", line 1, in <lambda> File "/usr/lib/python2.4/site-packages/Bcfg2/Client/Proxy.py", line 130, in run_method ret = apply(method, self._authinfo + methodArgs) File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib64/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib64/python2.4/xmlrpclib.py", line 1286, in _parse_response return u.close() File "/usr/lib64/python2.4/xmlrpclib.py", line 744, in close raise Fault(**self._stack[0]) Fault: <Fault 4: 'not all arguments converted during string formatting'>
In the server we see:
Client 10.1.1.1 called function RecvProbeData with wrong argument count Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Component.py", line 162, in _cobalt_marshalled_dispatch response = self._dispatch(method, (address, ) + params) File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "/usr/sbin/bcfg2-server", line 167, in Bcfg2RecvProbeData self.logger.error("Failed to process probe data from client %s" % (address), exc_info=1) TypeError: not all arguments converted during string formatting
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
I think that the attached patch should fix this. Can you verify that a different error message occurs after it is applied? The root issue is that the server is having trouble processing some of the probe data upload.