On 16 July 2012 22:40, Alan Kesselmann alan.kesselm...@gmail.com wrote:
Why is it wrong - thats my default 2.7.2 installation that all other sites
should work with.
It is wrong because WSGIPythonHome is not meant to be set to the name
of the Python binary.
On 16 July 2012 23:46, Alan Kesselmann alan.kesselm...@gmail.com wrote:
Allright... so humm..
do i understand this correctly: if i want to use apache with python 2.7.2 i
should also libapache2-mod-wsgi package mod_wsgi.so file?
If using distro packaged Python 2.7.2, you must use distro
Good night, dear sir :) You have been alot of help to me. i greatly
appreciate it.
Hmmm allright. So if i knew how to switch back to default mod_wsgi.so i
could go back and forth between ucs2 and ucs4 pythons? right? Then
everything would be sort of fixed i guess. Or i could use ucs2 python
Python home in log should not say /use/bin/python. That is very wrong. That
would suggest you have a rouge WSGIPythonHome directive in your Apache config
somewhere. Can you check.
Graham
On 16/07/2012, at 10:25 AM, Alan Kesselmann alan.kesselm...@gmail.com wrote:
On Monday, July 16, 2012
so i took my time and read carefully though the wiki about checking my
installation so it looks like it should be working.
I did what the wiki says and:
alan@alan:~$ unset LD_LIBRARY_PATH
alan@alan:~$ ldd /usr/lib/apache2/modules/mod_wsgi.so
linux-vdso.so.1 = (0x7fff6e1f7000)
Can continue here. But in a bit over a day I will be on a plane for a
day, so don't expect quick answers then. :-)
On 10 July 2012 16:47, Alan Kesselmann alan.kesselm...@gmail.com wrote:
so i took my time and read carefully though the wiki about checking my
installation so it looks like it
What is the current problem after fixing Python and mod_wsgi installations?
Did you ensure you recreated your virtual environments using the newly
installed Python?
Send the latest errors you get.
Graham
On 10 July 2012 17:06, Alan Kesselmann alan.kesselm...@gmail.com wrote:
No problem man -
*Did all that just now:*
alan@alan:~$ sudo uninstall virtualenvwrapper
[sudo] password for alan:
sudo: uninstall: command not found
alan@alan:~$ sudo pip uninstall virtualenvwrapper
Uninstalling virtualenvwrapper:
/usr/local/bin/virtualenvwrapper.sh
/usr/local/bin/virtualenvwrapper_lazy.sh
Run 'pldd' on one of the process IDs of Apache once started. May need
to be root. This will tell you what libpython Apache is actually
using.
On 10 July 2012 21:01, Alan Kesselmann alan.kesselm...@gmail.com wrote:
Did all that just now:
alan@alan:~$ sudo uninstall virtualenvwrapper
[sudo]
This is occurring because you have a Python 2.7 installed in a system
location as well.
Why aren't you using the system Python 2.7?
To get around this issue, when building Python and also mod_wsgi. Set:
LD_RUN_PATH=/opt/lib
export LD_RUN_PATH
This only needs to be set when they are
So let me get this straight so i dont do it rial and error way for 1 hour:
1) unpack 2.7.3.
2 ) LD_RUN_PATH=/opt/lib
3) export $LD_RUN_PATH
4) ./configure --enable-shared --prefix=/opt --enable-unicode=ucs2
5) make
6 ) make install?
And yes - i have python 2.7.2 installed and im installing 2.7.3
On 9 July 2012 18:37, Alan Kesselmann alan.kesselm...@gmail.com wrote:
So let me get this straight so i dont do it rial and error way for 1 hour:
1) unpack 2.7.3.
2 ) LD_RUN_PATH=/opt/lib
3) export $LD_RUN_PATH
No '$'. Just:
export LD_RUN_PATH
Make sure also run at this point:
make
Awesome! Thanks Graham!
Both modules installed successfully and virtualenv too. At first apache
wouldnt start but after restarting computer it works too now.
This didnt fix my original problem (
http://stackoverflow.com/questions/11382024/python-version-virtualenvwrapper-and-django),
but at
Sort of looks like the virtual environment you are pointing mod_wsgi
at was constructed using Python 2.7.2 and not Python 2.7.3.
Try some of the checks starting at:
http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation#Python_Shared_Library
Graham
On 9 July 2012 20:59, Alan Kesselmann
Hmmm..
ldd /opt/bin/python
prints out :
alan@alan:/opt/lib/python2.7$ ldd /opt/bin/python
linux-vdso.so.1 = (0x7fff4818c000)
libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7f6bf236e000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f6bf212d000)
libc.so.6 =
On 9 July 2012 21:39, Alan Kesselmann alan.kesselm...@gmail.com wrote:
Hmmm..
ldd /opt/bin/python
prints out :
alan@alan:/opt/lib/python2.7$ ldd /opt/bin/python
linux-vdso.so.1 = (0x7fff4818c000)
libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7f6bf236e000)
libpthread.so.0
alan@alan:/usr/lib/apache2/modules$ ldd mod_wsgi.so
linux-vdso.so.1 = (0x7fff497ff000)
libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7fdc404d5000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fdc40294000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6
The problem is that your Python installation was not configured to
install a shared library for Python. That is, when 'configure' was run
in Python source code when it was being installed, the
'--enable-shared' option was not used.
If you are using a binary Python installation then there isn't
18 matches
Mail list logo
