[DRE-maint] ruby-json 1.8.3-1 MIGRATED to testing
FYI: The status of the ruby-json source package in Debian's testing distribution has changed. Previous version: 1.8.2-1 Current version: 1.8.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] chef-zero 4.2.2-1 MIGRATED to testing
FYI: The status of the chef-zero source package in Debian's testing distribution has changed. Previous version: 3.1.3-1 Current version: 4.2.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] asciidoctor 1.5.2-2 MIGRATED to testing
FYI: The status of the asciidoctor source package in Debian's testing distribution has changed. Previous version: 1.5.2-1 Current version: 1.5.2-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-bcrypt 3.1.10-1 MIGRATED to testing
FYI: The status of the ruby-bcrypt source package in Debian's testing distribution has changed. Previous version: 3.1.7-2 Current version: 3.1.10-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-cucumber-core 1.1.3-1 MIGRATED to testing
FYI: The status of the ruby-cucumber-core source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.1.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-test-unit 3.1.2-1 MIGRATED to testing
FYI: The status of the ruby-test-unit source package in Debian's testing distribution has changed. Previous version: 3.0.9-3 Current version: 3.1.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-minitest 5.7.0-1 MIGRATED to testing
FYI: The status of the ruby-minitest source package in Debian's testing distribution has changed. Previous version: 5.6.1-1 Current version: 5.7.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-specinfra 2.35.1-1 MIGRATED to testing
FYI: The status of the ruby-specinfra source package in Debian's testing distribution has changed. Previous version: 1.25.4-1 Current version: 2.35.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] nanoc 3.8.0-1 MIGRATED to testing
FYI: The status of the nanoc source package in Debian's testing distribution has changed. Previous version: 3.7.3-1 Current version: 3.8.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-cssmin 1.0.3-4 MIGRATED to testing
FYI: The status of the ruby-cssmin source package in Debian's testing distribution has changed. Previous version: 1.0.3-3 Current version: 1.0.3-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] rubygems-integration 1.9 MIGRATED to testing
FYI: The status of the rubygems-integration source package in Debian's testing distribution has changed. Previous version: 1.8 Current version: 1.9 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Processing of ruby-omniauth-multipassword_0.4.2-1_amd64.changes
ruby-omniauth-multipassword_0.4.2-1_amd64.changes uploaded successfully to localhost along with the files: ruby-omniauth-multipassword_0.4.2-1.dsc ruby-omniauth-multipassword_0.4.2.orig.tar.gz ruby-omniauth-multipassword_0.4.2-1.debian.tar.xz ruby-omniauth-multipassword_0.4.2-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-omniauth-multipassword_0.4.2-1_amd64.changes is NEW
binary:ruby-omniauth-multipassword is NEW. source:ruby-omniauth-multipassword is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] nanoc is marked for autoremoval from testing
nanoc 3.8.0-1 is marked for autoremoval from testing on 2015-07-07 It (build-)depends on packages with these RC bugs: 784768: libhiredis-dev: Transition to cmake 3.2 786669: ruby-celluloid: tests sometimes fail, causing ftbfs sometimes 787910: ruby-fog-storm-on-demand: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/storm_on_demand/shared.rb ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-omniauth-bitbucket_0.0.2-1_amd64.changes is NEW
binary:ruby-omniauth-bitbucket is NEW. source:ruby-omniauth-bitbucket is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Processing of ruby-omniauth-bitbucket_0.0.2-1_amd64.changes
ruby-omniauth-bitbucket_0.0.2-1_amd64.changes uploaded successfully to localhost along with the files: ruby-omniauth-bitbucket_0.0.2-1.dsc ruby-omniauth-bitbucket_0.0.2.orig.tar.gz ruby-omniauth-bitbucket_0.0.2-1.debian.tar.xz ruby-omniauth-bitbucket_0.0.2-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] unicorn: native systemd service
On Thu, Jun 25, 2015 at 11:26:26PM +, Eric Wong wrote:
+Cc unicorn-public list
Christos Trochalakis chris...@skroutz.gr wrote:
Hello all,
I have recently migrated our main ruby application to systemd implementing zero
downtime upgrades.
systemd doesn't like replacing the binary on the fly. There is one exception to
this, services with PIDFile. When PIDFile is set, systemd reads it when the
main process exits and replaces the main process. nginx also had this issue a
few months ago [0].
So, in order to support zero-downtime upgrades we have to use a pid file.
I don't think so. You should be able to bind the listen socket in
systemd and rely on the socket activation features (setting the
UNICORN_FD environment variable to the created FD).
You still need to have the matching listen directive in the unicorn
config file so unicorn does not close it.
With socket activation, you should just be able to kill unicorn using
SIGQUIT (just master, or even all workers) and restart without ever
dropping a connection. I do NOT suggest using SIGTERM for unicorn,
since that'll cause the master to kill all workers ASAP.
Yes, you are right socket activation is also an option! I have made some
experiments with a simple rack app to test it.
systemd uses the LISTEN_FDS env variable that is an integer indicating the
number of inherited file descriptors. Those FDs have consecutive numbers
starting from `SD_LISTEN_FDS_START` which is `3` (man sd_listen_fds).
So for example if LISTEN_FDS=2, UNICORN_FD should be 3,4. I used a
simple wrapper script for that. Here is the full configuration:
$ tail -n+1 /srv/uni/* /etc/systemd/system/uni.*
== /srv/uni/config.ru ==
app = proc do |env|
sleep 5
[
200,
{ 'Content-Type' = 'text/plain' },
[Socket Activated!\n, pid:#{$$}\n, ppid:#{Process.ppid}\n]
]
end
run app
== /srv/uni/unicorn.conf.rb ==
worker_processes 2
working_directory /srv/uni
# Keep in sync with uni.socket
listen 9000, :tcp_nopush = true
listen 9001, :tcp_nopush = true
== /srv/uni/wrapper ==
#!/bin/bash
[ -z $LISTEN_FDS ] exec $@
UNICORN_FD=
for fd in `seq 3 $(($LISTEN_FDS+2))`; do
UNICORN_FD=${UNICORN_FD}${fd},
done
export UNICORN_FD
echo wrapped fds: ${UNICORN_FD}
exec $@
== /etc/systemd/system/uni.service ==
[Unit]
Description=Unicorn Server
[Service]
ExecStart=/srv/uni/wrapper /usr/bin/unicorn -c /srv/uni/unicorn.conf.rb -d
KillSignal=SIGQUIT
KillMode=mixed
== /etc/systemd/system/uni.socket ==
[Unit]
Description=Unicorn Socket
[Socket]
ListenStream=0.0.0.0:9000
ListenStream=0.0.0.0:9001
[Install]
WantedBy=sockets.target
Make sure to activate the systemd units:
chmod +x /srv/uni/wrapper
systemdctl daemon-reload
systemctl enable uni.socket
systemctl start uni.socket
The application sleeps for 5secs before replying.
I run the following commands from 3 different terminals:
$ curl localhost:9000 [blocked for 5sec]
# systemctl stop uni.service [issues sigquit on the running unicorn, killing
the 2nd worker and waiting the 1st to finish]
$ curl localhost:9000 [blocked since there are no more workers to accept right
now]
After the first request is served, unicorn dies and systemd respawns a new
master.
The second request is accepted by the new master (notice the different ppid).
Some notes:
TCP socket options are not applied by unicorn on inherited sockets (TCPSocket
=== sock is false). systemd socket files have support for most options now but
we might want unicorn to `setsockopt` them as well. For example,
'DeferAcceptSec', 'KeepAliveIntervalSec', 'NoDelay' are supported since v216, so
they are not available in jessie (v215).
socket activation is a really interesting setup, but personally I would not run
it with a large application. Clients would have to wait for the new master to
be up and running before a reply is returned, and that could take tenths of
seconds. The USR2 rexec solves that problem since both old and new workers are
accepting on the socket and we can kill the old ones when we are ready. In that
case the PIDFile trick is handy to support zero downtime restarts with no
latency.
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
