Closed johnnykv closed 11 years ago
There seems to be a bug in the feedpuller. If a communication error occurs at the "correct" moment it will kill the feedpuller greenlet completly.
2013-02-21 12:47:56,303 (root) Mongo collection count: url: 192001, hpfeed: 7552164 (635 in error state), session: 7535125, dork: 868, file: 11616, Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/gevent/greenlet.py", line 390, in run result = self._run(*self.args, **self.kwargs) File "/home/johnny/mnemosyne/hpfeeds/feedpuller.py", line 58, in start_listening self.hpc.run(on_message, on_error) File "/home/johnny/mnemosyne/hpfeeds/hpfeeds.py", line 134, in run d = self.s.recv(BUFSIZ) File "/usr/lib/python2.7/dist-packages/gevent/socket.py", line 423, in recv return sock.recv(*args) error: [Errno 104] Connection reset by peer <Greenlet at 0x1498910: <bound method FeedPuller.start_listening of <hpfeeds.feedpuller.FeedPuller instance at 0x14f02d8>>> failed with error 2013-02-21 13:18:46,056 (root) Mongo collection count: url: 192006, hpfeed: 7552696 (635 in error state), session: 7535656, dork: 868, file: 11616, 2013-02-21 13:49:36,255 (root) Mongo collection count: url: 192006, hpfeed: 7552696 (635 in error state), session: 7535656, dork: 868, file: 11616,
There seems to be a bug in the feedpuller. If a communication error occurs at the "correct" moment it will kill the feedpuller greenlet completly.