Sorry, my mistake. I know that this is not a topic for this list, but I was
talking about virtualenvwrapper.
El 18/09/2013 03:41, "Łukasz Mierzwa" <[email protected]> escribió:

> What do you mean by "default path"? AFAIK there is no default path for
> virtualenv, you need to specify destination directory when creating
> virtualenv. Just create one that will be accessible by the user you want to
> run uWSGI workers as (www-data in your case).
>
>
> 2013/9/18 Oscar A. Mata T. <[email protected]>
>
>> How do I change virtualenv default path?
>> El 18/09/2013 01:27, "Łukasz Mierzwa" <[email protected]> escribió:
>>
>> www-data user (and any other user) has no access to /root directory
>>>
>>>
>>> 2013/9/17 Oscar A. Mata T. <[email protected]>
>>>
>>>> Hi there,
>>>>
>>>> I figured out why the issue is happening, I was running uwsgi as
>>>> www-data user, then in config file I put the same user access for
>>>> www-data, when I removed it the app start running with the virtualenv.
>>>> So this bring me to another question, which is the right way to run
>>>> apps with specific privileges, what is the problem with www-data user?
>>>> do I need to configure something additional with this user?
>>>>
>>>> Best regards,
>>>>
>>>> 2013/9/12 Roberto De Ioris <[email protected]>:
>>>> >
>>>> >> Sorry,
>>>> >>
>>>> >> I pasted the wrong log, this is the right:
>>>> >>
>>>> >> ----- LOG -----
>>>> >>
>>>> >> uwsgi --master --emperor /etc/uwsgi/apps-enabled --die-on-term
>>>> >> *** Starting uWSGI 1.9.15 (32bit) on [Thu Sep 12 12:43:31 2013] ***
>>>> >> compiled with version: 4.6.3 on 06 September 2013 01:16:38
>>>> >> os: Linux-2.6.32-19-pve #1 SMP Wed May 15 07:32:52 CEST 2013
>>>> >> nodename: dev02
>>>> >> machine: i686
>>>> >> clock source: unix
>>>> >> detected number of CPU cores: 1
>>>> >> current working directory: /etc/uwsgi/apps-available
>>>> >> detected binary path: /usr/local/bin/uwsgi
>>>> >> uWSGI running as root, you can use --uid/--gid/--chroot options
>>>> >> *** WARNING: you are running uWSGI as root !!! (use the --uid flag)
>>>> ***
>>>> >> your processes number limit is 128192
>>>> >> your memory page size is 4096 bytes
>>>> >> detected max file descriptor number: 1024
>>>> >> lock engine: pthread robust mutexes
>>>> >> Python version: 2.7.3 (default, Apr 10 2013, 06:03:17)  [GCC 4.6.3]
>>>> >> *** starting uWSGI Emperor ***
>>>> >> *** has_emperor mode detected (fd: 6) ***
>>>> >> [uWSGI] getting INI configuration from inochinoki.ini
>>>> >> *** Starting uWSGI 1.9.15 (32bit) on [Thu Sep 12 12:43:31 2013] ***
>>>> >> compiled with version: 4.6.3 on 06 September 2013 01:16:38
>>>> >> os: Linux-2.6.32-19-pve #1 SMP Wed May 15 07:32:52 CEST 2013
>>>> >> nodename: dev02
>>>> >> machine: i686
>>>> >> clock source: unix
>>>> >> detected number of CPU cores: 1
>>>> >> current working directory: /etc/uwsgi/apps-enabled
>>>> >> detected binary path: /usr/local/bin/uwsgi
>>>> >> setgid() to 33
>>>> >> setuid() to 33
>>>> >> your processes number limit is 128192
>>>> >> limiting address space of processes...
>>>> >> your process address space limit is 146800640 bytes (140 MB)
>>>> >> your memory page size is 4096 bytes
>>>> >> detected max file descriptor number: 1024
>>>> >> lock engine: pthread robust mutexes
>>>> >> uwsgi socket 0 bound to UNIX address /tmp/inochinoki.socket fd 3
>>>> >> Python version: 2.7.3 (default, Apr 10 2013, 06:03:17)  [GCC 4.6.3]
>>>> >> Set PythonHome to /root/.virtualenvs/inochinoki
>>>> >> *** Python threads support is disabled. You can enable it with
>>>> >> --enable-threads ***
>>>> >> Python main interpreter initialized at 0x8286670
>>>> >> your mercy for graceful operations on workers is 60 seconds
>>>> >> *** Operational MODE: no-workers ***
>>>> >> spawned uWSGI master process (pid: 8655)
>>>> >> ImportError: No module named site
>>>> >> VACUUM: unix socket /tmp/inochinoki.socket removed.
>>>> >> [emperor] removed uwsgi instance inochinoki.ini
>>>> >> ^C[emperor] *** RAGNAROK EVOKED ***
>>>> >> SIGINT/SIGQUIT received...killing workers...
>>>> >> The Emperor has been buried (pid: 8656)
>>>> >> goodbye to uWSGI.
>>>> >>
>>>> >> ----- LOG -----
>>>> >>
>>>> >>
>>>> >> 2013/9/12 Łukasz Mierzwa <[email protected]>
>>>> >>
>>>> >>> > ImportError: No module named wsgihandler
>>>> >>>
>>>> >>> Maybe you just need to add:
>>>> >>>
>>>> >>> chdir  = <dir where wsgihandler is located>
>>>> >>>
>>>> >>> maybe chdir=%(base)/opt would work.
>>>> >>>
>>>> >>> uWSGI can't find wsgihandler module that you specified, use chdir
>>>> option
>>>> >>> to set working directory.
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >
>>>> >
>>>> > Hi, first of all remove limit-as and optimize=2 they can cause
>>>> problems
>>>> > with error/debug messages (and generally use tiny configuration for
>>>> > debugging)
>>>> >
>>>> > Send the output of
>>>> >
>>>> > ls -l /root/.virtualenvs/inochinoki
>>>> >
>>>> > and
>>>> >
>>>> > ls -l /root/.virtualenvs/inochinoki/lib/python*
>>>> >
>>>> > maybe there is something wrong in the virtualenv itself
>>>> >
>>>> > --
>>>> > Roberto De Ioris
>>>> > http://unbit.it
>>>> > _______________________________________________
>>>> > uWSGI mailing list
>>>> > [email protected]
>>>> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>>>
>>>>
>>>>
>>>> --
>>>> Oscar A. Mata T.
>>>> Director de TI
>>>> Maximum Labs
>>>> Representaciones Metamax C.A.
>>>> _______________________________________________
>>>> uWSGI mailing list
>>>> [email protected]
>>>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>>>
>>>
>>>
>>>
>>> --
>>> Łukasz Mierzwa
>>>
>>> _______________________________________________
>>> uWSGI mailing list
>>> [email protected]
>>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>>
>>>
>> _______________________________________________
>> uWSGI mailing list
>> [email protected]
>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>
>>
>
>
> --
> Łukasz Mierzwa
>
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to