What steps will reproduce the problem?
1. Node is experiencing failure and errors connecting to remove db
2. All other nodes are processing just fine besides this host.
3.
What is the expected output? What do you see instead?
root@osiris:~# pyrit batch
Connecting to storage at 'mysql://127.0.0.1/pyrit'... connected.
Working on ESSID 'default'
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 803, in batchprocess
for results in dbiterator:
File "/usr/local/lib/python2.6/dist-packages/cpyrit/cpyrit.py", line 787, in next
solvedResults
File "/usr/local/lib/python2.6/dist-packages/cpyrit/storage.py", line 1068, in __setitem__
session.add(PYR2_DBObject(essid_obj, key, results))
File "<string>", line 4, in __init__
File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/state.py", line 82, in initialize_instance
return manager.events.original_init(*mixed[1:], **kwargs)
File "/usr/local/lib/python2.6/dist-packages/cpyrit/storage.py", line 937, in __init__
self.key = key
File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 150, in __set__
self.impl.set(instance_state(instance), instance_dict(instance), value, None)
File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 448, in set
state.modified_event(dict_, self, False, old)
File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/state.py", line 279, in modified_event
if not self._strong_obj:
TypeError: an integer is required
What version of the product are you using? On what operating system?
Pyrit 0.4.1-dev (svn r298)
Linux LameBox 2.6.31-22-generic-pae #73-Ubuntu SMP Fri Feb 11 18:39:01 UTC 2011
i686 GNU/Linux
Please provide any additional information below.
I edited 127.0.0.1 for privacy sake, not posting my public ip,
Original issue reported on code.google.com by thefixe...@gmail.com on 12 Mar 2011 at 8:01
Original issue reported on code.google.com by
thefixe...@gmail.com
on 12 Mar 2011 at 8:01