> 2.0.8 definitely fixed some segfaults on my end.
So far, since September 30 I have not seen any segmentation faults.
Seems that upgrade to 2.0.8 and using %{GLOBAL} solved the problem.
Graham, thank you for the support! :)
--
Maciej Wisniowski
--~--~-~--~~~---~--~--
2008/10/1 Brett Hoerner <[EMAIL PROTECTED]>:
>
> On Tue, Sep 30, 2008 at 4:22 PM, Pigletto <[EMAIL PROTECTED]> wrote:
>> Maybe that is the problem? I'll give a try to newest psycopg2
>
> 2.0.8 definitely fixed some segfaults on my end.
Good to know. The psycopg2 package has always been a bit of a
2008/10/1 Pigletto <[EMAIL PROTECTED]>:
> One more question as I'm a bit confused about WSGIApplicationGroup
> directive. So far I was not using this at all. Does this mean that %
> {GLOBAL} was used implicitly - by default? I only had WSGIProcessGroup
> directives in use.
The default for WSGIApp
On Tue, Sep 30, 2008 at 4:22 PM, Pigletto <[EMAIL PROTECTED]> wrote:
> Maybe that is the problem? I'll give a try to newest psycopg2
2.0.8 definitely fixed some segfaults on my end.
Brett
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Currently I use psycopg2 from the svn - version dated at January 2008.
I've just looked at initd.org's svn and I see there is psycopg2-2.0.8
and in change log from march I found:
2008-03-07 James Henstridge <[EMAIL PROTECTED]>
* psycopg/pqpath.c (_pq_fetch_tuples): Don't call Python AP
I've managed to get segmentation fault (I was just clicking around my
application, I forced few reloads of mod_wsgi by changing wsgi script,
etc.), and I was able to reproduce this few times.
Again, I've connected to it with gdb but this time I've issued command
'share' before 'bt'. Thanks to this
On 30 Wrz, 14:41, "Graham Dumpleton" <[EMAIL PROTECTED]>
wrote:
> What do you get if you run:
>
>ulimit -a
>
> Maybe they have some sort of hard memory limits in place and you are
> hitting that.
Output of ulimit -a is:
---
core file size
What do you get if you run:
ulimit -a
Maybe they have some sort of hard memory limits in place and you are
hitting that.
Graham
2008/9/30 Pigletto <[EMAIL PROTECTED]>:
>
> Now, again, my application is working with the same setup as before
> (without GLOBAL). I don't know why this started w
Now, again, my application is working with the same setup as before
(without GLOBAL). I don't know why this started without segfault now.
Nothing has changed.
I have to mention that the issue that caused I was not able to start
my application today morning was
because my memory was over the limit
2008/9/30 Pigletto <[EMAIL PROTECTED]>:
> After switching to WSGIApplicationGroup %{GLOBAL} my application
> started, but I have few more applications on this apache instance so I
> can't use this kind of setup.
Can you explain to me how WebFaction process/memory limits work?
If you don't have i
Not particularly useful unfortunately.
Next thing would be to determine if crash happens as a result of
import WSGI script file itself, or due to call of WSGI application.
Thus at head of WSGI script file add:
import sys
print >> sys.stderr, "START OF WSGI SCRIPT FILE"
and at end of WSGI s
Today I was not able to start my application as I got segmentation
faults constantly.
I've attached gdb and that is the result:
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212216416 (LWP 29850)]
PyErr_Occurred () at Python/errors.c:80
80
> All I can suggest at this point are:
>
> 1. Disable the background email thread and see if the problem still occurs.
>
> 2. Force application to run in main interpreter by setting:
>
> WSGIApplicationGroup %{GLOBAL}
>
> This will eliminate possibility that problems are caused by a third
> par
2008/9/29 Pigletto <[EMAIL PROTECTED]>:
>> Does your Django application create any background threads to perform
>> processing.
> Yes. I'm using external threads to send e-mail messages.
> Hm... I'll try to perform some actions that will cause e-mails to be
> sent
> and then I'll see whether proce
> Are you using the Python installation and Apache modules that
> WebFaction supplies or have you built any yourself from source code?
I've built Apache 2.2 and mod_wsgi 2.3 myself. Python is webfaction's
python2.5
> Have you installed any third party Python modules yourself? Are you
> running PH
Are you using the Python installation and Apache modules that
WebFaction supplies or have you built any yourself from source code?
Have you installed any third party Python modules yourself? Are you
running PHP in the same Apache installation?
Does your Django application create any background th
16 matches
Mail list logo
