R
R
Rustem Vorozheikin2015-05-14 19:18:01
Django
Rustem Vorozheikin, 2015-05-14 19:18:01

Why doesn't uwsgi work/start?

Good afternoon.
I'm trying to deploy a django project on the server with a bunch of uwsgi + nginx + django.
I do everything according to the tutorial
After the command: uwsgi --http :8000 --wsgi-file test.pywhen you navigate to ip:8000, "Hello world!" should be displayed, but unfortunately this does not happen.
The following is displayed in the console after this command:

*** Starting uWSGI 2.0.10 (64bit) on [Fri May 15 00:11:37 2015] ***
compiled with version: 4.8.2 on 14 May 2015 19:32:19
os: Linux-3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
nodename: ip-172-31-18-24
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 2
current working directory: /home/ubuntu/uwsgi-tutorial/mysite
detected binary path: /home/ubuntu/uwsgi-tutorial/bin/uwsgi
*** WARNING: you are running uWSGI without its master process manager ***
your processes number limit is 31534
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 http bound on :8000 fd 4
spawned uWSGI http 1 (pid: 17621)
uwsgi socket 0 bound to TCP address 127.0.0.1:45470 (port auto-assigned) fd 3
Python version: 2.7.6 (default, Mar 22 2014, 23:03:41)  [GCC 4.8.2]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0xf39450
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 72760 bytes (71 KB) for 1 cores
*** Operational MODE: single process ***
WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0xf39450 pid: 17620 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI worker 1 (and the only) (pid: 17620, cores: 1)

Do not tell me what could be the problem? How to solve it? Any recommendations?
Thanks in advance)

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
sim3x, 2015-05-14
@sim3x

Because

NetRange: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: PRIVATE-ADDRESS-BBLK-RFC1918-IANA-RESERVED

so if you are not on the same network as your host, then you cannot see

S
Sergey, 2015-05-15
@Weidmann

Where are you running this business? What does the browser say?
ping 172.31.18.24
If ip is pinged, then after starting, in the second console:
iptables -L --line-numbers --verbose
netstat -apn | grep8000

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question