[Twisted-Python] How can LoopCall not be defined?

[L. Daniel Burr]

Hi Stephan,


On Thu, 08 Sep 2011 00:51:13 -0500, Stephan <schenette at gmail.com> wrote:

> I'm running a server with about 20 client connections going to it
> right now and monitoring the error log eventually I see LoopCall is
> not defined.
> how can that be? Thanks in advance.
>
>
> 2011-09-07 22:47:26-0700 [-] Unhandled Error
> 	Traceback (most recent call last):
> 	  File "/usr/lib/python2.6/dist-packages/twisted/application/app.py",
> line 445, in startReactor
> 	    self.config, oldstdout, oldstderr, self.profiler, reactor)
> 	  File "/usr/lib/python2.6/dist-packages/twisted/application/app.py",
> line 348, in runReactorWithLogging
> 	    reactor.run()
> 	  File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py",
> line 1170, in run
> 	    self.mainLoop()
> 	  File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py",
> line 1179, in mainLoop
> 	    self.runUntilCurrent()
> 	--- <exception caught here> ---
> 	  File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py",
> line 778, in runUntilCurrent
> 	    call.func(*call.args, **call.kw)
> 	  File "/usr/sbin/firefoxprocess.py", line 48, in onTimer
> 	    self.firesharkProtocol.handleProcessTimedOut()
> 	  File "/usr/sbin/fireshark.py", line 32, in handleProcessTimedOut
> 	    self.dirtyExit();
> 	  File "/usr/sbin/fireshark.py", line 68, in dirtyExit
> 	    self.checkIfFirefoxWasKilledLoop =  
> LoopCall(self.checkIfFirefoxWasKilled)
> 	exceptions.NameError: global name 'LoopCall' is not defined

Are you talking about task.LoopingCall, or is LoopCall something define in  
your own code?

L. Daniel Burr