For the life of me I can't get my little puller zeromq script to get
anything from my local uwsgi server. The puller script works when I push
to it with another script, but I get nothing from my uwsgi server. Im on
uwsgi 1.4.6
In my .ini file:
...
log-zeromq = tcp://127.0.0.1:9191
My puller script (taken pretty much directly from the example):
import zmq
ctx = zmq.Context()
puller = ctx.socket(zmq.PULL)
puller.bind("tcp://127.0.0.1:9191")
while True:
message = puller.recv()
print message,
On Tue, Jun 4, 2013 at 11:35 AM, <[email protected]> wrote:
> Send uWSGI mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of uWSGI digest..."
>
>
> Today's Topics:
>
> 1. new redis router plugin (Roberto De Ioris)
> 2. SIGHUP just shutting down server instead of restarting
> (Tim Tisdall)
> 3. Re: SIGHUP just shutting down server instead of restarting
> (Roberto De Ioris)
> 4. Re: SIGHUP just shutting down server instead of restarting
> (Tim Tisdall)
> 5. Re: SIGHUP just shutting down server instead of restarting
> (Roberto De Ioris)
> 6. Re: SIGHUP just shutting down server instead of restarting
> (Tim Tisdall)
> 7. Re: SIGHUP just shutting down server instead of restarting
> (Roberto De Ioris)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 4 Jun 2013 13:27:34 +0200
> From: "Roberto De Ioris" <[email protected]>
> To: [email protected]
> Subject: [uWSGI] new redis router plugin
> Message-ID:
> <[email protected]>
> Content-Type: text/plain;charset=utf-8
>
>
> Hi, just in time for 1.9.12 i have added a redis router plugin.
>
> It exposes 4 commands:
>
> "redis" get an item from a redis server:
>
> route = /foobar redis:addr=127.0.0.1:6372,key=/foobar
>
> "redis-continue" as "redis" but continue to the next rule
>
> "redisstore/redis-store" store the output to a redis item
>
> route = /cacheme redisstore:addr=127.0.0.1:6372,key=mykey
>
>
> the plugin is builtin by default
>
> --
> Roberto De Ioris
> http://unbit.it
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 4 Jun 2013 12:03:55 -0400
> From: Tim Tisdall <[email protected]>
> To: uWSGI developers and users list <[email protected]>
> Subject: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <
> cagxywpy2pxdq73ujv4g6632gdwzs818zxszaz-k6necbmby...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I'm having a strange issue where my one server is simply shutting off when
> getting a SIGHUP instead of gracefully restarting like it's supposed to.
> I'm using version 1.9.11 . The ones that are working as expected are an
> older version.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.unbit.it/pipermail/uwsgi/attachments/20130604/efe97f4c/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 4 Jun 2013 18:06:16 +0200
> From: "Roberto De Ioris" <[email protected]>
> To: "uWSGI developers and users list" <[email protected]>
> Subject: Re: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <[email protected]>
> Content-Type: text/plain;charset=utf-8
>
>
> > I'm having a strange issue where my one server is simply shutting off
> when
> > getting a SIGHUP instead of gracefully restarting like it's supposed to.
> > I'm using version 1.9.11 . The ones that are working as expected are an
> > older version.
> > _______________________________________________
> > uWSGI mailing list
> > [email protected]
> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> >
>
> Can you report your full config ?
>
> --
> Roberto De Ioris
> http://unbit.it
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 4 Jun 2013 12:17:52 -0400
> From: Tim Tisdall <[email protected]>
> To: uWSGI developers and users list <[email protected]>
> Subject: Re: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <
> cagxywpagaq2aibgycyweuyqg-d2ey2-v6dq_+j91zyz7-ea...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Here's my init script (you can see the arguments passed on the $arg
> variable):
>
> #! /bin/bash
> ### BEGIN INIT INFO
> # Provides: uwsgi_bloodhound
> # Required-Start: $local_fs $remote_fs $networking
> # Required-Stop: $local_fs $remote_fs $networking
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> # Short-Description: Starts uwsgi_bloodhound
> # Description: Starts and stops uwsgi_bloodhound as needed
> ### END INIT INFO
> # /etc/init.d/uwsgi_bloodhound
> #
>
> daemon="/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/uwsgi"
> pid="/var/run/uwsgi/bloodhound.pid"
> args="-s /var/run/uwsgi/bloodhound.sock --uid bloodhound --gid www-data
> --pidfile $pid --vacuum --daemonize /var/log/uwsgi/bloodhound.log -C -w
> trac.web.main:dispatch_request --env
> TRAC_ENV=/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/main"
>
> # Carry out specific functions when asked to by the system
> case "$1" in
> start)
> echo "Starting uwsgi_bloodhound"
> start-stop-daemon -p $pid --start --exec $daemon -- $args
> ;;
> stop)
> echo "Stopping script uwsgi_bloodhound"
> start-stop-daemon --signal QUIT -p $pid --stop $daemon -- $args
> ;;
> reload | restart)
> echo "Restarting worker threads"
> kill -HUP $(cat $pid)
> ;;
> *)
> echo "Usage: /etc/init.d/uwsgi_bloodhound {start|stop|reload}"
> exit 1
> ;;
> esac
>
> exit 0
>
>
> On Tue, Jun 4, 2013 at 12:06 PM, Roberto De Ioris <[email protected]>
> wrote:
>
> >
> > > I'm having a strange issue where my one server is simply shutting off
> > when
> > > getting a SIGHUP instead of gracefully restarting like it's supposed
> to.
> > > I'm using version 1.9.11 . The ones that are working as expected are
> an
> > > older version.
> > > _______________________________________________
> > > uWSGI mailing list
> > > [email protected]
> > > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> > >
> >
> > Can you report your full config ?
> >
> > --
> > Roberto De Ioris
> > http://unbit.it
> > _______________________________________________
> > uWSGI mailing list
> > [email protected]
> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.unbit.it/pipermail/uwsgi/attachments/20130604/38faf3f6/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Tue, 4 Jun 2013 18:23:12 +0200
> From: "Roberto De Ioris" <[email protected]>
> To: "uWSGI developers and users list" <[email protected]>
> Subject: Re: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <[email protected]>
> Content-Type: text/plain;charset=utf-8
>
>
> > Here's my init script (you can see the arguments passed on the $arg
> > variable):
> >
> > #! /bin/bash
> > ### BEGIN INIT INFO
> > # Provides: uwsgi_bloodhound
> > # Required-Start: $local_fs $remote_fs $networking
> > # Required-Stop: $local_fs $remote_fs $networking
> > # Default-Start: 2 3 4 5
> > # Default-Stop: 0 1 6
> > # Short-Description: Starts uwsgi_bloodhound
> > # Description: Starts and stops uwsgi_bloodhound as needed
> > ### END INIT INFO
> > # /etc/init.d/uwsgi_bloodhound
> > #
> >
> > daemon="/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/uwsgi"
> > pid="/var/run/uwsgi/bloodhound.pid"
> > args="-s /var/run/uwsgi/bloodhound.sock --uid bloodhound --gid www-data
> > --pidfile $pid --vacuum --daemonize /var/log/uwsgi/bloodhound.log -C -w
> > trac.web.main:dispatch_request --env
> > TRAC_ENV=/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/main"
> >
> > # Carry out specific functions when asked to by the system
> > case "$1" in
> > start)
> > echo "Starting uwsgi_bloodhound"
> > start-stop-daemon -p $pid --start --exec $daemon -- $args
> > ;;
> > stop)
> > echo "Stopping script uwsgi_bloodhound"
> > start-stop-daemon --signal QUIT -p $pid --stop $daemon -- $args
> > ;;
> > reload | restart)
> > echo "Restarting worker threads"
> > kill -HUP $(cat $pid)
> > ;;
> > *)
> > echo "Usage: /etc/init.d/uwsgi_bloodhound {start|stop|reload}"
> > exit 1
> > ;;
> > esac
> >
> > exit 0
> >
> >
>
>
> Ok, can you report the logs in /var/log/uwsgi/bloodhound.log when you send
> the HUP ?
>
>
> --
> Roberto De Ioris
> http://unbit.it
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 4 Jun 2013 12:32:36 -0400
> From: Tim Tisdall <[email protected]>
> To: uWSGI developers and users list <[email protected]>
> Subject: Re: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <
> cagxywpbx_ew0rez9f-juurb7wbej+n9u4eickqnhb1sz24v...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Here it is... (not much to see):
>
> Gracefully killing worker 1 (pid: 8468)...
> VACUUM: unix socket /var/run/uwsgi/bloodhound.sock removed.
>
>
>
> On Tue, Jun 4, 2013 at 12:23 PM, Roberto De Ioris <[email protected]>
> wrote:
>
> >
> > > Here's my init script (you can see the arguments passed on the $arg
> > > variable):
> > >
> > > #! /bin/bash
> > > ### BEGIN INIT INFO
> > > # Provides: uwsgi_bloodhound
> > > # Required-Start: $local_fs $remote_fs $networking
> > > # Required-Stop: $local_fs $remote_fs $networking
> > > # Default-Start: 2 3 4 5
> > > # Default-Stop: 0 1 6
> > > # Short-Description: Starts uwsgi_bloodhound
> > > # Description: Starts and stops uwsgi_bloodhound as needed
> > > ### END INIT INFO
> > > # /etc/init.d/uwsgi_bloodhound
> > > #
> > >
> > > daemon="/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/uwsgi"
> > > pid="/var/run/uwsgi/bloodhound.pid"
> > > args="-s /var/run/uwsgi/bloodhound.sock --uid bloodhound --gid www-data
> > > --pidfile $pid --vacuum --daemonize /var/log/uwsgi/bloodhound.log -C -w
> > > trac.web.main:dispatch_request --env
> > > TRAC_ENV=/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/main"
> > >
> > > # Carry out specific functions when asked to by the system
> > > case "$1" in
> > > start)
> > > echo "Starting uwsgi_bloodhound"
> > > start-stop-daemon -p $pid --start --exec $daemon -- $args
> > > ;;
> > > stop)
> > > echo "Stopping script uwsgi_bloodhound"
> > > start-stop-daemon --signal QUIT -p $pid --stop $daemon -- $args
> > > ;;
> > > reload | restart)
> > > echo "Restarting worker threads"
> > > kill -HUP $(cat $pid)
> > > ;;
> > > *)
> > > echo "Usage: /etc/init.d/uwsgi_bloodhound {start|stop|reload}"
> > > exit 1
> > > ;;
> > > esac
> > >
> > > exit 0
> > >
> > >
> >
> >
> > Ok, can you report the logs in /var/log/uwsgi/bloodhound.log when you
> send
> > the HUP ?
> >
> >
> > --
> > Roberto De Ioris
> > http://unbit.it
> > _______________________________________________
> > uWSGI mailing list
> > [email protected]
> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.unbit.it/pipermail/uwsgi/attachments/20130604/bfee909c/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 7
> Date: Tue, 4 Jun 2013 20:38:56 +0200
> From: "Roberto De Ioris" <[email protected]>
> To: "uWSGI developers and users list" <[email protected]>
> Subject: Re: [uWSGI] SIGHUP just shutting down server instead of
> restarting
> Message-ID:
> <[email protected]>
> Content-Type: text/plain;charset=utf-8
>
>
> > Here it is... (not much to see):
> >
> > Gracefully killing worker 1 (pid: 8468)...
> > VACUUM: unix socket /var/run/uwsgi/bloodhound.sock removed.
> >
> >
>
>
> Sorry, just noted now the master is missing. Without it no graceful reload
> could be accomplished
>
>
> >
> > On Tue, Jun 4, 2013 at 12:23 PM, Roberto De Ioris <[email protected]>
> > wrote:
> >
> >>
> >> > Here's my init script (you can see the arguments passed on the $arg
> >> > variable):
> >> >
> >> > #! /bin/bash
> >> > ### BEGIN INIT INFO
> >> > # Provides: uwsgi_bloodhound
> >> > # Required-Start: $local_fs $remote_fs $networking
> >> > # Required-Stop: $local_fs $remote_fs $networking
> >> > # Default-Start: 2 3 4 5
> >> > # Default-Stop: 0 1 6
> >> > # Short-Description: Starts uwsgi_bloodhound
> >> > # Description: Starts and stops uwsgi_bloodhound as needed
> >> > ### END INIT INFO
> >> > # /etc/init.d/uwsgi_bloodhound
> >> > #
> >> >
> >> > daemon="/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/uwsgi"
> >> > pid="/var/run/uwsgi/bloodhound.pid"
> >> > args="-s /var/run/uwsgi/bloodhound.sock --uid bloodhound --gid
> >> www-data
> >> > --pidfile $pid --vacuum --daemonize /var/log/uwsgi/bloodhound.log -C
> >> -w
> >> > trac.web.main:dispatch_request --env
> >> > TRAC_ENV=/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/main"
> >> >
> >> > # Carry out specific functions when asked to by the system
> >> > case "$1" in
> >> > start)
> >> > echo "Starting uwsgi_bloodhound"
> >> > start-stop-daemon -p $pid --start --exec $daemon -- $args
> >> > ;;
> >> > stop)
> >> > echo "Stopping script uwsgi_bloodhound"
> >> > start-stop-daemon --signal QUIT -p $pid --stop $daemon --
> >> $args
> >> > ;;
> >> > reload | restart)
> >> > echo "Restarting worker threads"
> >> > kill -HUP $(cat $pid)
> >> > ;;
> >> > *)
> >> > echo "Usage: /etc/init.d/uwsgi_bloodhound {start|stop|reload}"
> >> > exit 1
> >> > ;;
> >> > esac
> >> >
> >> > exit 0
> >> >
> >> >
> >>
> >>
> >> Ok, can you report the logs in /var/log/uwsgi/bloodhound.log when you
> >> send
> >> the HUP ?
> >>
> >>
> >> --
> >> Roberto De Ioris
> >> http://unbit.it
> >> _______________________________________________
> >> uWSGI mailing list
> >> [email protected]
> >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> >>
> > _______________________________________________
> > uWSGI mailing list
> > [email protected]
> > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> >
>
>
> --
> Roberto De Ioris
> http://unbit.it
>
>
> ------------------------------
>
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
>
> End of uWSGI Digest, Vol 45, Issue 3
> ************************************
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
