I didn't have my uwsgi setup to log. So I did with this command :
So I went to the site to reach the 500 error to see if anything updates and nothing is updated in the log file when I check it.
This is the only thing it logs:
So, it doesn't show anything. Also, at first I was running that command without the --daemonize tag. Since I have I can't kill the server to restart it. Wanted to try to kill it with "kill -9 [process id] " but when I do another process comes in it's place.
On Friday, August 29, 2014 11:59:11 AM UTC-4, amarshall wrote:
-- uwsgi --socket :8001 --wsgi-file wsgi.py --master --processes 5 --threads 2 --daemonize /var/log/uwsgi/lokalapp.log
So I went to the site to reach the 500 error to see if anything updates and nothing is updated in the log file when I check it.
This is the only thing it logs:
*** Starting uWSGI 2.0.6 (64bit) on [Fri Aug 29 15:43:09 2014] ***
compiled with version: 4.8.2 on 24 July 2014 15:50:13
os: Linux-3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014
nodename: web01
machine: x86_64
clock source: unix
detected number of CPU cores: 2
current working directory: /var/www/lokalapp.co
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
your processes number limit is 15802
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)
probably another instance of uWSGI is running on the same address (:8001).
bind(): Address already in use [core/socket.c line 759]
*** Starting uWSGI 2.0.6 (64bit) on [Fri Aug 29 15:45:57 2014] ***
compiled with version: 4.8.2 on 24 July 2014 15:50:13
os: Linux-3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014
nodename: web01
machine: x86_64
clock source: unix
detected number of CPU cores: 2
current working directory: /var/www/lokalapp.co
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
your processes number limit is 15802
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)
probably another instance of uWSGI is running on the same address (:8001).
bind(): Address already in use [core/socket.c line 759]
So, it doesn't show anything. Also, at first I was running that command without the --daemonize tag. Since I have I can't kill the server to restart it. Wanted to try to kill it with "kill -9 [process id] " but when I do another process comes in it's place.
On Friday, August 29, 2014 11:59:11 AM UTC-4, amarshall wrote:
I'm pretty sure my ALLOWED_HOST is setup right to allow all url locations after the main domain. I have not setup the EMAIL to send me notifications upon 500 server error. Will do now. About to check my uwsgi log and post it as well
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3273b9da-e7aa-41b6-a18b-32c0bd95b150%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment