it seems you already answered your own question, the old version have a bug
that causes segfault, consider upgrading
On Wed, Jan 9, 2019 at 11:08 PM Thomas-James Goin
wrote:
> I was referred to this mailing list by a coworker to ask for some help on
> a segfaulting issue I’m seeing with uwsgi.
Which old version do you mean? The libc6 library, the uwsgi version, or the
python2.7 library version(s)?
—
James Goin | Software Engineer, Liberator Squad
> On Jan 10, 2019, at 4:15 AM, Avraham Serour wrote:
>
> it seems you already answered your own question, the old version have a bug
I meant in general, the version of the stuff you posted is different, no
surprise you have different behavior
maybe it is the python minor version, my gut blames libc, honestly I would
pull my son ear if I caught him using ubuntu that old
On Thu, Jan 10, 2019 at 3:20 PM Thomas-James Goin
wrote:
I don't use django, but can you wrap the import statement with a try/catch
and print out additional debug information when it fires?
Things like the uwsgi environ or and nginx or python environment variables
you can get.
On Thu, Jan 10, 2019 at 6:22 AM tk wrote:
>
>
> Le 10/01/2019 à 9:19 AM,
i dont know... what Django version are you using? I have no problems
running my sites with Django 1.11.x, django-hotsauce and uWSGI.
Cheers,
tk
Le 05/01/2019 à 4:01 PM, Larry Martell a écrit :
I am having an odd interment django problem. I have an app which is
deployed at 30 different sites,
On Thu, Jan 10, 2019 at 3:15 AM tk wrote:
>
> i dont know... what Django version are you using? I have no problems
> running my sites with Django 1.11.x, django-hotsauce and uWSGI.
I have both 1.9 and 2.0 and it happens with both.
>
> Cheers,
>
> tk
>
> Le 05/01/2019 à 4:01 PM, Larry Martell a
Le 10/01/2019 à 9:19 AM, Larry Martell a écrit :
I have both 1.9 and 2.0 and it happens with both.
Django 1.9 is quite old and probably no longer supported. You should
upgrade to Django 1.11.x for best results. I never tried seriously
Django 2.0 yet. :-)
tk
Le 05/01/2019 à 4:01 PM,
Yeah, with the environment I’m operating in I don’t exactly have a choice on
that (yet). We’re evaluating putting the application in-question into a Docker
container and running it that way, but we haven’t quite gotten there yet.
I’m going to try upgrading to uwsgi 2.0.17.1 on a test host and
Interesting thing to note: I switched to uwsgi 2.0.17.1 and encountered a
slightly longer segmentation fault stack trace:
—
!!! uWSGI process 32449 got Segmentation Fault !!!
*** backtrace of 32449 ***
/SCRUBBED/BINARY/PATH/bin/uwsgi(uwsgi_backtrace+0x2e) [0x46b54e]
>
> However, after moving from kernel version 4.4.0-134-generic over to
> 3.13.0-164-generic, the segfaults stopped. I’m wondering if there’s a
> memory management bug somewhere in the mix. Anyone have any ideas on how
> I might be able to track this back and provide a definitive bug report?
>
You’re 100% right. So I ended-up discovering three things:
- The “new” hosts we’re migrating to that were having the problems had 1/4 the
memory they ideally should have had
- The segmentation faults were caused by the Linux oom-killer coming in and
killing the child processes to try and
11 matches
Mail list logo
