Ticket #416 (closed defect: fixed)

Opened 16 years ago

Last modified 16 years ago

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 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
  File "<string>", line 1, in <lambda>
  File "/usr/lib/python2.4/site-packages/Bcfg2/Client/", line 130, in run_method
    ret = apply(method, self._authinfo + methodArgs)
  File "/usr/lib64/python2.4/", line 1096, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.4/", line 1383, in __request
  File "/usr/lib64/python2.4/", line 1147, in request
    return self._parse_response(h.getfile(), sock)
  File "/usr/lib64/python2.4/", line 1286, in _parse_response
    return u.close()
  File "/usr/lib64/python2.4/", 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 called function RecvProbeData with wrong argument count
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/Bcfg2/Server/", line 162, in _cobalt_marshalled_dispatch
    response = self._dispatch(method, (address, ) + params)
  File "/usr/lib/python2.4/", 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


bcfg2-server.diff (683 bytes) - added by desai 16 years ago.

Change History

comment:1 Changed 16 years ago by desai

  • Status changed from new to assigned
  • Description modified (diff)

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.

Changed 16 years ago by desai

comment:2 Changed 16 years ago by desai

  • Status changed from assigned to closed
  • Resolution set to fixed

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.