Internal Server Error при настройки логов django?

Question

[devrais]

Выбивает ошибку как добавляю в settings.
settings.py

...
LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'file': {
            'level': 'DEBUG',
            'class': 'logging.FileHandler',
            'filename': 'home/django/pro/djangopt/log/debug.log', # путь до файла
        },
    },
    'loggers': {
        'django': {       #<-- Не совсем понял что это. Вроде как папку которую он будет смотреть(app) или файл.. (ставил blog все равно)-->
            'handlers': ['file'],
            'level': 'DEBUG', 
            'propagate': True,
        },
    },
}
...

Comments

[Евген]

а ошибку чего не приложил?

Answer 1

[Сергей Горностаев]

'filename': '/home/django/pro/djangopt/log/debug.log'

Comments

[devrais]

Все равно ошибка. Мне выше подсказали в логах uWSGI посмотреть но они меня не настраиваются 502 выбивает.

# django.ini file
[uwsgi]

# master
master                  = true

# maximum number of processes
processes               = 10

# the socket (use the full path to be safe)
socket          = /tmp/uwsgi.sock

# with appropriate permissions - *may* be needed
chmod-socket    = 666

# the base directory
chdir           = /home/django/pro/djangopt

# Django's wsgi file
module          = djangopt.wsgi

# the virtualenv
home            = /home/django/.djenv

logto = /home/django/pro/djangopt/log/uwsgi.log

# clear environment on exit
vacuum          = true


# reload uwsgi
touch-reload     = /home/django/pro/djangopt/djangopt/settings.py
touch-reload     = /home/django/pro/djangopt/djangopt/urls.py

[Сергей Горностаев]

devrais, 502-я ошибка чаще всего означает, что uWSGI не запустился.

[devrais]

Сергей Горностаев, буду ща копаться, спасибо. Как разберусь с логами, надеюсь, решу свой основной вопрос +. Все взаимосвязано))

[devrais]

Сергей Горностаев,
При добавлении в settings.py

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'file': {
            'level': 'DEBUG',
            'class': 'logging.FileHandler',
            'filename': '/home/django/pro/djangopt/log/debug.log',
        },
    },
    'loggers': {
        'django': {
            'handlers': ['file'],
            'level': 'DEBUG',
            'propagate': True,
        },
    }
}

Вот что выдает

spawned uWSGI worker 6 (pid: 2655, cores: 1)
spawned uWSGI worker 7 (pid: 2656, cores: 1)
spawned uWSGI worker 8 (pid: 2657, cores: 1)
spawned uWSGI worker 9 (pid: 2658, cores: 1)
spawned uWSGI worker 10 (pid: 2659, cores: 1)
Thu Apr 11 18:24:21 2019 - [emperor] vassal django.ini is ready to accept requests
--- no python application found, check your startup logs for errors ---
[pid: 2652|app: -1|req: -1/1] 176.49.193.179 () {46 vars in 815 bytes} [Thu Apr 11 18:24:24 2019] GET / => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
announcing my loyalty to the Emperor...
Thu Apr 11 18:24:24 2019 - [emperor] vassal django.ini is now loyal
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/2] 176.49.193.179 () {46 vars in 815 bytes} [Thu Apr 11 18:25:17 2019] GET / => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
announcing my loyalty to the Emperor...
Thu Apr 11 18:25:17 2019 - [emperor] vassal django.ini is now loyal
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/3] 157.7.222.32 () {34 vars in 495 bytes} [Thu Apr 11 18:25:44 2019] GET /wp-content/iindex.php?zzz=S8lM1chNMdUwMdXUtAYA => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/4] 157.7.222.32 () {34 vars in 509 bytes} [Thu Apr 11 18:26:33 2019] GET /wp-admin/iinstall-helper.php?zzz=S8lM1chNMdUwMdXUtAYA => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/5] 185.18.149.3 () {34 vars in 507 bytes} [Thu Apr 11 18:26:42 2019] GET /wp-admin/images/iimages.php?zzz=S8lM1chNMdUwMdXUtAYA => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/6] 157.7.222.32 () {34 vars in 501 bytes} [Thu Apr 11 18:27:18 2019] GET /wp-includes/ID3/IID3.php?zzz=S8lM1chNMdUwMdXUtAYA => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
--- no python application found, check your startup logs for errors ---
[pid: 2650|app: -1|req: -1/7] 157.7.222.32 () {34 vars in 509 bytes} [Thu Apr 11 18:27:20 2019] GET /wp-includes/fonts/ffonts.php?zzz=S8lM1chNMdUwMdXUtAYA => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (1 switches on core 0)
--- no python application found, check your startup logs for errors ---

[Сергей Горностаев]

devrais, судя по "no python application found" не запускаются worker'ы. Попытайтесь запустить в консоли сначала devserver, а потом uWSGI с теми же параметрами.

[devrais]

Сергей Горностаев, devserver это же от runserver запуск? Если да, то ошибоки в консоль не выдал. Зайти на страницу не смог(на vds сервер, там 127.0.0.1:8000, может можно как то иначе хз). Запустил через косоль uwsgi --emperor /etc/uwsgi/vassals --uid www-data --gid www-data --master. Выдал

*** Starting uWSGI 2.0.18 (64bit) on [Thu Apr 11 19:00:43 2019] ***
compiled with version: 5.4.0 20160609 on 11 April 2019 09:33:54
os: Linux-4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018
nodename: cs547318
machine: x86_64
clock source: unix
detected number of CPU cores: 1
current working directory: /home/django/pro/djangopt
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
your processes number limit is 1800
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
Python version: 3.5.2 (default, Nov 12 2018, 13:43:14)  [GCC 5.4.0 20160609]
*** starting uWSGI Emperor ***
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from django.ini
*** Starting uWSGI 2.0.18 (64bit) on [Thu Apr 11 19:00:43 2019] ***
compiled with version: 5.4.0 20160609 on 11 April 2019 09:33:54
os: Linux-4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018
nodename: cs547318
machine: x86_64
clock source: unix
detected number of CPU cores: 1
current working directory: /etc/uwsgi/vassals
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
chdir() to /home/django/pro/djangopt
your processes number limit is 1800
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
Python version: 3.5.2 (default, Nov 12 2018, 13:43:14)  [GCC 5.4.0 20160609]
Set PythonHome to /home/django/.djenv
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x1785e60
your mercy for graceful operations on workers is 60 seconds
*** Operational MODE: no-workers ***
spawned uWSGI master process (pid: 3190)
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0xb1f370
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 801944 bytes (783 KB) for 10 cores
*** Operational MODE: preforking ***
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0xb1f370 pid: 3192 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 3192)
Thu Apr 11 19:00:44 2019 - [emperor] vassal django.ini has been spawned
spawned uWSGI worker 1 (pid: 3194, cores: 1)
spawned uWSGI worker 2 (pid: 3195, cores: 1)
spawned uWSGI worker 3 (pid: 3196, cores: 1)
spawned uWSGI worker 4 (pid: 3197, cores: 1)
spawned uWSGI worker 5 (pid: 3198, cores: 1)
spawned uWSGI worker 6 (pid: 3199, cores: 1)
spawned uWSGI worker 7 (pid: 3200, cores: 1)
spawned uWSGI worker 8 (pid: 3201, cores: 1)
Thu Apr 11 19:00:44 2019 - [emperor] vassal django.ini is ready to accept requests
spawned uWSGI worker 9 (pid: 3202, cores: 1)
spawned uWSGI worker 10 (pid: 3203, cores: 1)

п.с На всякий случай.
п.с.с Я настроил nginx+uwsgi+supervisor все работает, но при добавление в settings.py (logging) выдает ошибку на странице Internal Server Error и в логах uwsgi выше.

[Сергей Горностаев]

devrais, под вашей учёткой ошибок нет, значит высока вероятность, что у той учётки, под которой должен запускаться uwsgi, нет доступа к /home/django/pro/djangopt/log/debug.log

[devrais]

Сергей Горностаев, Огромное спасибо!!!))) Боже в такой мелочи проблема была)) Самое странное что он другие логи видет uwsgi а debug не хотел ШОК! Я бы хрен бы догадался)

Answer 2

[Keofaste]

Добавить "/" в начало пути, проверить наличие самой папки "/home/django/pro/djangopt/log/" и права на запись.