Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

executable file 382 lines (285 sloc) 12.119 kb
#!/usr/bin/env ruby
# Author: Greg Brockman <>
require 'rubygems'
require 'einhorn'
module Einhorn
module Executable
def self.einhorn_usage(long)
usage = <<EOF
## Usage
Einhorn is the language-independent shared socket manager. Run
`einhorn -h` to see detailed usage. At a high level, usage looks like
the following:
einhorn [options] program
Einhorn will open one or more shared sockets and run multiple copies
of your process. You can seamlessly reload your code, dynamically
reconfigure Einhorn, and more.
if long
usage << <<EOF
## Overview
To set Einhorn up as a master process running 3 copies of `sleep 5`:
$ einhorn -n 3 sleep 5
You can communicate your running Einhorn process via `einhornsh`:
$ einhornsh
Welcome gdb! You are speaking to Einhorn Master Process 11902
Enter 'help' if you're not sure what to do.
Type "quit" or "exit" to quit at any time
> help
You are speaking to the Einhorn command socket. You can run the following commands:
### Server sockets
If your process is a server and listens on one or more sockets,
Einhorn can open these sockets and pass them to the workers. You can
specify the addresses to bind by passing one or more `-b ADDR`
einhorn -b my-command
einhorn -b,r -b my-command
Each address is specified as an ip/port pair, possibly accompanied by options:
ADDR := (IP:PORT)[<,FLAG>...]
In the worker process, the opened file descriptors will be represented
as file descriptor numbers in a series of environment variables named
EINHORN_FD_0, EINHORN_FD_1, etc. (respecting the order that the `-b`
options were provided in), with the total number of file descriptors
in the EINHORN_FD_COUNT environment variable:
EINHORN_FD_0="6" #
EINHORN_FD_0="6" #,r
EINHORN_FD_1="7" #
Valid flags are:
r, so_reuseaddr: set SO_REUSEADDR on the server socket
n, o_nonblock: set O_NONBLOCK on the server socket
You can for example run:
$ einhorn -b,r -m manual -n 4 -- example/time_server
Which will run 4 copies of
EINHORN_FD_0=6 EINHORN_FD_COUNT=1 example/time_server
Where file descriptor 6 is a server socket bound to ``
and with `SO_REUSEADDR` set. It is then your application's job to
figure out how to `accept()` on this file descriptor.
### Command socket
Einhorn opens a UNIX socket to which you can send commands (run
`help` in `einhornsh` to see what admin commands you can
run). Einhorn relies on file permissions to ensure that no malicious
users can gain access. Run with a `-d DIRECTORY` to change the
directory where the socket will live.
Note that the command socket uses a line-oriented YAML protocol, and
you should ensure you trust clients to send arbitrary YAML messages
into your process.
### Seamless upgrades
You can cause your code to be seamlessly reloaded by upgrading the
worker code on disk and running
$ einhornsh
> upgrade
Once the new workers have been spawned, Einhorn will send each old
worker a SIGUSR2. SIGUSR2 should be interpreted as a request for a
graceful shutdown.
### ACKs
After Einhorn spawns a worker, it will only consider the worker up
once it has received an ACK. Currently two ACK mechanisms are
supported: manual and timer.
#### Manual ACK
A manual ACK (configured by providing a `-m manual`) requires your
application to send a command to the command socket once it's
ready. This is the safest ACK mechanism. If you're writing in Ruby,
just do
require 'einhorn/worker'
in your worker code. If you're writing in a different language, or
don't want to include Einhorn in your namespace, you can send the
{"command":"worker:ack", "pid":PID}
to the UNIX socket pointed to by the environment variable
`EINHORN_SOCK_PATH`. (Be sure to include a trailing newline.)
To make things even easier, you can pass a `-g` to Einhorn, in which
case you just need to `write()` the above message to the open file
descriptor pointed to by `EINHORN_SOCK_FD`.
(See `lib/einhorn/worker.rb` for details of these and other socket
discovery mechanisms.)
#### Timer ACK [default]
By default, Einhorn will use a timer ACK of 1 second. That means that
if your process hasn't exited after 1 second, it is considered ACK'd
and healthy. You can modify this timeout to be more appropriate for
your application (and even set to 0 if desired). Just pass a `-m
### Preloading
If you're running a Ruby process, Einhorn can optionally preload its
code, so it only has to load the code once per upgrade rather than
once per worker process. This also saves on memory overhead, since all
of the code in these processes will be stored only once using your
operating system's copy-on-write features.
To use preloading, just give Einhorn a `-p PATH_TO_CODE`, and make
sure you've defined an `einhorn_main` method.
In order to maximize compatibility, we've worked to minimize Einhorn's
dependencies. It has no dependencies outside of the Ruby standard
### Command name
You can set the name that Einhorn and your workers show in PS. Just
pass `-c <name>`.
### Config file
[new] Traditionally, Einhorn was configured entirely through
command-line options. However, this meant the only interface to modify
a running Einhorn's settings was via RPCs. Most relevantly, there was
no way to specify that you'd like to change the set of ports bound by
Einhorn now supports an optional YAML configuration file. Today, the
configuration file only supports the `bind` option:
- addr:
port: 3000
flags: [r, n] # optional, uses the same flags as the command-line
fd: 7 # optional, specifies which file descriptor Einhorn will bind
Upon upgrade, the configuration file gets reloaded. Einhorn figures
out what's changed, and will modify its file descriptor state to match
the configuration file. This includes potentially renumbering file
descriptors for a given addr/port.
For example, if you change the sample configuration file to:
- addr:
port: 3001
flags: [r, n]
fd: 7
- addr:
port: 3000
flags: [r]
fd: 8
Einhorn will perform the following operations:
- Renumber the existing (fd 7) to a temporary fd.
- Bind at descriptor 7.
- Renumber the existing (temporary fd) to 8.
usage << <<EOF
### Options
# Would be nice if this could be loadable rather than always
# executing, but when run under gem it's a bit hard to do so.
if true # $0 == __FILE__
Einhorn::TransientState.script_name = $0
Einhorn::TransientState.argv = ARGV.dup
Einhorn::TransientState.environ = ENV.to_hash
optparse = do |opts|
opts.on('-b ADDR', '--bind ADDR', 'Bind an address and add the corresponding FD via the environment') do |addr|
unless addr =~ /\A([^:]+):(\d+)((?:,\w+)*)\Z/
raise "Invalid value for #{addr.inspect}: bind address must be of the form address:port[,flags...]"
host = $1
port = Integer($2)
flags = Einhorn::FD.parse_flags($3)
Einhorn::State.bind << [host, port, flags]
opts.on('-C config', '--config config', 'The Einhorn config file to load') do |config_file|
Einhorn::State.config_file = config_file
opts.on('-c CMD_NAME', '--command-name CMD_NAME', 'Set the command name in ps to this value') do |cmd_name|
Einhorn::State.cmd_name = cmd_name
opts.on('-d PATH', '--socket-path PATH', 'Where to open the Einhorn command socket') do |path|
Einhorn::State.socket_path = path
opts.on('-e PIDFILE', '--pidfile PIDFILE', 'Where to write out the Einhorn pidfile') do |pidfile|
Einhorn::State.pidfile = pidfile
opts.on('-f LOCKFILE', '--lockfile LOCKFILE', 'Where to store the Einhorn lockfile') do |lockfile|
Einhorn::State.lockfile = lockfile
opts.on('-g', '--command-socket-as-fd', 'Leave the command socket open as a file descriptor, passed in the EINHORN_SOCK_FD environment variable. This allows your worker processes to ACK without needing to know where on the filesystem the command socket lives.') do
Einhorn::State.command_socket_as_fd = true
opts.on('-h', '--help', 'Display this message') do
opts.banner = Einhorn::Executable.einhorn_usage(true)
puts opts
opts.on('-k', '--kill-children-on-exit', 'If Einhorn exits unexpectedly, gracefully kill all its children') do
Einhorn::State.kill_children_on_exit = true
opts.on('-l', '--backlog N', 'Connection backlog (assuming this is a server)') do |b|
Einhorn::State.config[:backlog] = b.to_i
opts.on('-m MODE', '--ack-mode MODE', 'What kinds of ACK to expect from workers. Choices: FLOAT (number of seconds until assumed alive), manual (process will speak to command socket when ready). Default is MODE=1.') do |mode|
# Try manual
if mode == 'manual'
Einhorn::State.ack_mode = {:type => :manual}
# Try float
parsed = Float(mode)
rescue ArgumentError
Einhorn::State.ack_mode = {:type => :timer, :timeout => parsed}
# Give up
raise "Invalid ack-mode #{mode.inspect} (valid modes: FLOAT or manual)"
opts.on('-n', '--number N', 'Number of copies to spin up') do |n|
Einhorn::State.config[:number] = n.to_i
opts.on('-p PATH', '--preload PATH', 'Load this code into memory, and fork but do not exec upon spawn. Must define an "einhorn_main" method') do |path|
Einhorn::State.path = path
opts.on('-q', '--quiet', 'Make output quiet (can be reconfigured on the fly)') do
opts.on('-s', '--seconds N', 'Number of seconds to wait until respawning') do |b|
Einhorn::State.config[:seconds] = s.to_i
opts.on('-v', '--verbose', 'Make output verbose (can be reconfigured on the fly)') do
opts.on('--drop-env-var VAR_NAME', 'Delete VAR_NAME from the environment that is restored on upgrade') do |var|
Einhorn::State.drop_environment_variables << var
opts.on('--reexec-as=CMDLINE', 'Substitute CMDLINE for \"einhorn\" when upgrading') do |cmdline|
Einhorn::State.reexec_commandline = Shellwords.shellsplit(cmdline)
Einhorn.plugins_send(:optparse, opts)
opts.on('--nice MASTER[:WORKER=0][:RENICE_CMD=/usr/bin/renice]', 'Unix nice level at which to run the einhorn processes. If not running as root, make sure to ulimit -e as appopriate.') do |nice|
master, worker, renice_cmd = nice.split(':')
master = Integer(master) if master
worker = Integer(worker) if worker
Einhorn::State.nice[:master] = master if master
Einhorn::State.nice[:worker] = worker if worker
Einhorn::State.nice[:renice_cmd] = renice_cmd if renice_cmd
opts.on('--with-state-fd STATE', '[Internal option] With file descriptor containing state') do |fd|
Einhorn::TransientState.stateful = true
read = IO.for_fd(Integer(fd))
state =
opts.on('--upgrade-check', '[Internal option] Check if Einhorn can exec itself and exit with status 0 before loading code') do
exit 0
opts.on('--version', 'Show version') do
puts Einhorn::VERSION
if ARGV.length < 1
optparse.banner = Einhorn::Executable.einhorn_usage(false)
puts optparse
ret =
rescue TypeError
Jump to Line
Something went wrong with that request. Please try again.