Custom Query (894 matches)
Results (34 - 36 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#563 | desai | [email protected]… | fixed | Confusing message from dns error |
Description |
I've got an error from the bcfg2 client regarding an error that people did have here and reproducing it give out this error against trunk. This error was reproduced by putting an different hostname in the A-record of the dns server or putting a double entry in the dns server. [email protected]:~# bcfg2 -kevq no server x509 fingerprint; no server verification performed! Unknown failure Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/Bcfg2/Proxy.py", line 27, in __call__ return _Method.__call__(self, *args) File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.4/xmlrpclib.py", line 1286, in _parse_response return u.close() File "/usr/lib/python2.4/xmlrpclib.py", line 744, in close raise Fault(**self._stack[0]) Fault: <Fault 6: 'Client metadata resolution error for 10.145.3.26'> Failed to download probes from bcfg2 Server Failure This error is a bit confusing, so i suggest that we put a notice to look to the syslog of the server so that the user can see the other error attached to it. I've made a little patch suggesting solution to the user so he can resolved the error. |
|||
#575 | desai | [email protected]… | fixed | Bcfg2 should prevent concurent update of config |
Description |
Bcfg2 client has no mechanism to prevent 2 client doing an update at the same time. Or to prevent use of client when agent is doing an update of the config. |
|||
#576 | desai | [email protected]… | fixed | 2 group of same category should give an alert, only the last is taken |
Description |
If you build up a profile with some groups that are catogarized, if the same category show up more than one time, only the last category/Group is considered and the other is lost. An alert should show up about this issue because the sysadmin would not realize his error much too late. An alert should show up in the log and an alert should be in the statistics. |