> Le 13 janv. 2015 à 19:25, Django User a écrit :
>
> hello
> i keep getting the following error messages that state mod_wsgi was already
> loaded and segmentation faults. pls. see an example:
>
> [Tue Jan 13 23:46:11 2015] [error]
> /usr/local/lib/python2.7/dist-packages/pytz/__init__.py:29:
Subject: Re: Segmentation fault
Try to update both your python and your mysql<-> python bindings. The libraries
you are using are either incompatible or have a bug.
Good luck
Sexta-feira, 8 de Agosto de 2014 5:21:44 UTC+1, Tianwei Sheng escreveu:
Hi, all,
Recently I constantly met segmen
Try to update both your python and your mysql<-> python bindings. The
libraries you are using are either incompatible or have a bug.
Good luck
Sexta-feira, 8 de Agosto de 2014 5:21:44 UTC+1, Tianwei Sheng escreveu:
>
> Hi, all,
>
> Recently I constantly met segmentation fault for my django serve
> I highly reccomend you to switch to psycopg2 2.0.8
> After I did a switch to this version, I haven't seen any segmentation
> faults since 30 september 2008 (earlier I had them every few days).
Ys! It works! After I'd updated psycopg to version 2.0.8 the
problem just disappeared! It seems to
> Sometimes pages load well but sometimes I get "Internal Server Error"
> at the same URL. In this case I have to reload page once or twice to
> load it properly. I'm using FastCGI and after fault I can see the
> following message in the apache logs:
> "[error] [client 127.0.0.1] FastCGI: incomple
Just to mention: it's appearantly a psycopg2 error. with psycopg1
everything worked fine.
On Aug 25, 10:18 am, kire <[EMAIL PROTECTED]> wrote:
> My site works fine locally mysql, sqlite and postgresql. On the server
> it worked fine om mysql - myisam (well, as long you can speak about
> fine for
What version of django are you using?
Will other commands (like validate or runserver) work?
Is this an existing known-to-work django app, or are you running
something new?
Thanks!
Jeff Anderson
Chris Hoeppner wrote:
> Hi there,
>
> I'm getting a segmentation fault on syncdb. No further output.
On 1/23/07, Rchard Peng <[EMAIL PROTECTED]> wrote:
> Nikolaus Schlemm wrote:
> > > Aha! Not sure why I didn't think of that, but a back and forth
> > > switching php modules on and off eventually led me to mhash.so -
> > > switching off that module solved all my woes.
> > ouch mhash again ... a co
upgrade your MySQL-python to the latest will resolve the problem
Nikolaus Schlemm wrote:
> > Aha! Not sure why I didn't think of that, but a back and forth
> > switching php modules on and off eventually led me to mhash.so -
> > switching off that module solved all my woes.
> ouch mhash again ...
> Aha! Not sure why I didn't think of that, but a back and forth
> switching php modules on and off eventually led me to mhash.so -
> switching off that module solved all my woes.
ouch mhash again ... a couple of months ago that interfered with md5 for some
reason resulting in wrong digests, but
Hi Nikl,
> - have you tried to increase apache's loglevel?
Yes, but the errors were no more verbose.
> - do you have any php-extensions installed? if so, you might want
> to check out
> if php is really the factor by loading it without any extensions.
> if that
> works, try adding them bac
hi James,
> I'm running Ubuntu Edgy Eft, with the following versions (updated to
> the most recent available from apt-get)
> Apache/2.0.55 (Ubuntu) mod_python/3.2.8 Python/2.4.4c1 PHP/5.1.6
> mod_ssl/2.0.55 OpenSSL/0.9.8b
> and Django 0.95.
I'm running pretty much the same combo, but with
12 matches
Mail list logo
