All geek questions in one place

Why can't I start my server for guns? "Used compound"

Any ideas why my gun server doesn't start?

jeffy@originaldjangster :~$ sudo /home/jeffy/django_files/django_test_venv/bin/gunicorn -c /home/jeffy/django_files/django_test_venv/gunicorn_config.py django_test.wsgi Connection in use: ('127.0.0.1', 8001) Retrying in 1 second. Connection in use: ('127.0.0.1', 8001) Retrying in 1 second. Connection in use: ('127.0.0.1', 8001) Retrying in 1 second. Connection in use: ('127.0.0.1', 8001) Retrying in 1 second. Connection in use: ('127.0.0.1', 8001) Retrying in 1 second. Can't connect to ('127.0.0.1', 8001) jeffy@originaldjangster :~$

nginx listens for http://104.131.200.120/ and goes to gunicorn, which listens for 127.0.0.1. I'm on Ubuntu 14.

I have listed all the processes to make sure that the machine gun is already running:

 jeffy@originaldjangster :~$ ps -a PID TTY TIME CMD 7653 pts/1 00:00:00 ps jeffy@originaldjangster :~$ ps PID TTY TIME CMD 7249 pts/1 00:00:00 bash 7654 pts/1 00:00:00 ps jeffy@originaldjangster :~$ ps -A PID TTY TIME CMD 1 ? 00:00:02 init 2 ? 00:00:00 kthreadd 3 ? 00:00:00 ksoftirqd/0 5 ? 00:00:00 kworker/0:0H 6 ? 00:00:00 kworker/u2:0 7 ? 00:00:00 rcu_sched 8 ? 00:00:00 rcu_bh 9 ? 00:00:00 migration/0 10 ? 00:00:00 watchdog/0 11 ? 00:00:00 khelper 12 ? 00:00:00 kdevtmpfs 13 ? 00:00:00 netns 14 ? 00:00:00 writeback 15 ? 00:00:00 kintegrityd 16 ? 00:00:00 bioset 17 ? 00:00:00 kworker/u3:0 18 ? 00:00:00 kblockd 19 ? 00:00:00 ata_sff 20 ? 00:00:00 khubd 21 ? 00:00:00 md 22 ? 00:00:00 devfreq_wq 23 ? 00:00:08 kworker/0:1 24 ? 00:00:00 khungtaskd 25 ? 00:00:00 kswapd0 26 ? 00:00:00 ksmd 27 ? 00:00:00 fsnotify_mark 28 ? 00:00:00 ecryptfs-kthrea 29 ? 00:00:00 crypto 41 ? 00:00:00 kthrotld 44 ? 00:00:00 scsi_eh_0 45 ? 00:00:00 scsi_eh_1 66 ? 00:00:00 deferwq 67 ? 00:00:00 charger_manager 120 ? 00:00:01 jbd2/vda-8 121 ? 00:00:00 ext4-rsv-conver 271 ? 00:00:00 upstart-udev-br 275 ? 00:00:00 systemd-udevd 322 ? 00:00:00 dbus-daemon 349 ? 00:00:00 kpsmoused 351 ? 00:00:00 kworker/0:2 356 ? 00:00:00 systemd-logind 358 ? 00:00:00 rsyslogd 387 ? 00:00:00 kvm-irqfd-clean 624 ? 00:00:00 upstart-file-br 704 ? 00:00:00 upstart-socket- 758 tty4 00:00:00 getty 761 tty5 00:00:00 getty 767 tty2 00:00:00 getty 768 tty3 00:00:00 getty 770 tty6 00:00:00 getty 794 ? 00:00:00 sshd 800 ? 00:00:00 acpid 802 ? 00:00:00 cron 804 ? 00:00:00 atd 853 ? 00:00:01 postgres 855 ? 00:00:00 postgres 856 ? 00:00:01 postgres 857 ? 00:00:01 postgres 858 ? 00:00:02 postgres 859 ? 00:00:02 postgres 903 ? 00:00:17 supervisord 961 tty1 00:00:00 getty 982 ? 00:00:00 kauditd 1266 ? 00:00:07 kworker/u2:1 3027 ? 00:00:00 kworker/u3:1 3230 ? 00:00:00 sudo 3231 ? 00:00:01 gunicorn 7014 ? 00:00:00 gunicorn 7115 ? 00:00:00 sshd 7192 ? 00:00:00 sshd 7193 ? 00:00:00 sftp-server 7200 ? 00:00:00 sshd 7248 ? 00:00:00 sshd 7249 pts/1 00:00:00 bash 7610 ? 00:00:00 nginx 7613 ? 00:00:00 nginx 7614 ? 00:00:00 nginx 7615 ? 00:00:00 nginx 7616 ? 00:00:00 nginx 7649 ? 00:00:00 sshd 7650 ? 00:00:00 sshd 7655 pts/1 00:00:00 ps

There are two lines of fire:

  3231 ? 00:00:01 gunicorn 7014 ? 00:00:00 gunicorn

I tried to kill these two processes, but, for example, when bringing them to the forefront with fg 3231 he says "there is no such task."

Someone suggested trying netstat -aWn --programs | grep 80 netstat -aWn --programs | grep 80 . Here is the result that I do not understand

 jeffy@originaldjangster :~$ sudo netstat -aWn --programs | grep 80 tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 3231/python3.4 unix 2 [ ACC ] STREAM LISTENING 8911 800/acpid /var/run/acpid.socket unix 2 [ ] DGRAM 8908 800/acpid

Any ideas what causes this connect-to-use error? Thanks.

+6
source share
2 answers

Turns out I just need sudo kill 3231 and sudo kill 7014 . I thought incorrectly that at first they had to be brought to the fore. The fact that the processes could not be seen until I used the capital option A ( ps -A ) misleads me that they were somehow special.

The server was working (in the foreground) when I was sleeping in front of my wife. She left the computer before going to bed.

Ubuntu and gunicorn Newbie. Can you tell me?

+5
source

I also ran into the same problem ... Do not try to run gunicorn from su . Just change the user and try again.

0
source

Source: https://habr.com/ru/post/973610/

More articles:


All Articles