Results 1 to 4 of 4

Thread: "fatal python error: pyeval_acquirethread null new thread state" in logs of mod_wsgi

  1. #1
    Join Date
    Apr 2007
    Location
    Krasnodar, Russia
    Beans
    92
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Exclamation "fatal python error: pyeval_acquirethread null new thread state" in logs of mod_wsgi

    I've successfully upgraded to 12.10 release, but after reboot this line appeared in logs of Apache and Django:
    Code:
    Fri Oct 19 13:38:43 2012] [info] mod_wsgi (pid=6911): Shutdown requested 'fantomas'.
    [Fri Oct 19 13:38:43 2012] [info] mod_wsgi (pid=6911): Stopping process 'fantomas'.
    Fatal Python error: PyEval_AcquireThread: NULL new thread state
    [Fri Oct 19 13:38:44 2012] [info] mod_wsgi (pid=7136): Attach interpreter ''.
    [Fri Oct 19 13:38:44 2012] [info] mod_wsgi (pid=7137): Attach interpreter ''.
    [Fri Oct 19 13:38:44 2012] [info] mod_wsgi (pid=7134): Attach interpreter ''.
    [Fri Oct 19 13:38:44 2012] [info] mod_wsgi (pid=7135): Attach interpreter ''.
    [Fri Oct 19 13:38:44 2012] [info] mod_wsgi (pid=7138): Attach interpreter ''.
    [Fri Oct 19 13:39:18 2012] [info] mod_wsgi (pid=7135): Create interpreter 'fantomas|'.
    So I have 200 error of Apache:
    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Code:
    python manage.py runserver
    works fine:
    Code:
    voland@django-dev:~/sandbox/fantomas$ python manage.py runserver
    Validating models...
    
    0 errors found
    Django version 1.4.1, using settings 'fantomas.settings'
    Development server is running at http://127.0.0.1:8000/
    Quit the server with CONTROL-C.
    django.wsgi:
    Code:
    import os, sys
    
    sys.path.append('/home/voland/sandbox')
    sys.path.append('/home/voland/sandbox/fantomas')
    os.environ['DJANGO_SETTINGS_MODULE'] = 'fantomas.settings'
    
    import django.core.handlers.wsgi
    application = django.core.handlers.wsgi.WSGIHandler()
    Settings:
    Code:
    WSGIScriptAlias / /home/voland/sandbox/fantomas/deploy/django.wsgi
        
    WSGIDaemonProcess fantomas maximum-requests=200 stack-size=524288
    WSGIProcessGroup fantomas
    What should I do to get my django back to work?
    Blog (in Russian) Microblog (in Russian)
    Member of Ubuntu Russian LoCo Team
    Member of Ubuntu Russian Translators Team

  2. #2
    dino99's Avatar
    dino99 is offline Ubuntu addict and loving it
    Join Date
    Jun 2006
    Location
    Nux Jam
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: "fatal python error: pyeval_acquirethread null new thread state" in logs of mod_w

    have you some packages from ppa(s) ? maybe some conflicts

  3. #3
    Join Date
    Apr 2007
    Location
    Krasnodar, Russia
    Beans
    92
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: "fatal python error: pyeval_acquirethread null new thread state" in logs of mod_w

    No, there are no packages from ppa.
    I've solved problem with server misconfiguration, Django started to work, but I still have this errors in logs
    Blog (in Russian) Microblog (in Russian)
    Member of Ubuntu Russian LoCo Team
    Member of Ubuntu Russian Translators Team

  4. #4
    Join Date
    Sep 2005
    Location
    Washington, DC
    Beans
    31
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Question Re: "fatal python error: pyeval_acquirethread null new thread state" in logs of mod_w

    Quote Originally Posted by Voland View Post
    I've solved problem with server misconfiguration, Django started to work, but I still have this errors in logs
    What was the misconfiguration? I've just started to see the

    Code:
    PyEval_AcquireThread: NULL new thread state
    error, but only occasionally.
    Free software, free speech, free thought
    GNU/Linux, Esperanto, Atheism

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •