What steps will reproduce the problem?
1. Pyrit client returns errors when "list_cores" command is executed on head
node.
2.
3.
What is the expected output? What do you see instead?
Serving 0 active clients; 0 PMKs/s; 0.0 TTS Traceback (most recent call last):
File "/usr/local/bin/pyrit", line 6, in <module>
pyrit_cli.Pyrit_CLI().initFromArgv()
File "/usr/local/lib/python2.6/dist-packages/pyrit_cli.py", line 115, in initFromArgv
func(self, **options)
File "/usr/local/lib/python2.6/dist-packages/pyrit_cli.py", line 877, in serve
server.addClient(addr)
File "/usr/local/lib/python2.6/dist-packages/cpyrit/network.py", line 140, in addClient
client = NetworkClient(srv_addr, self.enqueue, known_uuids)
File "/usr/local/lib/python2.6/dist-packages/cpyrit/network.py", line 68, in __init__
self.srv_uuid, self.uuid = self.server.register(";".join(known_uuids))
File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib/python2.6/xmlrpclib.py", line 1237, in request
errcode, errmsg, headers = h.getreply()
File "/usr/lib/python2.6/httplib.py", line 1048, in getreply
response = self._conn.getresponse()
File "/usr/lib/python2.6/httplib.py", line 974, in getresponse
response.begin()
File "/usr/lib/python2.6/httplib.py", line 391, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.6/httplib.py", line 349, in _read_status
line = self.fp.readline()
File "/usr/lib/python2.6/socket.py", line 397, in readline
data = recv(1)
socket.error: [Errno 104] Connection reset by peer
What version of the product are you using? On what operating system?
Pyrit 0.4.0 Read Only
Please provide any additional information below.
cpus are non sse2, PIII cpus
Master Node- Linux udontneedtoknow.com 2.6.31-22-generic-pae #70-Ubuntu SMP
Thu Dec 2 00:54:52 UTC 2010 i686 GNU/Linux
Slave Node - Linux PowerEdge6300 2.6.31-22-generic-pae #70-Ubuntu SMP Thu Dec 2
00:54:52 UTC 2010 i686 GNU/Linux
Original issue reported on code.google.com by thefixe...@gmail.com on 2 Feb 2011 at 10:05
Original issue reported on code.google.com by
thefixe...@gmail.com
on 2 Feb 2011 at 10:05