[modwsgi] Re: mod_wsgi permission error on activate file

Now I removed the virtual environment and change wsgi-file to this: [image: Screenshot 2023-04-17 170647.png] and the config file accordingly and the application starts! Now I am struggeling with my sqlite db. Obviously it not enough to just have in the document root like in the test system. If

[modwsgi] Re: mod_wsgi permission error on activate file

Hi Graham, thank you very much for your comments and recommendations. 1. I do not have AppArmor enabled - at least I am not aware of 2. I have checked my installation implementing the suggested test applicationn "myapp" described here

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

If you are still using: WSGIScriptAlias / /var/www/wsgi-scripts/mywebtool.wsgi then your WSGI application will hide the original Apache document root directory. If you application is responding for both / and /mywebtool, then that is going to be because of how your Flask routes are set

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

I'm happy to report that I have the Flask app up and running. I cleaned up and double-checked my directories and made one change to the script: I renamed references of "app" to "application". This got my "hello world" app running, but once I did it have it running, I noticed that it would run

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

I will check these in the morning. Thank you for all the help. On Monday, October 29, 2018 at 5:48:39 PM UTC-7, Graham Dumpleton wrote: > > You don't need to chmod +x the WSGI script file. > > Ensure you still have: > > from mywebtool import app as application > > in the WSGi script file. > >

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

Nothing should be cached from old version of file, but to be safe I would suggest stopping and starting Apache, trying again and seeing what error you get. Also see comments below. > On 30 Oct 2018, at 11:36 am, wc wrote: > > mywebtool.wsgi is indeed in the location you noted > > my virtual

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

mywebtool.wsgi is indeed in the location you noted my virtual host section (showing the WSGIScriptAlias) is: ServerName my.server.edu DocumentRoot /var/www/FLASKAPPS Require all granted WSGIScriptAlias / /var/www/wsgi-scripts/mywebtool.wsgi

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

Where is 'mywebtool.wsgi'. The error suggests: /var/www/wsgi-scripts/mywebtool.wsgi yet, the error also says: [Mon Oct 29 15:55:30.446084 2018] [wsgi:error] [pid 20476] [client 60.248.94.241:50359] File "/var/www/wsgi-scripts/mywebtool.wsgi", line 1, in [Mon Oct 29 15:55:30.446150

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

I believe I understand what you mean for the package vs. module structure. I get: $ ls -las /var/www/FLASKAPPS total 6 1 drwxr-xr-x 2 root wheel3 Oct 23 17:39 . 1 drwxr-xr-x 4 root wheel4 Oct 23 18:10 .. 5 -rw-r--r-- 1 wes wes148 Oct 23 17:33 mywebtool.py When I do the ls

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

> On 30 Oct 2018, at 11:16 am, wc wrote: > > Yes, my "mywebtool" is under > > /var/www/FLASKAPPS > > I'm assuming that Apache is running as user www, though I should check that > and check the permissions on the file. As I recall, I uploaded the files as > root because I was unable to

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

Yes, my "mywebtool" is under /var/www/FLASKAPPS I'm assuming that Apache is running as user www, though I should check that and check the permissions on the file. As I recall, I uploaded the files as root because I was unable to modify the directory /var/www as myself from my ftp prog. I

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

Is your mywebtool module/package under: /var/www/FLASKAPPS or: /var/www/wsgi-scripts Are the directories/files readable to the user that Apache runs as? Is mod_wsgi compiled for Python 2.7 or 3.X? If mywebtool is a package, does it have an __init__.py file in it. Graham > On 30 Oct

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

Thank you both for your replies. I now have a better understanding of the wsgi framework and I am using the error log to my advantage. I was able to find an error in my httpd.conf - I was using Apache 2.2 syntax in my directives, now I've updated it with the "Require all granted" and I am

Re: [modwsgi] Re: mod_wsgi problems on freeBSD

I'd agree on that except as noted. If the error message from the Apache error log is shown, along with configuration for your WSGI application in Apache config, as well as saying where your Python application code is located, that would help to give better idea of what is going on. > On 30

[modwsgi] Re: mod_wsgi problems on freeBSD

403 usually means that the directory to which you are hosting the .wsgi isn't configured with: AllowOverride None Require all granted This is required even though you have configured WSGIScriptAlias /web/path/to/app /path/to/your/app.wsgi On Monday, October 29, 2018 at 6:52:29 PM

[modwsgi] Re: [mod_wsgi] Error during make: /bin/sh: 1: apxs: not found

Thank you very much. I knew it'd have to be something conceptually simple. I managed to resolve it by installing apache2-prefork-dev (took two attempts). Still got some other errors, but I dont think any of those have anything to do with mod_wsgi. Op maandag 4 juni 2018 12:10:21 UTC+2 schreef

[modwsgi] Re: mod_wsgi issues when using anaconda3 and httpd

Thank you for an immediate response. It works for me. Now mod_wsgi is loaded onto the server and I can access Apache server page through localhost. But when I have placed myapp.conf file. I could not access the page and the error_log says* avahi_entry_group_add_service_strlst failed invalid

[modwsgi] Re: mod_wsgi issues when using anaconda3 and httpd

Thank you for your immediate response. I will work on the installation again and will get back to you. On Monday, December 5, 2016 at 1:49:35 PM UTC-6, ram.u...@gmail.com wrote: > > Hi All, > > I am using Redhat scientific Linux 6.7. OS has python2.6 already > installed. I have downloaded

Re: [modwsgi] Re: mod_wsgi importError

And does /var/www/flask_stuff_files/templates/analysis exist? Does it have to be a directory or a file? For uploads those directories will need to be writable to Apache user. > On 22 Aug 2016, at 8:52 AM, Tierprot B. wrote: > > Hmm and now im more confused, i copied server

Re: [modwsgi] Re: mod_wsgi importError

Hmm and now im more confused, i copied server files from /home/user/flask_stuff_files to the new directory /var/www/flask_stuff_files and corrected Apache conf, now it looks like: apache-wsgi config: ServerName www.example.com DocumentRoot

Re: [modwsgi] Re: mod_wsgi importError

> On 22 Aug 2016, at 8:16 AM, Tierprot B. wrote: > > Aha! Thanks! Addition of proper user and group options to WSGIDaemonProcess > solved the ImportError! The last question i have might be not related to > mod_wsgi directly, but still. > I have a Flask app, purpose of

Re: [modwsgi] Re: mod_wsgi importError

Aha! Thanks! Addition of proper user and group options to WSGIDaemonProcess solved the ImportError! The last question i have might be not related to mod_wsgi directly, but still. I have a Flask app, purpose of which to be able to upload files provided by user, do some math and return result on a

Re: [modwsgi] Re: mod_wsgi importError

> > > That is what WSGIScriptAlias is doing in giving it the path to the WSGI > script file. If you mean something different you need to be clearer. > > b) that it should include python files from outside directory, for example > home/user/flask_stuff_files ? > > > If you are talking about

Re: [modwsgi] Re: mod_wsgi importError

> On 21 Aug 2016, at 8:35 PM, Tierprot B. wrote: > > Thanks for the fast reply! I did what you`ve wrote and yay it worked! Now i > wondering how can i tell to mod_wsgi two things - a) that wsgi file itself > lies in /var/www/wsgi-scripts and That is what WSGIScriptAlias

[modwsgi] Re: mod_wsgi importError

Thanks for the fast reply! I did what you`ve wrote and yay it worked! Now i wondering how can i tell to mod_wsgi two things - a) that wsgi file itself lies in /var/www/wsgi-scripts and b) that it should include python files from outside directory, for example home/user/flask_stuff_files ? --

Re: [modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

Can you provide the traces for all threads? Graham > On 9 Oct 2015, at 12:36 am, 'Lukasz Szajkowski' via modwsgi > wrote: > > Thanks a lot Graham for advice > > I tried the settings > WSGIScriptAlias / /opt/hosts/pyws.test/pyws/pyws/wsgi.py > process-group=pyws.st

[modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

Thanks a lot Graham for advice I tried the settings WSGIScriptAlias / /opt/hosts/pyws.test/pyws/pyws/wsgi.py process-group=pyws.st application-group=%{GLOBAL} WSGIImportScript /opt/hosts/pyws.test/pyws/pyws/wsgi_monitor.py process-group=pyws.st application-group=%{GLOBAL} but I still got the

[modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

Deadlock shows that application hangs trying to load modules (from django or built-in etc.). Normally it should be done only once at start-up, but in our case it's after many requests (*Why)*. So possible explanations: * python process/interpreter is killed/restarted from outside (e.g. by

Re: [modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

> On 6 Oct 2015, at 6:32 pm, 'Lukasz Szajkowski' via modwsgi > wrote: > > Deadlock shows that application hangs trying to load modules (from django or > built-in etc.). Normally it should be done only once at start-up, but in our > case it's after many requests

[modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

I am not sure if it matters but there is one more python demon on the same Apache here is the config #LogLevel warn ErrorLog "/opt/logs/pyframe/vhost_epa_prod_error.log" CustomLog "/opt/logs/pyframe/vhost_epa_prod_access.log" combined WSGIDaemonProcess epa.prod processes=1 threads=25 user=pnc

Re: [modwsgi] Re: mod_wsgi (3.4-14) / Apache 2.4.12 / cx_oracle 5.2 / Oracle 12 / Red Hat (6.7) / Django 1.8.2 hanging under load

Looks like a lock isn't being freed or a lock priority inversion, etc. Tricky. On Mon, Sep 28, 2015 at 3:10 PM, 'Lukasz Szajkowski' via modwsgi < modwsgi@googlegroups.com> wrote: > The actual stack trace while hanging is > #0 0x7f047ff099b0 in sem_wait () from /lib64/libpthread.so.0 > #1

[modwsgi] Re: mod_wsgi app hanging and I can't pinpoint where its hanging...need help

ppp On Monday, August 12, 2013 at 6:54:24 PM UTC-4, Adam wrote: > > Ok. So this one pyramid app I wrote half a year ago is acting up as this > group of artists went ahead to release a new art pack. The app is hitting > some infinite loops/deadlocks somewhere and I'm not sure what's going on

[modwsgi] Re: mod_wsgi-express possible to edit conf file?

There is one --include-file option for mod_wsgi-express, which might be what you are looking for: --include-file FILE-PATH Specify the path to an additional web server configuration file to be included at the end of the

[modwsgi] Re: mod_wsgi-express: Syntax error: cannot load .../server/mod_wsgi-py27.so into server

Dear Graham, many thanks for your fast answer. I reseted the system and installed it again. Today I will install all requirements and give you feedback as soon as possible. Thank your very much for your help. I hope that i will run fine :) Am Mittwoch, 3. Juni 2015 22:44:39 UTC+2 schrieb

[modwsgi] Re: mod_wsgi v3.5 Installation within Python

Some additional Version background on my system environment: - Platform: Windows 7 Pro 32-bit - Python Installation: - Version 2.7.6 32 Bit - (Default Install for Multiple User; User installed had Admin privileges) - LAMP Stack: XAMPP v1.8.2 32-bit - Apache

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

Thank you for the fast response. The failure is that I can not browse to my hello world app, and see the expected response Yo World. yohost is in my hosts files (tied currently to 127.0.0.1).. pingable and resolvable. i've tried to get to the site using wget wget http://yohost/yo I am able

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

So In the error log I see the following: [Thu Sep 25 13:57:44.291610 2014] [core:info] [pid 3148:tid 139882152310528] [client 127.0.0.1:38363] AH00128: File does not exist: /var/www/html/yo The access log shows a 404: 127.0.0.1 - - [25/Sep/2014:13:57:44 +] GET /yo HTTP/1.1 404 490 -

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

The same request within the browser also shows that Not Found The requested URL /yo was not found... On Thursday, September 25, 2014 9:04:57 AM UTC-4, David Sargrad wrote: I am trying to follow the instructions for running the mod_wsgi hello world application:

Re: [modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

What other VirtualHost definitions are setup for port 80, and especially with the same ServerName. You can't have more than for same server name and port combination. Most likely it is ignoring your added one and using a previous one. Also do check if you new one is even being loaded by adding

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

I did a fresh install of both apache and mod_wsgi yesterday. This is the only virtual host enabled (above and beyond the default). Though I started first with my flask app yesterday I disabled that site: /etc/apache2/sites-enabled# ls -ltr total 0 lrwxrwxrwx 1 root root 35 Sep 25 12:03

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

Ok. I've added a syntax error intentionally (this btw was something i did b4 to verify that the site file was being loaded).. did it again just to be thorough: service apache2 restart * Restarting web server apache2

Re: [modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

If you access: http://yohost/yo.wsgi do you see the source code for the script? If you don't it means that VirtualHost is not being used but the default is. Also try using telnet to access the server port directly: $ telnet yohost 80 GET /yo HTTP/1.0 Host: yohost With multiple returns after

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

Wow.. telnet shows yo world.. root@sensis-8930:/etc/apache2# telnet yohost 80 Trying 127.0.1.1... Connected to sensis-8930.corp.sensis.com. Escape character is '^]'. GET /yo HTTP/1.0 Host: yohost HTTP/1.1 200 OK Date: Thu, 25 Sep 2014 14:31:54 GMT Server: Apache/2.4.7 (Ubuntu) Content-Length: 9

[modwsgi] Re: mod_wsgi hello world failing on ubuntu 14.04

Hmm. Ok with your suggestions, I've finally figured out the problem. It is indeed a problem with having the default VirtualHost enabled. I disabled that and voila everything works: a2dissite 000-default I'm surprised that none of the tutorials that I've seen suggest this. They all talk about

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

I just changed processes=2 threads=5 to see how long I can stay alive without queuing requests. htop now reports 18 threads: 10320 www-data 20 0 172M 75264 4668 S 0.0 0.9 0:57.46 mod-wsgi -k start 10321 www-data 20 0 172M 75264 4668 S 0.0 0.9 1:16.62 mod-wsgi

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

I left the config processes=2 threads=5 from about 12:00pm ET - 1:40pm ET and the capacity analysis and app reports showed lots of request queueing and really, really bad performance. During that time apache memory usage climbed from 140M-180M in NR's server monitor. Going to try flipping

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

Just discovered htop tree view. With processes=5 threads=2 I wouldn't expect to see 5 threads under each process. Memory for one of these processes has ballooned to 283M. Eventually when all 5 of them get there, that means I'll be using 1.5G of ram for mod_wsgi. 20179 www-data 20 0 147M

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

After monitoring the wsgi processes for some time I noticed one of the processes consumed 585M of memory. Ouch. if all 5 processes consumed that much, the server would be approaching 3G of memory used by mod_wsgi. After looking through the mod_wsgi config parameters

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

Graham, I'm still not sure why with processes=5 threads=2 I see 5 threads for each process for mod_wsgi in htop. If you could explain that last little hanging chad it would be great. Thanks! Updated SO with summary of solution:

[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned

Thank you, Graham. This information is invaluable. Mark On Wednesday, February 19, 2014 12:05:56 PM UTC-5, scoopseven wrote: This question started on SO: http://serverfault.com/questions/576527/apache-processes-in-top-more-than-maxclients/576600 I've updated my Apache config and mod_wsgi

[modwsgi] Re: mod_wsgi: Possible enhancement: making log level adjustable per message

[Moved to Google Group from private email] Thanks for the response Graham. Yes, the standalone version makes use of Python logging. It seemed that it was adding an additional and potentially unnecessary layer to use Python logging on top of the existing Apache multilevel logging given that

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

Hi Graham I have carried out the make install now and when I run the otool on the installed mod_wsgi.so I get the following result; mod_wsgi.so: /Library/Frameworks/Python.framework/Versions/3.2/Python (compatibility version 3.2.0, current version 3.2.0) /usr/lib/libSystem.B.dylib

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

With Mountain lion it comes with versions 2.3, 2.5, 2.6, 2.7. These are installed as you have correctly stated however the installation is a little different compared to a linux installation. The version 3.2 that I have installed is from the python site at the following location

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

With otool -L showing the correct result, what then was the result when you tried to actually use it with Apache??? If there is still a run time linking issue causing Apache not to start, you can usually see the error by running: sudo /usr/sbin/apachectl -t It will show any linker error as

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

Graham These are the steps that I followed and the output I received; 1. ./configure --with-python=/Library/Frameworks/Python.framework/Versions/3.2/bin/python3 --disable-framework 2. make 3. cd .libs 4. otool -L mod_wsgi.so Output mod_wsgi.so:

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

The output is correct, although one thing worried me. Can you confirm that you manually installed Python 3.2, because a system Python wouldn't be under: /Library/Frameworks/Python.framework What Python versions are under: /System/Library/Frameworks/Python.framework/Versions I ask as I am

[modwsgi] Re: mod_wsgi prevents apache start following update

Hi Graham, thanks for the pointer but it hasn't worked. Here is what I entere into terminal; hostname:mod_wsgi-3.4 user$ ./configure --with-python=/Library/Frameworks/Python.framework/Versions/3.2/bin/python3 --disable-framework checking for apxs2... no checking for apxs... /usr/sbin/apxs

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

Run 'make distclean' in the directory before you rerun configure. You still had old build results lying around by the look of it. On 4 October 2012 05:08, Jake jake.griff...@realspaces.com wrote: Hi Graham, thanks for the pointer but it hasn't worked. Here is what I entere into terminal;

[modwsgi] Re: mod_wsgi prevents apache start following update

I had deleted the previous download and started with a clean one. Not sure if the 'make distclean' will do anything. I ran it anyway and got the following ; make: *** No rule to make target `distclean'. Stop. Which I think is to be expected. On Wednesday, October 3, 2012 12:02:16 AM UTC+1,

Re: [modwsgi] Re: mod_wsgi prevents apache start following update

The output you gave showed: hostname:mod_wsgi-3.4 user$ make make: Nothing to be done for `all'. which indicated that make had already been run in the directory again. From that fresh source code, do the configure and make and then run: otool -L .libs/mod_wsgi.so without doing an install.

Re: [modwsgi] Re: mod_wsgi and mod_ruid2

Graham, Thank you very much for help! Now it is working perfect! WSGIDaemonProcess moin user=www-moin group=www-moin home=/web/moin/ processes=5 threads=10 maximum-requests=1000 umask=0007 On Friday, July 20, 2012 8:51:00 PM UTC+3, Graham Dumpleton wrote: Use: WSGIDaemonProcess moin

[modwsgi] Re: mod_wsgi and mod_ruid2

Thank you for reply! I tried: apt-get remove libapache2-mod-wsgi # /usr/local/src wget http://modwsgi.googlecode.com/files/mod_wsgi-3.3.tar.gz tar -zxvf mod_wsgi-3.3.tar.gz cd mod_wsgi-3.3 vi mod_wsgi.c Change: #if defined(MPM_ITK) if (chown(process-socket, process-uid, -1) 0) { #else

Re: [modwsgi] Re: mod_wsgi and mod_ruid2

Use: WSGIDaemonProcess moin user=www-moin group=www-moin home=/tmp processes=5 threads=10 maximum-requests=1000 umask=0007 That is, add home=/tmp argument. This will get rid of complaint about not being able to change home directory. Graham On 20 July 2012 10:20, slech xum...@gmail.com wrote:

[modwsgi] Re: mod_wsgi under virtualenv: Error no module named site

Yes that was indeed the problem. My /home/admin was 700 although I had fixed permissions is /home/admin/py_run. Changing /home/admin permissions to 755 fixed it. Thanks On Jul 10, 10:32 am, Graham Dumpleton graham.dumple...@gmail.com wrote: You are missing a WSGIProcessGroup directive to go with

[modwsgi] Re: mod_wsgi without python instalation

Great, thanks. Any idea what to do with registry entry? -- 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.

Re: [modwsgi] Re: mod_wsgi without python instalation

On 23 May 2012 20:20, Martin B. andzin.d...@gmail.com wrote: Great, thanks. Any idea what to do with registry entry? Look at WSGIPythonHome and WSGIPythonPath directives in mod_wsgi configuration. Graham -- You received this message because you are subscribed to the Google Groups modwsgi

Re: [modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

Has this problem been resolved yet? I am running an OSX version that comes with Apache/2.2.22 and would hate to have to downgrade Apache to run mod_wsgi. -- Gnarlie -- You received this message because you are subscribed to the Google Groups modwsgi group. To view this discussion on

Re: [modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

On 27 April 2012 04:16, Gnarlodious gnarlodi...@gmail.com wrote: Has this problem been resolved yet? I am running an OSX version that comes with Apache/2.2.22 and would hate to have to downgrade Apache to run mod_wsgi. Can you clarify what you are asking about? The prior discussion was about

[modwsgi] Re: mod_wsgi import python modile placed in a folder

I have made it with: site.addsitedir('/home/baddc0re/Desktop/htdocs/') -- You received this message because you are subscribed to the Google Groups modwsgi group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/CbF0Lerej88J. To post to this group, send email

Re: [modwsgi] Re: mod_wsgi import python modile placed in a folder

If you are trying to say it works when you use that, that could only be the case if you had .pth files in the directory /home/baddc0re/Desktop/htdocs/. Otherwise there should be no difference between that and doing sys.path.append() for same directory. Graham On 14 April 2012 18:23, badc0re

Re: [modwsgi] Re: mod_wsgi-3.3 Python 3.2 - apache2.2 - windows 7 build

On 28 December 2011 02:51, Ahmed Hassan ahmed.i...@gmail.com wrote: i also tried Visual Studio 2008 and the same goes here I fixed what would have been a few obvious build problems with mod_wsgi 4.0 trunk on Windows since last email. I still haven't tried it myself yet as still trying to get

Re: [modwsgi] Re: mod_wsgi and apache vs. paster

Thanks very much. On 3/26/2012 3:28 PM, Graham Dumpleton wrote: See: http://code.google.com/p/modwsgi/wiki/TipsAndTricks#Determining_If_Running_Under_mod_wsgi Graham On 27 March 2012 03:02, Kentjkentbo...@gmail.com wrote: I found this: if shell in sys.argv: And I'll use that unless

[modwsgi] Re: mod_wsgi and apache vs. paster

I found this: if shell in sys.argv: And I'll use that unless someone has a better way. Thanks! On Monday, March 26, 2012 11:46:07 AM UTC-4, Kent wrote: Graham, How can I detect from within my application whether it is being run by apache with mod_wsgi versus run by paster? I'm

Re: [modwsgi] Re: mod_wsgi and apache vs. paster

See: http://code.google.com/p/modwsgi/wiki/TipsAndTricks#Determining_If_Running_Under_mod_wsgi Graham On 27 March 2012 03:02, Kent jkentbo...@gmail.com wrote: I found this: if shell in sys.argv: And I'll use that unless someone has a better way. Thanks! On Monday, March 26, 2012

[modwsgi] Re: mod_wsgi for Apache2.2 / Python2.5 on Windows

On 9 February 2012 02:58, Vijay vijaykumar...@gmail.com wrote: Graham Request your help in obtaining mod_wsgi module that is compatible with Apache2.2python2.5 on windows. I read your blogs and thought that you might be able to help me in this. I am newbie to world of python and am finding it

Re: [modwsgi] Re: mod_wsgi and access scripts for authentication

On 28 January 2012 12:53, James Slagle james.sla...@gmail.com wrote: I have a small patch for mod_wsgi that has enabled me to use WSGIAccessScript and have access to the client SSL certificate. The patch makes it so that the mod_ssl hooks that are registered at APR_HOOK_MIDDLE are run before

[modwsgi] Re: [mod_wsgi] It does not work with zeromq..

I am using mod_wsgi for python 2.7 and it completely works well without zmq things. And zmq works well when it used stand alone. I don't know why mod_wsgi cannot import zmq. Plus, it does not work even if I remove add site-package things. On Jan 6, 11:20 am, Graham Dumpleton

[modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

I should add that I installed the Python from the package installer. Should I have built it custom-like? -- Gnarlie -- You received this message because you are subscribed to the Google Groups modwsgi group. To view this discussion on the web visit

Re: [modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

Can you provide more context than that please? Have you used mod_wsgi 4.X source code from mod_wsgi source code repository? You can't use mod_wsgi 3.3 source code with Python 3.2. Also, what platform are you doing this on? Graham On 21 December 2011 23:37, Gnarlodious gnarlodi...@gmail.com

[modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

No I didn't know there is a version 4, I'll keep it in mind for next time. The only reason I wanted to upgrade is that Py3.1 leaves all sorts of .pyc files in my workspace, and in Py3.2 they are corralled into a cache folder. -- Gnarlie -- You received this message because you are subscribed

Re: [modwsgi] Re: mod_wsgi compiled with Python 3.2.2?

On 22 December 2011 13:21, Gnarlodious gnarlodi...@gmail.com wrote: No I didn't know there is a version 4, I'll keep it in mind for next time. The only reason I wanted to upgrade is that Py3.1 leaves all sorts of .pyc files in my workspace, and in Py3.2 they are corralled into a cache folder.

[modwsgi] Re: mod_wsgi-3.3 Python 3.2 - apache2.2 - windows 7 build

i cloned source with Mercurial: https://code.google.com/p/modwsgi/ In the folder there is win32-ap22py31.mk renamed to win32-ap22py32.mk and modified paths for python32, visual studio 10.0 and sdks/v7.0A still getting error c:\python32\include\pytime.h(21) : warning C4820: 'unnamed-tag' : '4'

[modwsgi] Re: mod_wsgi, apache, on RedHat - no module named os

Thanks, Graham. Permissions on that lib directory were the issue. We're over the hump with that, and on to some django config, now. Thanks a ton! On Jun 9, 7:14 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: The only thing I can see to suggest right now is to check whether the user

Re: [modwsgi] Re: mod_wsgi + virtualenv + multiple projects

zelegolas, If i understand the situation correctly, you just need to run an apache instance with modwsgi compiled for python2.6, where you would run all your projects which use python2.6. Then, say on port 81, run another instance of apache with modwsgi compiled for python2.7, and again all

Re: [modwsgi] Re: mod_wsgi + virtualenv + multiple projects

On 16 May 2011 17:25, Mr Kiwi mrk...@gmail.com wrote: zelegolas, If i understand the situation correctly, you just need to run an apache instance with modwsgi compiled for python2.6, where you would run all your projects which use python2.6. Then, say on port 81, run another instance of

[modwsgi] Re: mod_wsgi + virtualenv + multiple projects

If I understand well mod_wsgi is completely useless in my case :( Anyway thanks for your answer 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

Re: [modwsgi] Re: mod_wsgi + virtualenv + multiple projects

On 16 May 2011 07:03, zelegolas zelego...@gmail.com wrote: If I understand well mod_wsgi is completely useless in my case :( Yes and no. Within one single Apache instance you can't currently do what you want. You could however run up multiple Apache instances where each mod_wsgi uses different

[modwsgi] Re: mod_wsgi + multiprocessing

Thanks very much for the detailed prodding at this...and for the general advice. I figured it was a bad idea to be using multiprocessing in the mod_wsgi environment, so I appreciate the confirmation. //Ed On May 2, 7:55 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: Using the

[modwsgi] Re: mod_wsgi and apache on windows

Please use the mod_wsgi mailing list, don't mail me directly. Ensure you use reply-all to this email to ensure followups go back to the mailing list. First though go watch: http://code.google.com/p/modwsgi/wiki/WhereToGetHelp?tm=6#Conference_Presentations It talks about reasons for permissions

Re: [modwsgi] Re: Mod_wsgi ...

Hi all, Sorry by delay ... but I want to say thank for all of you ... I have not resolved my problem yet, because I cannot found a good solution for that, however I will verify all suggestions and think about it..., who knows I have a insight and decide to change for the Ubuntu or changes my

Re: [modwsgi] Re: Mod_wsgi ...

Hello all, Graham ..., I have sent only to you several emails on January_2011. Just look for them, Ok. As I told you before ( 01/2011 ) everything is right with the Python's installation except that it is 64bits, I am not sure whether is a big problem ... All users is default of the Python's

Re: [modwsgi] Re: Mod_wsgi ...

Ademir, Both Apache and Python must be compiled for 64 bits. In other words both must be compiled the same either 32 or 64 bits. Both Apache should have libs compiled for x86_64 if they are both 64 bit. You can use the ldd command to see how they are compiled. You will notice that on the machine

Re: [modwsgi] Re: Mod_wsgi ...

Ademir, Sorry, I hadn't realized that you were using this on a Windows box my apologies, however the fact that both Apache and Python need to be compiled for the same bit width is still necessary. I don't know how to test this on a windows machine since I never use them. You did mention in your

Re: [modwsgi] Re: Mod_wsgi ...

On 7 March 2011 03:09, Ademir Francisco da Silva ademirfs@gmail.com wrote: Hello all, Graham ..., I have sent only to you several emails on January_2011. Just look for them, Ok. As I told you before ( 01/2011 ) everything is right with the Python's installation except that it is

[modwsgi] Re: mod_wsgi build problems

I stand corrected. By starting apache manually, I was lulled into a false sense apache would find the shared library. It did not on reboot. After doing a make clean and issuing your instructions below and make install, all is well. Thanks again. This setting will not be used by mod_wsgi when run

[modwsgi] Re: mod_wsgi build problems

Your way is better by embedding the path at configure time. Apache is working with this. Root's config is set to load this library. Oh and by the way, thanks for all your help. It was invaluable. On Feb 8, 9:57 pm, Graham Dumpleton graham.dumple...@gmail.com wrote: On 8 February 2011 05:52,

Re: [modwsgi] Re: mod_wsgi build problems

On 8 February 2011 05:52, octopusgrabbus old_road_f...@verizon.net wrote: Success. Reconfigured Python 2.6.6 with --enable-shared put in link lrwxrwxrwx 1 root root 30 Feb  7 12:01 /usr/local/lib/python2.6/config/ libpython 2.6.so - /usr/local/lib/libpython2.6.so And loaded the library

[modwsgi] Re: mod_wsgi build problems

Please keep discussion on the mailing list. On 8 February 2011 01:58, octopusgrabbus old_road_f...@verizon.net wrote: Graham: My answer back to you was not intended to be flip. I looked at the link you posted this morning, and cannot find the instructions to rebuild Python on this 64-bit

[modwsgi] Re: mod_wsgi build problems

Made that error go away by adding the location of the shared library to the load library path. On Feb 7, 11:46 am, octopusgrabbus old_road_f...@verizon.net wrote: Graham: I rebuilt Python 2.6.6 using the --enable-shared switch on config. This produced /usr/local/lib/libpython2.6.so.1.0 I

[modwsgi] Re: mod_wsgi build problems

Success. Reconfigured Python 2.6.6 with --enable-shared put in link lrwxrwxrwx 1 root root 30 Feb 7 12:01 /usr/local/lib/python2.6/config/ libpython 2.6.so - /usr/local/lib/libpython2.6.so And loaded the library from .bashrc export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH mod_wsgi built

  1   2   3   4   5   >