Robin Atwood wrote:
> Whenever denyhosts tries to sync I now get the following messages:
>
> Apr 29 18:50:01 sync : ERROR <Fault 1:
> "exceptions.KeyError:'timestamp'">
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/site-packages/DenyHosts/sync.py", line 117, in
> receive_new_hosts
> self.__prefs.get("SYNC_DOWNLOAD_RESILIENCY"))
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
> return self.__send(self.__name, args)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
> verbose=self.__verbose
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1253, in request
> return self._parse_response(h.getfile(), sock)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1392, in _parse_response
> return u.close()
> File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close
> raise Fault(**self._stack[0])
> Fault: <Fault 1: "exceptions.KeyError:'timestamp'">
>
> Recently I changed the log formatting via:
>
> Apr 29 17:49:53 prefs : INFO DAEMON_LOG_MESSAGE_FORMAT:
> [%(asctime)s %(name)-12s: %(levelname)-8s %(message)s]
> Apr 29 17:49:53 prefs : INFO DAEMON_LOG_TIME_FORMAT: [%b %d %H:
> %M:%S]
>
> which may be relevant since there is a reference to timestamps in the message.
Not relevant.
The error above means the sync server has a very different timestamp
compared with your server, probably in the past. Its not on your side
since I just checked and my server is showing the same error.
This has happened before, at least once this year, and it really means
that somebody is either servicing the sync server or perhaps it has
changed to a different server which is not completely configured.
--
René Berber
------------------------------------------------------------------------------
_______________________________________________
Denyhosts-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/denyhosts-user
