Modify ↓
Ticket #563 (closed enhancement: fixed)
Confusing message from dns error
Reported by: | [email protected]… | Owned by: | desai |
---|---|---|---|
Priority: | minor | Milestone: | Bcfg2 0.9.6 Release |
Component: | bcfg2-server | Version: | 0.9.x |
Keywords: | dns error confusing message | Cc: |
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.
Attachments
Change History
Changed 15 years ago by [email protected]…
- Attachment bcfg-error-msg.diff added
comment:1 Changed 15 years ago by desai
- Status changed from new to closed
- Resolution set to fixed
- Milestone set to Bcfg2 0.9.6 Release
I've improved the error message on the server side, and cleaned up the client-side error handling. This is fixed in [93baa718c3182f3b2b59280ac141e71a4a75b29c] (SVN r4693)
Note: See
TracTickets for help on using
tickets.
Patch clarifying the error and possible working solution