Can't start on local machine

79 views
Skip to first unread message

Christoph Lupprich

unread,
Feb 3, 2013, 12:55:16 PM2/3/13
to reque...@googlegroups.com
I would have loved to work on the UTF-8 internal server error bug today (I find the idea and service awesome and would have had a concrete usage scenario myself). Unfortunately, even after installing all dependencies, I wasn't able to get requestbin up and running on my local machine (OSX Mountain Lion). foreman correctly starts the web process but then it seems to hang. Sending a SIGTERM to the application reveals that the request is actually started to be processed, but Ginkgo seems to stop in some sleep command. Stack trace is attached. If someone has an idea how to get requestbin up and running locally, I can contribute some patches :)

18:54:48 web.1  | started with pid 61391
18:54:48 web.1  | running develop
18:54:48 web.1  | running egg_info
18:54:48 web.1  | writing requirements to requestbin.egg-info/requires.txt
18:54:48 web.1  | writing requestbin.egg-info/PKG-INFO
18:54:48 web.1  | writing top-level names to requestbin.egg-info/top_level.txt
18:54:48 web.1  | writing dependency_links to requestbin.egg-info/dependency_links.txt
18:54:48 web.1  | reading manifest file 'requestbin.egg-info/SOURCES.txt'
18:54:48 web.1  | writing manifest file 'requestbin.egg-info/SOURCES.txt'
18:54:48 web.1  | running build_ext
18:54:48 web.1  | Creating /usr/local/lib/python2.7/site-packages/requestbin.egg-link (link to .)
18:54:48 web.1  | requestbin 1.1.0 is already the active version in easy-install.pth
18:54:48 web.1  | 
18:54:48 web.1  | Installed /Users/kitto/Code/requestbin
18:54:48 web.1  | Processing dependencies for requestbin==1.1.0
18:54:48 web.1  | Searching for feedparser==5.1.3
18:54:48 web.1  | Best match: feedparser 5.1.3
18:54:48 web.1  | Processing feedparser-5.1.3-py2.7.egg
18:54:48 web.1  | feedparser 5.1.3 is already the active version in easy-install.pth
18:54:48 web.1  | 
18:54:48 web.1  | Using /usr/local/lib/python2.7/site-packages/feedparser-5.1.3-py2.7.egg
18:54:48 web.1  | Searching for Ginkgo==0.6.0dev
18:54:48 web.1  | Best match: Ginkgo 0.6.0dev
18:54:48 web.1  | Processing Ginkgo-0.6.0dev-py2.7.egg
18:54:48 web.1  | Ginkgo 0.6.0dev is already the active version in easy-install.pth
18:54:48 web.1  | Installing ginkgo script to /usr/local/share/python
18:54:48 web.1  | Installing ginkgoctl script to /usr/local/share/python
18:54:48 web.1  | 
18:54:48 web.1  | Using /usr/local/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg
18:54:48 web.1  | Finished processing dependencies for requestbin==1.1.0
^CSIGINT received
18:54:53 system | sending SIGTERM to all processes
18:54:53 web.1  | Starting process with ./config/heroku.conf.py...
18:54:53 web.1  | The ginkgo.async.threading manager should not be used in production environments due to the known limitations of the GIL
18:54:53 web.1  | The ginkgo.async.threading manager should not be used in production environments due to the known limitations of the GIL
18:54:53 web.1  | The ginkgo.async.threading manager should not be used in production environments due to the known limitations of the GIL
18:54:53 web.1  | The ginkgo.async.threading manager should not be used in production environments due to the known limitations of the GIL
18:54:53 web.1  | Traceback (most recent call last):
SIGTERM received
18:54:53 web.1  |   File "<string>", line 1, in <module>
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/runner.py", line 69, in run_ginkgo
18:54:53 web.1  |     ControlInterface().start(args.target, args.daemonize)
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/runner.py", line 181, in start
18:54:53 web.1  |     app.stop()
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/core.py", line 155, in stop
18:54:53 web.1  |     child.stop()
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/core.py", line 155, in stop
18:54:53 web.1  |     child.stop()
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/core.py", line 155, in stop
18:54:53 web.1  |     child.stop()
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/core.py", line 157, in stop
18:54:53 web.1  |     self.do_stop()
18:54:53 web.1  |   File "/usr/local/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/async/threading.py", line 67, in do_stop
18:54:53 web.1  |     t.join(self.stop_timeout)
18:54:53 web.1  |   File "/usr/local/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/async/threading.py", line 28, in join
18:54:53 web.1  |     return _spin_wait(super(Thread, self).join, timeout)
18:54:53 web.1  |   File "/usr/local/lib/python2.7/site-packages/Ginkgo-0.6.0dev-py2.7.egg/ginkgo/async/threading.py", line 14, in _spin_wait
18:54:53 web.1  |     if fn(timeout=1):
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/threading.py", line 674, in join
18:54:53 web.1  |     self.__block.wait(delay)
18:54:53 web.1  |   File "/usr/local/Cellar/python/2.7.3/lib/python2.7/threading.py", line 262, in wait
18:54:53 web.1  |     _sleep(delay)
18:54:53 web.1  | TypeError: stop() takes exactly 1 argument (3 given)
18:54:53 web.1  | terminated by SIGTERM

Jeff Lindsay

unread,
Mar 4, 2013, 10:57:15 AM3/4/13
to reque...@googlegroups.com
This is really odd. It could be because of updates to Ginkgo. I don't support that project anymore and it might have changed a little since it was taken over by others. It could be that the threading async manager is not up-to-date. You could dig into Ginkgo if you wanted, but otherwise it'll have to wait for me to look into it. 

Maybe submit a Github issue for this...


--
You received this message because you are subscribed to the Google Groups "requestbin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to requestbin+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Jeff Lindsay
http://progrium.com
Reply all
Reply to author
Forward
0 new messages