multi process Daphne with supervisor, getting [Errno 88] Socket operation on non-socket
any Solution for this problem? https://stackoverflow.com/questions/60275656/multi-process-daphne-with-supervisor-getting-errno-88-socket-operation-on-non#_=_ -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9e7c6812-b7b2-4411-b66d-d81710a9d346n%40googlegroups.com.
Re: Supervisor FATAl Exited too quickly (process log may have details(About inet_http_server and unix_http_server)
Hi,
add something like --log-file=/var/log/weather_project/gunicorn.log to the
gunicorn command line (and make sure Gunicorn has permission to write to that
directory), and restart the program. The information you need to locate the
problem is usually in that log file.
Regards,
Antonis
Antonis Christofides
http://djangodeployment.com
On 2017-09-09 19:27, Jonathan Cheng wrote:
> I wrote a Django project and I use supervisor with gunicorn
>
>
> |
> /etc/supervisor/conf.d/weather.conf
> |
>
>
>
> |
> [group:weather_station]
> programs=site
>
> [program:site]
> directory=$PROJECT
> command=/home/nhcc/.local/bin/gunicorn -c
> /$PROJECT/weather_station/gunicorn.conf.py -p gunicorn.pod
> weather_station.wsgi
> autostart=true
> autorestart=true
> stdout_logfile=/var/log/supervisor.log
> environment=my-environment-variable
> ~
> |
>
>
>
>
> |
> `sudo supervisorctl reread`
>
>
> `sudo supervisorctl reload`
>
>
> `sudo supervisorctl status`
> |
>
>
> It showed up the error
>
> > weather_station:site FATAL Exited too quickly (process log
> may have details)
>
>
> So I checked out the log file :
>
> |
> `/var/log/supervisor/supervisord.log`
> |
>
>
> > 2017-09-08 17:15:25,000 CRIT Supervisor running as root (no user in
> config file)
> > 2017-09-08 17:15:25,000 WARN Included extra file
> "/etc/supervisor/conf.d/weather.conf" during parsing
> >2017-09-08 17:15:25,007 INFO RPC interface 'supervisor' initialized
> >2017-09-08 17:15:25,008 CRIT Server 'inet_http_server' running without
> any HTTP
> > authentication checking
> > 2017-09-08 17:15:25,008 INFO RPC interface
> > 'supervisor' initialized
> > 2017-09-08 17:15:25,008 CRIT Server 'unix_http_server' running without
> any HTTP authentication checking
> > 2017-09-08 17:15:25,008 INFO supervisord started with pid 32371
> > 2017-09-08 17:15:26,013 INFO spawned: 'site' with pid 32447
> > 2017-09-08 17:15:26,018 INFO exited: site (exit status 127; not
> expected)
> > 2017-09-08 17:15:27,022 INFO spawned: 'site' with pid 32448
> > 2017-09-08 17:15:27,026 INFO exited: site (exit status 127; not
> expected)
> > 2017-09-08 17:15:29,032 INFO spawned: 'site' with pid 32449
> > 2017-09-08 17:15:29,038 INFO exited: site (exit status 127; not
> expected)
> > 2017-09-08 17:15:32,043 INFO spawned: 'site' with pid 32451
> > 2017-09-08 17:15:32,059 INFO exited: site (exit status 127; not
> expected)
> > 2017-09-08 17:15:33,060 INFO gave up: site entered FATAL state, too
> > many start retries too quickly
>
>
>
>
>
>
>
> According to `Included extra file`[the
> solution](https://github.com/Supervisor/supervisor/issues/272)
>
> According to `Server 'unix_http_server' running without any HTTP
> authentication checking`[the
> solution](https://github.com/Supervisor/supervisor/issues/717)
>
> I added two section [unix_http_server] and [inet_http_server]
>
>
>
> |
> [unix_http_server]
> file=/var/run/supervisor.sock ;(the path to the socket file)
> chmod=0766 ;socket file mode (default0700)
> ;chown=nobody:nogroup ;socket file uid:gid owner
> ;username=user ;(defaultisnousername (open server))
> ;password=123 ;(defaultisnopassword (open server))
>
> [inet_http_server] ;inet (TCP)server disabled bydefault
> port=*:9001 ;(ip_address:port specifier,*:port forall iface,
> ;username=user ;(defaultisnousername (open server))
> ;password=123 ;(defaultisnopassword (open server))
>
> |
>
>
>
> This is the current supervisor.conf
>
>
>
> |
> [unix_http_server]
> file=/var/run/supervisor.sock ;(the path to the socket file)
> chmod=0766 ;socket file mode (default0700)
>
> [supervisord]
> logfile=/var/log/supervisor/supervisord.log ;(main log
> file;default$CWD/supervisord.log)
> pidfile=/var/run/supervisord.pid ;(supervisord
> pidfile;defaultsupervisord.pid)
> childlogdir=/var/log/supervisor ;('AUTO'child log
> dir,default$TEMP)
>
> [rpcinterface:supervisor]
> supervisor.rpcinterface_factory
> =supervisor.rpcinterface:make_main_rpcinterface
>
> [supervisorctl]
>
Re: Supervisor FATAl Exited too quickly (process log may have details(About inet_http_server and unix_http_server)
Does that Guniorn command run directly from the command line? What's
gunicorn.pod? Make sure you can start gunicorn outside of supervisor and
then stick that command into conf file.
Cheers,
M
On Sun, 10 Sep 2017 at 2:28 am, Jonathan Cheng <jonathan950...@gmail.com>
wrote:
> I wrote a Django project and I use supervisor with gunicorn
>
>
> /etc/supervisor/conf.d/weather.conf
>
>
>
> [group:weather_station]
> programs=site
>
> [program:site]
> directory=$PROJECT
> command=/home/nhcc/.local/bin/gunicorn -c /$PROJECT/weather_station/
> gunicorn.conf.py -p gunicorn.pod weather_station.wsgi
> autostart=true
> autorestart=true
> stdout_logfile=/var/log/supervisor.log
> environment=my-environment-variable
> ~
>
>
>
>
> `sudo supervisorctl reread`
>
>
> `sudo supervisorctl reload`
>
>
> `sudo supervisorctl status`
>
>
> It showed up the error
>
> > weather_station:site FATAL Exited too quickly (process
> log may have details)
>
>
> So I checked out the log file :
>
> `/var/log/supervisor/supervisord.log`
>
>
> > 2017-09-08 17:15:25,000 CRIT Supervisor running as root (no user in
>> config file)
>> > 2017-09-08 17:15:25,000 WARN Included extra file
>> "/etc/supervisor/conf.d/weather.conf" during parsing
>> >2017-09-08 17:15:25,007 INFO RPC interface 'supervisor' initialized
>> >2017-09-08 17:15:25,008 CRIT Server 'inet_http_server' running without
>> any HTTP
>> > authentication checking
>> > 2017-09-08 17:15:25,008 INFO RPC interface
>> > 'supervisor' initialized
>> > 2017-09-08 17:15:25,008 CRIT Server 'unix_http_server' running without
>> any HTTP authentication checking
>> > 2017-09-08 17:15:25,008 INFO supervisord started with pid 32371
>> > 2017-09-08 17:15:26,013 INFO spawned: 'site' with pid 32447
>> > 2017-09-08 17:15:26,018 INFO exited: site (exit status 127; not
>> expected)
>> > 2017-09-08 17:15:27,022 INFO spawned: 'site' with pid 32448
>> > 2017-09-08 17:15:27,026 INFO exited: site (exit status 127; not
>> expected)
>> > 2017-09-08 17:15:29,032 INFO spawned: 'site' with pid 32449
>> > 2017-09-08 17:15:29,038 INFO exited: site (exit status 127; not
>> expected)
>> > 2017-09-08 17:15:32,043 INFO spawned: 'site' with pid 32451
>> > 2017-09-08 17:15:32,059 INFO exited: site (exit status 127; not
>> expected)
>> > 2017-09-08 17:15:33,060 INFO gave up: site entered FATAL state, too
>> > many start retries too quickly
>>
>>
>>
>
>
>
>
> According to `Included extra file`[the solution](
> https://github.com/Supervisor/supervisor/issues/272)
>
> According to `Server 'unix_http_server' running without any HTTP
> authentication checking`[the solution](
> https://github.com/Supervisor/supervisor/issues/717)
>
> I added two section [unix_http_server] and [inet_http_server]
>
>
>
>[unix_http_server]
> file=/var/run/supervisor.sock ; (the path to the socket file)
> chmod=0766 ; socket file mode (default 0700)
> ;chown=nobody:nogroup ; socket file uid:gid owner
> ;username=user ; (default is no username (open server))
> ;password=123 ; (default is no password (open server))
>
> [inet_http_server] ; inet (TCP) server disabled by default
> port=*:9001; (ip_address:port specifier, *:port for all iface,
> ;username=user ; (default is no username (open server))
> ;password=123 ; (default is no password (open server))
>
>
>
>
> This is the current supervisor.conf
>
>
>
> [unix_http_server]
> file=/var/run/supervisor.sock ; (the path to the socket file)
> chmod=0766 ; socket file mode (default 0700)
>
> [supervisord]
> logfile=/var/log/supervisor/supervisord.log ; (main log file;default
> $CWD/supervisord.log)
> pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default
> supervisord.pid)
> childlogdir=/var/log/supervisor; ('AUTO' child log dir,
> default $TEMP)
>
> [rpcinterface:supervisor]
> supervisor.rpcinterface_factory = supervisor.rpcinterface:
> make_main_rpcinterface
>
> [supervisorctl]
> serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL for a
> unix socket
>
> [inet_http_server] ; inet (TCP) server disabled by default
> port=*:9001;
>
> [include]
> files = /etc/supervisor/*.conf
> files = /etc/supervisor/conf.d/*.conf
>
>
>
>
>
&g
Supervisor FATAl Exited too quickly (process log may have details(About inet_http_server and unix_http_server)
I wrote a Django project and I use supervisor with gunicorn
/etc/supervisor/conf.d/weather.conf
[group:weather_station]
programs=site
[program:site]
directory=$PROJECT
command=/home/nhcc/.local/bin/gunicorn -c /$PROJECT/weather_station/
gunicorn.conf.py -p gunicorn.pod weather_station.wsgi
autostart=true
autorestart=true
stdout_logfile=/var/log/supervisor.log
environment=my-environment-variable
~
`sudo supervisorctl reread`
`sudo supervisorctl reload`
`sudo supervisorctl status`
It showed up the error
> weather_station:site FATAL Exited too quickly (process
log may have details)
So I checked out the log file :
`/var/log/supervisor/supervisord.log`
> 2017-09-08 17:15:25,000 CRIT Supervisor running as root (no user in
> config file)
> > 2017-09-08 17:15:25,000 WARN Included extra file
> "/etc/supervisor/conf.d/weather.conf" during parsing
> >2017-09-08 17:15:25,007 INFO RPC interface 'supervisor' initialized
> >2017-09-08 17:15:25,008 CRIT Server 'inet_http_server' running without
> any HTTP
> > authentication checking
> > 2017-09-08 17:15:25,008 INFO RPC interface
> > 'supervisor' initialized
> > 2017-09-08 17:15:25,008 CRIT Server 'unix_http_server' running without
> any HTTP authentication checking
> > 2017-09-08 17:15:25,008 INFO supervisord started with pid 32371
> > 2017-09-08 17:15:26,013 INFO spawned: 'site' with pid 32447
> > 2017-09-08 17:15:26,018 INFO exited: site (exit status 127; not expected)
> > 2017-09-08 17:15:27,022 INFO spawned: 'site' with pid 32448
> > 2017-09-08 17:15:27,026 INFO exited: site (exit status 127; not expected)
> > 2017-09-08 17:15:29,032 INFO spawned: 'site' with pid 32449
> > 2017-09-08 17:15:29,038 INFO exited: site (exit status 127; not expected)
> > 2017-09-08 17:15:32,043 INFO spawned: 'site' with pid 32451
> > 2017-09-08 17:15:32,059 INFO exited: site (exit status 127; not expected)
> > 2017-09-08 17:15:33,060 INFO gave up: site entered FATAL state, too
> > many start retries too quickly
>
>
>
According to `Included extra file`[the
solution](https://github.com/Supervisor/supervisor/issues/272)
According to `Server 'unix_http_server' running without any HTTP
authentication checking`[the
solution](https://github.com/Supervisor/supervisor/issues/717)
I added two section [unix_http_server] and [inet_http_server]
[unix_http_server]
file=/var/run/supervisor.sock ; (the path to the socket file)
chmod=0766 ; socket file mode (default 0700)
;chown=nobody:nogroup ; socket file uid:gid owner
;username=user ; (default is no username (open server))
;password=123 ; (default is no password (open server))
[inet_http_server] ; inet (TCP) server disabled by default
port=*:9001; (ip_address:port specifier, *:port for all iface,
;username=user ; (default is no username (open server))
;password=123 ; (default is no password (open server))
This is the current supervisor.conf
[unix_http_server]
file=/var/run/supervisor.sock ; (the path to the socket file)
chmod=0766 ; socket file mode (default 0700)
[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default
$CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default
supervisord.pid)
childlogdir=/var/log/supervisor; ('AUTO' child log dir,
default $TEMP)
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:
make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL for a
unix socket
[inet_http_server] ; inet (TCP) server disabled by default
port=*:9001;
[include]
files = /etc/supervisor/*.conf
files = /etc/supervisor/conf.d/*.conf
Then I ran
sudo supervisord -c /etc/supervisor/supervisord.conf
sudo supervisorctl -c /etc/supervisor/supervisord.conf
And I checked the log again
The error is completely be same
Does anyone know why??
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/4a1e659d-93be-4420-b68e-cd04d8188961%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Configurar Supervisor + Gunicorn + Nginx
https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04 On Tuesday, 2 May 2017 20:34:31 UTC+10, Ariel Gavegno wrote: > > Buenas, necesito saber como configurar Supervisor en un servidor Ubuntu, > de un proyecto Django 1.11. > Un ejemplo sería de mucha ayuda. > > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e40ae57f-0069-4bd1-9c6c-7ed0b22dd846%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Configurar Supervisor + Gunicorn + Nginx
Buenas, necesito saber como configurar Supervisor en un servidor Ubuntu, de un proyecto Django 1.11. Un ejemplo sería de mucha ayuda. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/811ff4e4-5a44-47e4-bc39-e9d7d23bfdc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Post - Deploy project Django-Nginx,gunicorn,virtualenv and supervisor
Hi guys in this post i can learn, how to deploy app in server with django :), and i share it with us ! http://michal.karzynski.pl/blog/2013/06/09/django-nginx-gunicorn-virtualenv-supervisor/ -- 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+unsubscr...@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/eba3eb4d-2a09-4d71-98e4-bb64c08a840f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Supervisor alternative on Python 3.3.2?
I'm not sure why I didn't think of that. Thanks! On Thursday, June 5, 2014 11:25:54 PM UTC-5, somecallitblues wrote: > > You can use init instead. > On 06/06/2014 5:09 am, "Kwest Ambani" <kwest...@gmail.com > > wrote: > >> Anyone know an alternative for Supervisor? I need something to keep >> Gunicorn running in the background. My server is running Python 3.3.2. with >> Nginx serving only static files. >> >> -- >> 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...@googlegroups.com . >> To post to this group, send email to django...@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/42356d62-79cd-415f-8890-f9a4a903deeb%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/42356d62-79cd-415f-8890-f9a4a903deeb%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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+unsubscr...@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/3070ecbc-d135-446b-9308-f197a64bcd8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Supervisor alternative on Python 3.3.2?
You can use init instead. On 06/06/2014 5:09 am, "Kwest Ambani" <kwestamb...@gmail.com> wrote: > Anyone know an alternative for Supervisor? I need something to keep > Gunicorn running in the background. My server is running Python 3.3.2. with > Nginx serving only static files. > > -- > 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+unsubscr...@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/42356d62-79cd-415f-8890-f9a4a903deeb%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/42356d62-79cd-415f-8890-f9a4a903deeb%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CAHqTbjng3K812YEBTn_78mi9ZgScjVfYA0PBg73GOcf27mgvXQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Supervisor alternative on Python 3.3.2?
Anyone know an alternative for Supervisor? I need something to keep Gunicorn running in the background. My server is running Python 3.3.2. with Nginx serving only static files. -- 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+unsubscr...@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/42356d62-79cd-415f-8890-f9a4a903deeb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: supervisor
Dne 22. 10. 2013 18:24, Diogene Laerce napsal(a): the trick is to add supervisor command that specifically tells the program to NOT daemonize [program:my_uwsgi] command = /usr/local/bin/uwsgi -i /path/to/config.ini autorestart = True user = your_user config.ini: your standard uwsgi config, but NO daemonize=logfile path that works perfectly I'm reloading all the time .. That means that you need to reload for every change in the code source, doesn't it ? There's no over way ? Exactly, the uwsgi has no idea that you edited .py files, you need to reload it. although there is some feature like the django server of autoreload, but just to be safe, you should reload the uwsgi processes by hand. I think I even saw some plugin for supervisor that does this automatically, but I'm not sure... Hoewer on a different note, you should have your dev code separated from production, so you don't change it that often that it would bother you to reload it :) Actually it didn't work for me : all my troubles remained the same. I found another software in the repositories : monit. It works (well I managed to make it work..) and I can even monitor CPU load with it. But I didn't see anyone use it in a django stack, do you know why ? Thanks anyway Never heard of monit... so can't tell you much :) -- 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+unsubscr...@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/5266A78F.5090801%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
the trick is to add supervisor command that specifically tells the program to NOT daemonize [program:my_uwsgi] command = /usr/local/bin/uwsgi -i /path/to/config.ini autorestart = True user = your_user config.ini: your standard uwsgi config, but NO daemonize=logfile path that works perfectly I'm reloading all the time .. That means that you need to reload for every change in the code source, doesn't it ? There's no over way ? Exactly, the uwsgi has no idea that you edited .py files, you need to reload it. although there is some feature like the django server of autoreload, but just to be safe, you should reload the uwsgi processes by hand. I think I even saw some plugin for supervisor that does this automatically, but I'm not sure... Hoewer on a different note, you should have your dev code separated from production, so you don't change it that often that it would bother you to reload it :) Actually it didn't work for me : all my troubles remained the same. I found another software in the repositories : monit. It works (well I managed to make it work..) and I can even monitor CPU load with it. But I didn't see anyone use it in a django stack, do you know why ? Thanks anyway -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce -- 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+unsubscr...@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/5266A6C4.6020109%40yahoo.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
Are you sure you need one ? Well I need to monitor at least uwsgi to keep the site up. I rely now on monit, it seems ok. Like I asked to Lukas, what do you think of it ? uWSGI Emperor is way more capable (in terms of monitoring and management of bad-behaving apps) and easy to manage (just drop files in a directory) Yes I think I saw something like that on my readings but it seemed (on the moment) way over my humble needs : I've got only 1 application to run. By the way, if you cannot use distro-included process managers (upstart or systemd), i find circus a great alternative to suprvisord. I have seen lot of users happy with 'god' too (it is a ruby app) I tried circus : it's nice but there is no much docs on it and I'm quite a newbie at all this. And I just realize now that when you said 'god', you didn't mean 'God'.. :) So I may give a shot later. Thank you -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce -- 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+unsubscr...@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/5266A6A5.9000200%40yahoo.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
> Hi, > > Anyone could share a good process control system software name to use > with uwsgi ? Apart from supervisor, I couldn't make it work : > - can't stop it only kill it > - bug on supervisorctl reload.. Even when using the last version. > > Thank you > Are you sure you need one ? uWSGI Emperor is way more capable (in terms of monitoring and management of bad-behaving apps) and easy to manage (just drop files in a directory) By the way, if you cannot use distro-included process managers (upstart or systemd), i find circus a great alternative to suprvisord. I have seen lot of users happy with 'god' too (it is a ruby app) -- Roberto De Ioris http://unbit.it -- 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+unsubscr...@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/f1a0778bda3a30ab9c9d09522b171797.squirrel%40manage.unbit.it. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
On 10/21/2013 02:51 PM, Diogene Laerce wrote: Thanks for reply. the trick is to add supervisor command that specifically tells the program to NOT daemonize [program:my_uwsgi] command = /usr/local/bin/uwsgi -i /path/to/config.ini autorestart = True user = your_user config.ini: your standard uwsgi config, but NO daemonize=logfile path that works perfectly I'm reloading all the time .. That means that you need to reload for every change in the code source, doesn't it ? There's no over way ? Exactly, the uwsgi has no idea that you edited .py files, you need to reload it. although there is some feature like the django server of autoreload, but just to be safe, you should reload the uwsgi processes by hand. I think I even saw some plugin for supervisor that does this automatically, but I'm not sure... Hoewer on a different note, you should have your dev code separated from production, so you don't change it that often that it would bother you to reload it :) Lukas -- 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+unsubscr...@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/52652245.9040600%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
Thanks for reply. the trick is to add supervisor command that specifically tells the program to NOT daemonize [program:my_uwsgi] command = /usr/local/bin/uwsgi -i /path/to/config.ini autorestart = True user = your_user config.ini: your standard uwsgi config, but NO daemonize=logfile path that works perfectly I'm reloading all the time .. That means that you need to reload for every change in the code source, doesn't it ? There's no over way ? -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce -- 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+unsubscr...@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/52652350.9060707%40yahoo.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: supervisor
On 10/21/2013 02:35 PM, Diogene Laerce wrote: Hi, Anyone could share a good process control system software name to use with uwsgi ? Apart from supervisor, I couldn't make it work : - can't stop it only kill it - bug on supervisorctl reload.. Even when using the last version. Thank you Hi, I'm using supervisor without problems on debian.. the trick is to add supervisor command that specifically tells the program to NOT daemonize [program:my_uwsgi] command = /usr/local/bin/uwsgi -i /path/to/config.ini autorestart = True user = your_user config.ini: your standard uwsgi config, but NO daemonize=logfile path that works perfectly I'm reloading all the time .. -- 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+unsubscr...@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/52651EA2.7000109%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
supervisor
Hi, Anyone could share a good process control system software name to use with uwsgi ? Apart from supervisor, I couldn't make it work : - can't stop it only kill it - bug on supervisorctl reload.. Even when using the last version. Thank you -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce -- 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+unsubscr...@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/52651F8D.9070905%40yahoo.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: ANN: django-supervisor: easy integration between django and supervisord
This is really excellent - thanks for releasing it. -Ethan On Tue, Jun 7, 2011 at 10:51 PM, Ryan Kelly <r...@rfk.id.au> wrote: > > Hi All, > > > I've just released a little experiment in combining the process > management awesomeness of supervisord with the convenience of Django's > management scripts. It's called, funnily enough, django-supervisor: > > http://pypi.python.org/pypi/django-supervisor/ > > > The concept is simple: instead of having supervisord in charge of > Django, why not put Django in charge of supervisord? > > > If you've got a Django project that needs to keep several processes > running at once (e.g. celeryd or celerybeat) then this might be the app > for you. You can: > > * manage all your processes with `python manage.py supervisor`. > > * keep your process definitions and configuration inside your > Django project directory. > > * use Django's template system to construct the supervisord config > file, interpolating environment variables or settings as you need. > > * merge pre-defined configuration files from all the INSTALLED_APPS, > and tweak or override them on a per-project basis. > > * auto-reload all running processes when your code changes >(but only in debug mode of course) > > > All comments, questions, feedback and criticism welcome. I hope you > find it useful. > > > Cheers, > > Ryan > > -- > Ryan Kelly > http://www.rfk.id.au | This message is digitally signed. Please visit > r...@rfk.id.au| http://www.rfk.id.au/ramblings/gpg/ for details > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
ANN: django-supervisor: easy integration between django and supervisord
Hi All, I've just released a little experiment in combining the process management awesomeness of supervisord with the convenience of Django's management scripts. It's called, funnily enough, django-supervisor: http://pypi.python.org/pypi/django-supervisor/ The concept is simple: instead of having supervisord in charge of Django, why not put Django in charge of supervisord? If you've got a Django project that needs to keep several processes running at once (e.g. celeryd or celerybeat) then this might be the app for you. You can: * manage all your processes with `python manage.py supervisor`. * keep your process definitions and configuration inside your Django project directory. * use Django's template system to construct the supervisord config file, interpolating environment variables or settings as you need. * merge pre-defined configuration files from all the INSTALLED_APPS, and tweak or override them on a per-project basis. * auto-reload all running processes when your code changes (but only in debug mode of course) All comments, questions, feedback and criticism welcome. I hope you find it useful. Cheers, Ryan -- Ryan Kelly http://www.rfk.id.au | This message is digitally signed. Please visit r...@rfk.id.au| http://www.rfk.id.au/ramblings/gpg/ for details signature.asc Description: This is a digitally signed message part
