On 14 April 2010 15:25, MMRUser <[email protected]> wrote:
> I installed apache with yum.. and I'm not sure whether it split apxs,
> even it split apxs from within the installation it should be in my
> system correct me if I'm wrong.. and mod_wsgi should detect it.
> Should I install apache-devel package it includes apxs see here:http://
> rpm.pbone.net/index.php3/stat/6/idpl/3383565/dir/redhat_5.x/com/apache-
> devel-1.3.4-1.i386.rpm
>
> /usr/sbin/apxs

You have to have apache-devel anyway.

Sounds like you should remove that other apxs package, then install
apache-devel.

The apache-devel package may still probably want some version of perl
for apxs to run.

Don't you have any perl version installed?

Graham

> On Apr 14, 10:35 am, Graham Dumpleton <[email protected]>
> wrote:
>> Unless they package it strangely, you wouldn't need to install a
>> separate 'apxs' package, it should be part of Apache dev package.
>>
>> Has RedHat split 'apxs' out of the Apache development package?
>>
>> Anyone know?
>>
>> Graham
>>
>> On 14 April 2010 14:27, MMRUser <[email protected]> wrote:
>>
>> > New problem arises, I tried to install apxs 2 (http://rpm.pbone.net/
>> > index.php3/stat/4/idpl/4434034/com/apache-apxs-2.2.4-1.i386.rpm.html)
>> > an as a dependency it requires perl-base (http://rpm.pbone.net/
>> > index.php3/stat/4/idpl/12070642/dir/redhat_el_5/com/perl-
>> > base-2.12-1.el5.rf.noarch.rpm.html) I installed it, but when I run the
>> > apxs still it gives me an error
>>
>> >  warning: apache-apxs-2.2.4-1.i386.rpm: Header V3 DSA signature:
>> > NOKEY, key ID 1bbd5459
>> > error: Failed dependencies:
>> >        perl-base >= 0:5.004 is needed by apache-apxs-2.2.4-1.i386
>>
>> > On Apr 14, 8:04 am, Graham Dumpleton <[email protected]>
>> > wrote:
>> >> On 14 April 2010 00:40, Carl Nobile <[email protected]> wrote:
>>
>> >> > You will have to recompile all the dependencies that use python
>> >> > yourself. DO NOT use RPM packages, this includes mod_wsgi. REMOVE all
>> >> > python dependent RPMs from your system and download the source and
>> >> > start compiling everything. There may not be all that many, you may
>> >> > only need to compile mod_wsgi depending on what you have installed.
>> >> > Make sure you do not have mod_python installed anywhere on the box.
>>
>> >> It should be made very clear that one should not remove the default
>> >> Python that the operating system ships with. This is because as I
>> >> understand it RedHat has various system tools which rely on that
>> >> specific version and removing it will cause them to break.
>>
>> >> Someone can correct me, but my understanding is that RPMs available from:
>>
>> >>  http://iuscommunity.org/packages/
>>
>> >> allow one to install both Python and mod_wsgi in such a way as to not
>> >> conflict with the operating system Python installation. Specifically,
>> >> the RPM for mod_wsgi is dependent on a IUS Python RPM which doesn't
>> >> clash with the system one and is installed into different area.
>>
>> >>http://dl.iuscommunity.org/pub/ius/stable/Redhat/5/SRPMS/repoview/pyt......
>>
>> >> Graham
>>
>> >> > ~Carl
>>
>> >> > On Tue, Apr 13, 2010 at 10:22 AM, MMRUser <[email protected]> 
>> >> > wrote:
>> >> >> So is there any way getting around this, I need python 2.6 for some
>> >> >> dependency reasons (with some packages require)..
>>
>> >> >> On Apr 13, 7:54 pm, Clodoaldo Neto <[email protected]> wrote:
>> >> >>> 2010/4/13 MMRUser <[email protected]>:
>>
>> >> >>> > ldd mod_wsgi.so out puts :
>>
>> >> >>> >        libpython2.4.so.1.0 => /usr/lib64/libpython2.4.so.1.0
>> >> >>> > (0x00002b6f95177000)
>> >> >>> >        libpthread.so.0 => /lib64/libpthread.so.0 
>> >> >>> > (0x00002b6f954a9000)
>> >> >>> >        libdl.so.2 => /lib64/libdl.so.2 (0x00002b6f956c4000)
>> >> >>> >        libutil.so.1 => /lib64/libutil.so.1 (0x00002b6f958c9000)
>> >> >>> >        libm.so.6 => /lib64/libm.so.6 (0x00002b6f95acc000)
>> >> >>> >        libc.so.6 => /lib64/libc.so.6 (0x00002b6f95d4f000)
>> >> >>> >        /lib64/ld-linux-x86-64.so.2 (0x0000003aaec00000)
>>
>> >> >>> > seems like it's the older version how to correct this one, I used 
>> >> >>> > the
>> >> >>> > rpm "mod_wsgi-3.2-1.el5.x86_64.rpm" to install mos_wsgi is that the
>> >> >>> > wrong rpm ?..
>>
>> >> >>> If you got it fromhttp://codepoint.net/attachments/mod_wsgithenit
>> >> >>> is built against the default Python install: 2.4
>>
>> >> >>> BTW what is so special about Python 2.5/2.6 that some people must
>> >> >>> prove to the world that their servers run it? The Django site says it
>> >> >>> works with Python 2.4. Redhat 5 as it is can run for years without a
>> >> >>> single glitch and I think that is the main goal for a production
>> >> >>> server, stability. Why would someone want to screw that and ask for a
>> >> >>> life of trouble? If their applications where that demanding they would
>> >> >>> not be running Django or any other morbidly obese framework. Why not
>> >> >>> just shift the server maintenance effort to application development?
>> >> >>> The application users will never know what Python version they are
>> >> >>> running or any other technical details.
>>
>> >> >>> I don't know where people is getting the advice to upgrade Python. I
>> >> >>> think it is plain wrong, especially for not experienced server admins.
>>
>> >> >>> Regards, Clodoaldo
>>
>> >> >>> > System:
>> >> >>> > Redhat Enterprise Linux 5.4 (64bit)
>>
>> >> >>> > On Apr 13, 6:49 pm, Graham Dumpleton <[email protected]>
>> >> >>> > wrote:
>> >> >>> >> On 13 April 2010 22:17, MMRUser <[email protected]> wrote:
>>
>> >> >>> >> > I'm getting this error on my server log.... I have two versions 
>> >> >>> >> > of
>> >> >>> >> > Python 2.4 and 2.5 Django is installed in to 2.6 and it's the 
>> >> >>> >> > default
>> >> >>> >> > python on my system, also it can be imported through command 
>> >> >>> >> > line..
>>
>> >> >>> >> > I tried then it raised no module name os
>> >> >>> >> > WSGIPythonHome /usr/local
>>
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [error] Exception 
>> >> >>> >> > exceptions.ImportError:
>> >> >>> >> > 'No module named ate$
>> >> >>> >> > 'import site' failed; use -v for traceback
>>
>> >> >>> >> There is no Python installation under /usr/local of the version 
>> >> >>> >> that
>> >> >>> >> mod_wsgi has been compiled against.
>>
>> >> >>> >> Run:
>>
>> >> >>> >>   ldd mod_wsgi.so
>>
>> >> >>> >> on the .so file that was generated by built process to work out 
>> >> >>> >> which
>> >> >>> >> Python it was compiled against. It possibly isn't the version you 
>> >> >>> >> want
>> >> >>> >> to use.
>>
>> >> >>> >> > Fatal Python error: unexpected exception during garbage 
>> >> >>> >> > collection
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [notice] caught SIGTERM, shutting down
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [notice] suEXEC mechanism enabled
>> >> >>> >> > (wrapper: /usr/sbin/suexec)
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [warn] module wsgi_module is already
>> >> >>> >> > loaded, skipping
>>
>> >> >>> >> You have duplicate LoadModule lines for mod_wsgi. Either you have
>> >> >>> >> listed it twice by accident, or your snippet configuration file is
>> >> >>> >> being included more than once for some reason.
>>
>> >> >>> >> Graham
>>
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [notice] Digest: generating secret for
>> >> >>> >> > digest authentication .$
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [notice] Digest: done
>> >> >>> >> > [Tue Apr 13 12:04:44 2010] [notice] Apache/2.2.3 (Red Hat) 
>> >> >>> >> > configured
>> >> >>> >> > -- resuming normal $
>> >> >>> >> > [Tue Apr 13 12:09:03 2010] [error] [client 127.0.0.1] Directory 
>> >> >>> >> > index
>> >> >>> >> > forbidden by Option$
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] mod_wsgi
>> >> >>> >> > (pid=24108): Target WSGI s$
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] mod_wsgi
>> >> >>> >> > (pid=24108): Exception occ$
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] Traceback 
>> >> >>> >> > (most
>> >> >>> >> > recent call last):
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1]   File 
>> >> >>> >> > "/var/www/
>> >> >>> >> > html/testproject/a$
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1]     import
>> >> >>> >> > django.core.handlers.wsgi
>> >> >>> >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] 
>> >> >>> >> > ImportError: No
>> >> >>> >> > module named django$
>>
>> >> >>> >> > --
>> >> >>> >> > You received this message because you are subscribed to the 
>> >> >>> >> > Google Groups "modwsgi" group.
>> >> >>> >> > To post to this group, send email to [email protected].
>> >> >>> >> > To unsubscribe from this group, send email to 
>> >> >>> >> > [email protected].
>> >> >>> >> > For more options, visit this group 
>> >> >>> >> > athttp://groups.google.com/group/modwsgi?hl=en.
>>
>> >> >>> > --
>> >> >>> > You received this message because you are subscribed to the Google 
>> >> >>> > Groups "modwsgi" group.
>> >> >>> > To post to this group, send email to [email protected].
>> >> >>> > To unsubscribe from this group, send email to 
>> >> >>> > [email protected].
>> >> >>> > For more options, visit this group 
>> >> >>> > athttp://groups.google.com/group/modwsgi?hl=en.
>>
>> >> >> --
>> >> >> You received this message because you are subscribed to the Google 
>> >> >> Groups "modwsgi" group.
>> >> >> To post to this group, send email to [email protected].
>> >> >> To unsubscribe from this group, send email to 
>> >> >> [email protected].
>> >> >> For more options, visit this group 
>> >> >> athttp://groups.google.com/group/modwsgi?hl=en.
>>
>> >> > --
>> >> > -------------------------------------------------------------------------------
>> >> > Carl J. Nobile (Software Engineer)
>> >> > [email protected]
>> >> > -------------------------------------------------------------------------------
>>
>> >> > --
>> >> > You received this message because you are subscribed to the Google 
>> >> > Groups "modwsgi" group.
>> >> > To post to this group, send email to [email protected].
>> >> > To unsubscribe from this group, send email to 
>> >> > [email protected].
>> >> > For more options, visit this group 
>> >> > athttp://groups.google.com/group/modwsgi?hl=en.
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "modwsgi" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to 
>> > [email protected].
>> > For more options, visit this group 
>> > athttp://groups.google.com/group/modwsgi?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "modwsgi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/modwsgi?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to