[modwsgi] I use WSGIDaemonProcess server user=demon group=demon but it still use www-data user
I user ubuntu 10.04 Apache/2.2.14 mod_wsgi 2.8. I use WSGIDaemonProcess server user=demon group=demon ,but when I print sys.stderr,os.environ,I see the result: ''' [Fri Nov 25 15:23:12 2011] [error] {'LANG': 'C', 'SHLVL': '1', 'APACHE_RUN_USER': 'www-data', 'APACHE_PID_FILE': '/var/run/ apache2.pid', 'PWD': '/', 'APACHE_RUN_GROUP': 'www-data', 'PATH': '/ usr/local/bin:/usr/bin:/bin', '_': '/usr/sbin/apache2'} ''' How can I change the user wsgi running? Thanks -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
[modwsgi] Re: I use WSGIDaemonProcess server user=demon group=demon but it still use www-data user
After I add WSGIProcessGroup directive,my app work ok now,but the print sys.stderr,os.environ still www-data. It works now but weird. On Fri, Nov 25, 2011 at 3:28 PM, Chunlin Zhang zhangchun...@gmail.com wrote: I user ubuntu 10.04 Apache/2.2.14 mod_wsgi 2.8. I use WSGIDaemonProcess server user=demon group=demon ,but when I print sys.stderr,os.environ,I see the result: ''' [Fri Nov 25 15:23:12 2011] [error] {'LANG': 'C', 'SHLVL': '1', 'APACHE_RUN_USER': 'www-data', 'APACHE_PID_FILE': '/var/run/ apache2.pid', 'PWD': '/', 'APACHE_RUN_GROUP': 'www-data', 'PATH': '/ usr/local/bin:/usr/bin:/bin', '_': '/usr/sbin/apache2'} ''' How can I change the user wsgi running? Thanks -- You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com. To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
[modwsgi] Re: win32 modwsgi error: ImportError: DLL load failed
Another issue: After I add WSGIDaemonProcess moin user=someuser group=somegroup home=/home/someuser processes=5 threads=10 maximum-requests=1000 umask=0007 to my http.conf,I could not start the apache service,got the err message:The Apache service named reported the following error: Invalid command 'WSGIDaemonProcess', perhaps misspelled or defined by a module not included in the server configuration . and the WSGIScriptAlias is ok. Thanks! On Thu, Apr 16, 2009 at 11:31 AM, Chunlin Zhang zhangchun...@gmail.com wrote: It is OK now! I reinstall with python 2.6.2 and now works. Thank you very much! On Thu, Apr 16, 2009 at 9:33 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/16 Chunlin Zhang zhangchun...@gmail.com: On Thu, Apr 16, 2009 at 4:56 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/15 chunlin zhangchun...@gmail.com: I just check my python installation,found the directory is C: \Documents and Settings\All Users\...\Python 2.6,so I chose All Users. That isn't necessarily sufficient indication as there are registry entries as well and is is those which are more of an issue as they define the directories to look for stuff. If you are going to reinstall anythng, install newer Python 2.6.2. Don't go back to Python 2.5 as don't supply latest mod_wsgi.so for that version of Python. So, just try the reinstall of Python like suggested. But like you say before,the win32 build(mod_wsgi-win32-ap22py26-2.4.so) is for 2.6.1,no problem about that?(Or I misunderstood?) Ok,I will try it first(2.6.2),if back to 2.5 I will install too much python module... The patch revision (third number) of Python shouldn't matter, so that module, although compiled against Python 2.6.1 should also work for other Python 2.6.X versions. I just want to see Python reinstalled and since 2.6.2 is latest, no reason not to use that. Graham Graham And I always using a Administrator privilege account(a windows user's usual habbit...). So I had better turn back to python 2.5...:( On Apr 15, 7:21 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Hmmm, I tell a lie. SInce Python 2.6.2 only just got released, the Apache module must have been compiled against Python 2.6.1. Can't be bothered starting up Windows at the moment to check. Anyway, would suggest your problem is therefore likely to be due to Python not being installed so as to be available to all users. So, reinstall it as user with Administrator rights and install it for all users when prompted. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~--~~~~--~~--~--~---
[modwsgi] Re: win32 modwsgi error: ImportError: DLL load failed
On Thu, Apr 16, 2009 at 6:40 PM, Graham Dumpleton graham.dumple...@gmail.com wrote: Daemon mode is not available on Windows. Just drop the WSGIDaemonProcess and WSGIProcessGroup directives. Will it be supported in the future? Graham Thanks! On Thu, Apr 16, 2009 at 11:31 AM, Chunlin Zhang zhangchun...@gmail.com wrote: It is OK now! I reinstall with python 2.6.2 and now works. Thank you very much! On Thu, Apr 16, 2009 at 9:33 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/16 Chunlin Zhang zhangchun...@gmail.com: On Thu, Apr 16, 2009 at 4:56 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/15 chunlin zhangchun...@gmail.com: I just check my python installation,found the directory is C: \Documents and Settings\All Users\...\Python 2.6,so I chose All Users. That isn't necessarily sufficient indication as there are registry entries as well and is is those which are more of an issue as they define the directories to look for stuff. If you are going to reinstall anythng, install newer Python 2.6.2. Don't go back to Python 2.5 as don't supply latest mod_wsgi.so for that version of Python. So, just try the reinstall of Python like suggested. But like you say before,the win32 build(mod_wsgi-win32-ap22py26-2.4.so) is for 2.6.1,no problem about that?(Or I misunderstood?) Ok,I will try it first(2.6.2),if back to 2.5 I will install too much python module... The patch revision (third number) of Python shouldn't matter, so that module, although compiled against Python 2.6.1 should also work for other Python 2.6.X versions. I just want to see Python reinstalled and since 2.6.2 is latest, no reason not to use that. Graham Graham And I always using a Administrator privilege account(a windows user's usual habbit...). So I had better turn back to python 2.5...:( On Apr 15, 7:21 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Hmmm, I tell a lie. SInce Python 2.6.2 only just got released, the Apache module must have been compiled against Python 2.6.1. Can't be bothered starting up Windows at the moment to check. Anyway, would suggest your problem is therefore likely to be due to Python not being installed so as to be available to all users. So, reinstall it as user with Administrator rights and install it for all users when prompted. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~--~~~~--~~--~--~---
[modwsgi] Re: win32 modwsgi error: ImportError: DLL load failed
On Thu, Apr 16, 2009 at 4:56 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/15 chunlin zhangchun...@gmail.com: I just check my python installation,found the directory is C: \Documents and Settings\All Users\...\Python 2.6,so I chose All Users. That isn't necessarily sufficient indication as there are registry entries as well and is is those which are more of an issue as they define the directories to look for stuff. If you are going to reinstall anythng, install newer Python 2.6.2. Don't go back to Python 2.5 as don't supply latest mod_wsgi.so for that version of Python. So, just try the reinstall of Python like suggested. But like you say before,the win32 build(mod_wsgi-win32-ap22py26-2.4.so) is for 2.6.1,no problem about that?(Or I misunderstood?) Ok,I will try it first(2.6.2),if back to 2.5 I will install too much python module... Graham And I always using a Administrator privilege account(a windows user's usual habbit...). So I had better turn back to python 2.5...:( On Apr 15, 7:21 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Hmmm, I tell a lie. SInce Python 2.6.2 only just got released, the Apache module must have been compiled against Python 2.6.1. Can't be bothered starting up Windows at the moment to check. Anyway, would suggest your problem is therefore likely to be due to Python not being installed so as to be available to all users. So, reinstall it as user with Administrator rights and install it for all users when prompted. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~--~~~~--~~--~--~---
[modwsgi] Re: win32 modwsgi error: ImportError: DLL load failed
It is OK now! I reinstall with python 2.6.2 and now works. Thank you very much! On Thu, Apr 16, 2009 at 9:33 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/16 Chunlin Zhang zhangchun...@gmail.com: On Thu, Apr 16, 2009 at 4:56 AM, Graham Dumpleton graham.dumple...@gmail.com wrote: 2009/4/15 chunlin zhangchun...@gmail.com: I just check my python installation,found the directory is C: \Documents and Settings\All Users\...\Python 2.6,so I chose All Users. That isn't necessarily sufficient indication as there are registry entries as well and is is those which are more of an issue as they define the directories to look for stuff. If you are going to reinstall anythng, install newer Python 2.6.2. Don't go back to Python 2.5 as don't supply latest mod_wsgi.so for that version of Python. So, just try the reinstall of Python like suggested. But like you say before,the win32 build(mod_wsgi-win32-ap22py26-2.4.so) is for 2.6.1,no problem about that?(Or I misunderstood?) Ok,I will try it first(2.6.2),if back to 2.5 I will install too much python module... The patch revision (third number) of Python shouldn't matter, so that module, although compiled against Python 2.6.1 should also work for other Python 2.6.X versions. I just want to see Python reinstalled and since 2.6.2 is latest, no reason not to use that. Graham Graham And I always using a Administrator privilege account(a windows user's usual habbit...). So I had better turn back to python 2.5...:( On Apr 15, 7:21 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Hmmm, I tell a lie. SInce Python 2.6.2 only just got released, the Apache module must have been compiled against Python 2.6.1. Can't be bothered starting up Windows at the moment to check. Anyway, would suggest your problem is therefore likely to be due to Python not being installed so as to be available to all users. So, reinstall it as user with Administrator rights and install it for all users when prompted. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups modwsgi group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~--~~~~--~~--~--~---