When I currently visit the site it says:

"uWSGI Error

Python application not found"

The logfile says:

Python version: 2.7.3 (default, May 18 2012, 14:51:16)  [GCC 4.4.6
20110731 (Red Hat 4.4.6-3)]
*** Python threads support is disabled. You can enable it with
--enable-threads ***
Python main interpreter initialized at 0x219d360
your server socket listen backlog is limited to 100 connections
*** Operational MODE: async ***
added /home/alectaylor/web2py/ to pythonpath.
Traceback (most recent call last):
  File "/home/alectaylor/web2py/wsgihandler.py", line 33, in <module>
    import gluon.main
  File "/home/alectaylor/web2py/gluon/__init__.py", line 15, in <module>
    from globals import current
  File "/home/alectaylor/web2py/gluon/globals.py", line 17, in <module>
    from storage import Storage, List
  File "/home/alectaylor/web2py/gluon/storage.py", line 15, in <module>
    import cPickle
ImportError: PyCapsule_Import could not import module "cStringIO"
unable to load app 0 (mountpoint='') (callable not found or import error)
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 1809)
spawned uWSGI worker 1 (pid: 1810, cores: 24)


On Sat, Jul 21, 2012 at 7:56 PM, Massimo Di Pierro
<massimo.dipie...@gmail.com> wrote:
> What is the main issue in your opinion? Did you try running a simple wsgi
> program without web2py?
>
>
> On Saturday, 21 July 2012 04:43:35 UTC-5, Alec Taylor wrote:
>>
>> I actually never got it to work on WebFaction...
>>
>> I might try every week or so and spend 30 minutes on it, but frankly I
>> don't have the time.
>>
>> Also, heroku and openshift are giving me issues with web2py, but it's
>> something before I throw web2py on it, which is why I haven't posted
>> on this mailing-list about it >.<
>>
>> Lets just say I'm thoroughly annoyed I haven't been able to get web2py
>> hosted and working live
>>
>> On Sat, Jul 21, 2012 at 7:15 PM, Neil <yager.n...@gmail.com> wrote:
>> > Figured it out: I removed the "--limit-as 64" argument and now it seems
>> > to
>> > work. I'm using uwsgi version 1.2.4. Could this cause any problems?
>> >
>> > Now, if I can get my static content served directly, I'm ready to roll
>> > with
>> > Webfaction. Previously, when using nginx+uwsgi, it was using 1-10MB of
>> > memory with every page view! I still don't really understand why this
>> > was
>> > not being released with that configuration. With the "--reload-on-rss"
>> > flag
>> > set, the uwsgi processes were being restarted every few minutes, and
>> > that
>> > was just with one person viewing the site (me)!
>> >
>> >
>> > On Saturday, July 21, 2012 9:33:56 AM UTC+1, Neil wrote:
>> >>
>> >> I'm following these instructions, and get stuck at the same point:
>> >>
>> >> initializing 24 uGreen threads with stack size of 262144 (256 KB)
>> >> mprotect(): Invalid argument [plugins/ugreen/ugreen.c line 109]
>> >>
>> >> How did you fix this?
>> >>
>> >> On Thursday, July 5, 2012 4:17:48 PM UTC+1, Alec Taylor wrote:
>> >>>
>> >>> Alright, fixed that last error,
>> >>
>> >>
>> >>
>> >
>> > --
>> >
>> >
>> >
>
> --
>
>
>

-- 



Reply via email to