Browse Source

Add init scripts and docs for Upstart and OpenRC

Adam Weiss 7 years ago

+ 10
- 0
contrib/init/ View File

@@ -0,0 +1,10 @@
Sample configuration files for:

SystemD: bitcoind.service
Upstart: bitcoind.conf
OpenRC: bitcoind.openrc

have been made available to assist packagers in creating node packages here.

See doc/ for more information.

+ 65
- 0
contrib/init/bitcoind.conf View File

@@ -0,0 +1,65 @@
description "Bitcoin Core Daemon"

start on runlevel [2345]
stop on starting rc RUNLEVEL=[016]

env BITCOIND_BIN="/usr/bin/bitcoind"
env BITCOIND_USER="bitcoin"
env BITCOIND_GROUP="bitcoin"
env BITCOIND_PIDDIR="/var/run/bitcoind"
# upstart can't handle variables constructed with other variables
env BITCOIND_PIDFILE="/var/run/bitcoind/"
env BITCOIND_CONFIGFILE="/etc/bitcoin/bitcoin.conf"
env BITCOIND_DATADIR="/var/lib/bitcoind"

expect fork

respawn limit 5 120
kill timeout 60

pre-start script
# this will catch non-existent config files
# bitcoind will check and exit with this very warning, but it can do so
# long after forking, leaving upstart to think everything started fine.
# since this is a commonly encountered case on install, just check and
# warn here.
if ! grep -qs '^rpcpassword=' "$BITCOIND_CONFIGFILE" ; then
echo "ERROR: You must set a secure rpcpassword to run bitcoind."
echo "The setting must appear in $BITCOIND_CONFIGFILE"
echo "This password is security critical to securing wallets "
echo "and must not be the same as the rpcuser setting."
echo "You can generate a suitable random password using the following"
echo "command from the shell:"
echo "bash -c 'tr -dc a-zA-Z0-9 < /dev/urandom | head -c32 && echo'"
echo "It is also recommended that you also set alertnotify so you are "
echo "notified of problems:"
echo "ie: alertnotify=echo %%s | mail -s \"Bitcoin Alert\"" \
exit 1

chmod 0755 "$BITCOIND_PIDDIR"
end script

exec start-stop-daemon \
--start \
--pidfile "$BITCOIND_PIDFILE" \
--exec "$BITCOIND_BIN" \
-- \
-datadir="$BITCOIND_DATADIR" \
-disablewallet \

+ 86
- 0
contrib/init/bitcoind.openrc View File

@@ -0,0 +1,86 @@

# backward compatibility for existing gentoo layout
if [ -d "/var/lib/bitcoin/.bitcoin" ]; then


name="Bitcoin Core Daemon"
description="Bitcoin crypto-currency p2p network daemon"

command_args="-pid=\"${BITCOIND_PIDFILE}\" \
-datadir=\"${BITCOIND_DATADIR}\" \
-daemon \

start_stop_daemon_args="-u ${BITCOIND_USER} \
-N ${BITCOIND_NICE:-0} -w 2000"

depend() {
need localmount net

# verify
# 1) that the datadir exists and is writable (or create it)
# 2) that a directory for the pid exists and is writable
# 3) ownership and permissions on the config file
start_pre() {
checkpath \
-d \
--mode 0750 \

checkpath \
-d \
--mode 0755 \

checkpath -f \
-m 0660 \

checkconfig || return 1

if ! grep -qs '^rpcpassword=' "${BITCOIND_CONFIGFILE}" ; then
eerror ""
eerror "ERROR: You must set a secure rpcpassword to run bitcoind."
eerror "The setting must appear in ${BITCOIND_CONFIGFILE}"
eerror ""
eerror "This password is security critical to securing wallets "
eerror "and must not be the same as the rpcuser setting."
eerror "You can generate a suitable random password using the following"
eerror "command from the shell:"
eerror ""
eerror "bash -c 'tr -dc a-zA-Z0-9 < /dev/urandom | head -c32 && echo'"
eerror ""
eerror "It is also recommended that you also set alertnotify so you are "
eerror "notified of problems:"
eerror ""
eerror "ie: alertnotify=echo %%s | mail -s \"Bitcoin Alert\"" \
eerror ""
return 1

+ 27
- 0
contrib/init/bitcoind.openrcconf View File

@@ -0,0 +1,27 @@
# /etc/conf.d/bitcoind: config file for /etc/init.d/bitcoind

# Config file location

# What directory to write pidfile to? (created and owned by $BITCOIND_USER)

# What filename to give the pidfile

# Where to write bitcoind data (be mindful that the blockchain is large)

# User and group to own bitcoind process

# Path to bitcoind executable

# Nice value to run bitcoind under

# Additional options (avoid -conf and -datadir, use flags above)

contrib/systemd/bitcoind.service → contrib/init/bitcoind.service View File

@@ -3,15 +3,20 @@ Description=Bitcoin's distributed currency daemon


ExecStart=/usr/bin/bitcoind -daemon -pid=/var/lib/bitcoind/ -conf=/etc/bitcoind.conf -datadir=/var/lib/bitcoind
ExecStart=/usr/bin/bitcoind -daemon -pid=/var/lib/bitcoind/ \
-conf=/etc/bitcoin/bitcoin.conf -datadir=/var/lib/bitcoind -disablewallet



+ 1
- 1
doc/ View File

@@ -68,7 +68,7 @@ The Bitcoin repo's [root README](
- [Assets Attribution](
- [Files](
- [Tor Support](
- [Systemd](
- [Init Scripts (systemd/upstart/openrc)](


+ 92
- 0
doc/ View File

@@ -0,0 +1,92 @@
Sample init scripts and service configuration for bitcoind

Sample scripts and configuration files for systemd, Upstart and OpenRC
can be found in the contrib/init folder.

contrib/init/bitcoind.service: systemd service unit configuration
contrib/init/bitcoind.openrc: OpenRC compatible SysV style init script
contrib/init/bitcoind.openrcconf: OpenRC conf.d file
contrib/init/bitcoind.conf: Upstart service configuration file

1. Service User

All three startup configurations assume the existence of a "bitcoin" user
and group. They must be created before attempting to use these scripts.

2. Configuration

At a bare minimum, bitcoind requires that the rpcpassword setting be set
when running as a daemon. If the configuration file does not exist or this
setting is not set, bitcoind will shutdown promptly after startup.

This password does not have to be remembered or typed as it is mostly used
as a fixed token that bitcoind and client programs read from the configuration
file, however it is recommended that a strong and secure password be used
as this password is security critical to securing the wallet should the
wallet be enabled.

If bitcoind is run with "-daemon" flag, and no rpcpassword is set, it will
print a randomly generated suitable password to stderr. You can also
generate one from the shell yourself like this:

bash -c 'tr -dc a-zA-Z0-9 < /dev/urandom | head -c32 && echo'

Once you have a password in hand, set rpcpassword= in /etc/bitcoin/bitcoin.conf

For an example configuration file that describes the configuration settings,
see contrib/debian/examples/bitcoin.conf.

3. Paths

All three configurations assume several paths that might need to be adjusted.

Binary: /usr/bin/bitcoind
Configuration file: /etc/bitcoin/bitcoin.conf
Data directory: /var/lib/bitcoind
PID file: /var/run/bitcoind/ (OpenRC and Upstart)
/var/lib/bitcoind/ (systemd)

The configuration file, PID directory (if applicable) and data directory
should all be owned by the bitcoin user and group. It is advised for security
reasons to make the configuration file and data directory only readable by the
bitcoin user and group. Access to bitcoin-cli and other bitcoind rpc clients
can then be controlled by group membership.

4. Installing Service Configuration

4a) systemd

Installing this .service file consists on just copying it to
/usr/lib/systemd/system directory, followed by the command
"systemctl daemon-reload" in order to update running systemd configuration.

To test, run "systemctl start bitcoind" and to enable for system startup run
"systemctl enable bitcoind"

4b) OpenRC

Rename bitcoind.openrc to bitcoind and drop it in /etc/init.d. Double
check ownership and permissions and make it executable. Test it with
"/etc/init.d/bitcoind start" and configure it to run on startup with
"rc-update add bitcoind"

4c) Upstart (for Debian/Ubuntu based distributions)

Drop bitcoind.conf in /etc/init. Test by running "service bitcoind start"
it will automatically start on reboot.

NOTE: This script is incompatible with CentOS 5 and Amazon Linux 2014 as they
use old versions of Upstart and do not supply the start-stop-daemon uitility.

5. Auto-respawn

Auto respawning is currently only configured for Upstart and systemd.
Reasonable defaults have been chosen but YMMV.

+ 0
- 47
doc/ View File

@@ -1,47 +0,0 @@

Packagers can find a .service file in this repo in order to integrate bitcoin's
daemon into systemd based distributions.

bitcoind.service file is located in contrib/systemd/ folder.

1. Users

This .service file assumes bitcoind user and group exist in the system, so packager
should make sure they are created on installation.

2. Files

The .service file assumes several paths that might need to be adjusted according
to packager's needs.

Daemon's config file is assumed to be located at /etc/bitcoind.conf (you can
use contrib/debian/examples/bitcoin.conf as an example). Once installed, users
must edit the file in order to update at least these two
values: rpcuser and rpcpassword . Failing to do so will make the daemon fail
to boot. However, the message written to /var/lib/bitcoind/debug.log file is
very helpful and no default values should be set:

YYYY-MM-DD HH:MM:DD Error: To use the "-server" option, you must set a rpcpassword in the configuration file:
It is recommended you use the following random password:
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "Bitcoin Alert"

Daemon's data and pid files will be stored in /var/lib/bitcoind directory, so it
should be created on installation and make bitcoind user/group it's owner.

3. Installing .service file

Installing this .service file consists on just copying it to /usr/lib/systemd/system
directory, followed by the command "systemctl daemon-reload" in order to update
running systemd configuration.