Take #2: "Issue 20: Exception caught"
Closed this issue · 7 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
And so...it returns :)
What is the expected output?
Normal log entries(?)
What do you see instead?
2014-03-21 12:41:37+0100 [honssh.server.HonsshServerFactory] Starting factory
<honssh.client.HonsshClientFactory instance at 0x1fcbd4d5998>
2014-03-21 12:41:37+0100 [HonsshServerTransport,218,193.17.184.197] Unhandled
Error
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/twisted/application/app.py", line 323, in runReactorWithLogging
reactor.run()
File "/usr/local/lib/python2.7/site-packages/twisted/internet/base.py", line 1169, in run
self.mainLoop()
File "/usr/local/lib/python2.7/site-packages/twisted/internet/base.py", line 1181, in mainLoop
self.doIteration(t)
File "/usr/local/lib/python2.7/site-packages/twisted/internet/pollreactor.py", line 167, in doPoll
log.callWithLogger(selectable, _drdw, selectable, fd, event)
--- <exception caught here> ---
File "/usr/local/lib/python2.7/site-packages/twisted/python/log.py", line 84, in callWithLogger
return callWithContext({"system": lp}, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/log.py", line 69, in callWithContext
return context.call({ILogContext: newCtx}, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
return func(*args,**kw)
File "/usr/local/lib/python2.7/site-packages/twisted/internet/posixbase.py", line 594, in _doReadOrWrite
self._disconnectSelectable(selectable, why, inRead)
File "/usr/local/lib/python2.7/site-packages/twisted/internet/posixbase.py", line 260, in _disconnectSelectable
selectable.readConnectionLost(f)
File "/usr/local/lib/python2.7/site-packages/twisted/internet/tcp.py", line 257, in readConnectionLost
self.connectionLost(reason)
File "/usr/local/lib/python2.7/site-packages/twisted/internet/tcp.py", line 277, in connectionLost
protocol.connectionLost(reason)
File "/HONEY/honssh/server.py", line 73, in connectionLost
self.client.loseConnection()
exceptions.AttributeError: HonsshServerTransport instance has no attribute 'client'
2014-03-21 12:41:37+0100 [Uninitialized] New client connection
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] kex alg, key alg:
diffie-hellman-group-exchange-sha1 ssh-rsa
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] outgoing: aes256-ctr
hmac-sha1 none
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] incoming: aes256-ctr
hmac-sha1 none
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] REVERSE
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] NEW KEYS
2014-03-21 12:41:37+0100 [HonsshClientTransport,client] Client Connection
Secured
2014-03-21 12:42:37+0100 [HonsshClientTransport,client] connection lost
2014-03-21 12:42:37+0100 [HonsshClientTransport,client] Stopping factory
<honssh.client.HonsshClientFactory instance at 0x1fcbd4d5998>
What version of the product are you using?
56dfab7e24f1
On what operating system?
OpenBSD 5.3/5.4 amd64
Please provide any additional information below
I have advanced logging enabled this time, but this incident did not generate
any logs at all.
The log snippet i included here is the only data i can provide you with - sorry.
Original issue reported on code.google.com by are.hans...@gmail.com on 21 Mar 2014 at 11:58
GoogleCodeExporter commented
Darn it :P Does HonSSH continue to run after it? Do you have the advanced log
of the connection that caused it by chance?
Original comment by tnn...@googlemail.com on 22 Mar 2014 at 4:10
- Changed state: Accepted
GoogleCodeExporter commented
Sorry man :P
Ye, it keeps running. I actually saw that issue multiple times yesterday.
The first issue did not generate any adv-logs, ill see if i can get some
adv-logs for you when i get back from work.
2014-03-22 17:10 GMT+01:00 <honssh@googlecode.com>:
Original comment by are.hans...@gmail.com on 22 Mar 2014 at 4:16
GoogleCodeExporter commented
From 2014-03-20 01:12:39+0100 to 2014-03-22 07:40:39+0100 there has been a
total of 13 log entries showing this exception.
Time of the events:
2014-03-22 07:40:39+0100
2014-03-21 22:54:50+0100
2014-03-21 22:54:50+0100
2014-03-21 12:41:37+0100
2014-03-21 14:37:37+0100
2014-03-21 19:04:00+0100
2014-03-21 21:54:43+0100
2014-03-21 22:23:06+0100
2014-03-21 22:23:06+0100
2014-03-20 01:12:26+0100
2014-03-20 01:12:26+0100
2014-03-20 01:12:39+0100
2014-03-20 01:12:39+0100
HonSSH has not been able to generate anything in the adv-logs (as far as i can
see) during these events.
This has occurred during attacks from six different IP addresses.
Hope you can make some sense out of that :)
Original comment by are.hans...@gmail.com on 22 Mar 2014 at 9:57
Attachments:
GoogleCodeExporter commented
Thanks man, I always find it fun to look through other peoples logs :D
If there's no ghost sessions and if HonSSH continues to run, I may just add
some error handling to avoid it.
Original comment by tnn...@googlemail.com on 24 Mar 2014 at 3:12
GoogleCodeExporter commented
Cool, sounds like a plan.
Hehe, if you like looking at logs I can send you +200mb :P
Original comment by are.hans...@gmail.com on 24 Mar 2014 at 5:14
GoogleCodeExporter commented
Original comment by tnn...@googlemail.com on 30 Mar 2014 at 10:16
- Changed state: Started
GoogleCodeExporter commented
Caused when the client part of HonSSH disconnected first - should be ok now.
Watch out for ghost sessions :P
Original comment by tnn...@googlemail.com on 30 Mar 2014 at 3:24
- Changed state: Fixed