-
Notifications
You must be signed in to change notification settings - Fork 3
/
service_control.rb
274 lines (246 loc) · 8.16 KB
/
service_control.rb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
require 'optparse'
module Picnic
# Provides functionality for controlling a Picnic-based server as
# an init.d service.
#
# Based on code from rubycas-server by jzylks and matt.zukowski.
#
# Usage Example:
#
# #!/usr/bin/env ruby
#
# require 'rubygems'
# require 'picnic/service_control'
#
# ctl = Picnic::ServiceControl.new('foo')
# ctl.handle_cli_input
#
# The file containing this code can now be used to control the Picnic
# app 'foo'.
#
# For, example, lets say you put this in a file called <tt>foo-ctl</tt>.
# You can now use <tt>foo-ctl</tt> on the command line as follows:
#
# chmod +x foo-ctl
# ./foo-ctl -h
# ./foo-ctl start --verbose --config /etc/foo/config.yml
# ./foo-ctl stop --config /etc/foo/config.yml
#
# Your <tt>foo-ctl</tt> script can also be used as part of Linux's init.d
# mechanism for launching system services. To do this, create the file
# <tt>/etc/init.d/foo</tt> and make sure that it is executable. It will
# look something like the following (this may vary depending on your Linux
# distribution; this example is for SuSE):
#
# #!/bin/sh
# CTL=foo-ctl
# . /etc/rc.status
#
# rc_reset
# case "$1" in
# start)
# $CTL start
# rc_status -v
# ;;
# stop)
# $CTL stop
# rc_status -v
# ;;
# restart)
# $0 stop
# $0 start
# rc_status
# ;;
# status)
# $CTL status
# rc_status -v
# ;;
# *)
# echo "Usage: $0 {start|stop|status|restart}
# exit 1
# ;;
# esac
# rc_exit
#
# You should now be able to launch your application like any other init.d script
# (just make sure that <tt>foo-ctl</tt> is installed in your executable <tt>PATH</tt>
# -- if your application is properly installed as a RubyGem, this will be done automatically).
#
# On most Linux systems, you can make your app start up automatically during boot by calling:
#
# chkconfig -a foo
#
# On Debian and Ubuntu, it's:
#
# update-rc.d foo defaults
#
class ServiceControl
attr_accessor :app, :options
# Creates a new service controller.
#
# +app+:: The name of the application. This should match the name of the
# binary, which by default is expected to be in the same directory
# as the service control script.
# +options+:: A hash overriding default options. The options are:
# +bin_file+:: The name of the binary file that this control
# script will use to start and stop your app.
# +pid_file+:: Where the app's PID file (containing the app's
# process ID) should be placed.
# +verbose+:: True if the service control script should report
# everything that it's doing to STDOUT.
def initialize(app, options = {})
@app = app
@options = options
@options[:bin_file] ||= "bin/#{app}"
@options[:pid_file] ||= "/etc/#{app}/#{app}.pid"
@options[:conf_file] ||= nil
@options[:verbose] ||= false
@options = options
end
# Parses command line options given to the service control script.
def handle_cli_input
OptionParser.new do |opts|
opts.banner = "Usage: #{$0} (start|stop|restart) [options]"
opts.banner += "\n#{app} is only usable when using webrick or mongrel"
opts.on("-c", "--config FILE", "Path to #{app} configuration file") { |value| @options[:conf_file] = value }
opts.on("-P", "--pid_file FILE", "Path to #{app} pid file") { |value| @options[:pid_file] = value }
opts.on('-v', '--verbose', "Print debugging information to the console") { |value| @options[:verbose] = value }
if ARGV.empty?
puts opts
exit
else
@cmd = opts.parse!(ARGV)
if @cmd.nil?
puts opts
exit
end
end
end
if !@options[:conf_file].nil? && !File.exists?(@options[:conf_file])
puts "Invalid path to #{app} configuration file: #{@options[:conf_file]}"
exit
end
case @cmd[0]
when "start":
puts "Starting #{app}..."
start
when "stop":
puts "Stopping #{app}..."
stop
when "restart":
puts "Restarting #{app}..."
stop
start
when "status":
puts "Checking status of #{app}..."
status
else
puts "Invalid command. Usage: #{app}-ctl [-cPv] start|stop|restart|status"
end
exit
end
def start
# use local app bin if it exists and is executable -- makes debugging easier
bin = options[:bin_file]
if File.exists?(bin)
exec = "ruby #{bin}"
else
exec = app
end
case get_state
when :ok
$stderr.puts "#{app} is already running"
exit 1
when :not_running, :empty_pid
$stderr.puts "The pid file '#{@options[:pid_file]}' exists but #{app} is not running." +
" The pid file will be automatically deleted for you, but this shouldn't have happened!"
File.delete(@options[:pid_file])
when :dead
$stderr.puts "The pid file '#{@options[:pid_file]}' exists but #{app} is not running." +
" Please delete the pid file first."
exit 1
when :missing_pid
# we should be good to go (unless the server is already running without a pid file)
else
$stderr.puts "#{app} could not be started. Try looking in the log file for more info."
exit 1
end
cmd = "#{exec} -d -P #{@options[:pid_file]}"
cmd += " -c #{@options[:conf_file]}" if !@options[:conf_file].nil?
puts "<<< #{cmd}" if @options[:verbose]
output = `#{cmd}`
puts ">>> #{output}" if @options[:verbose]
s = get_state
puts ">>> STATE: #{s.to_s}" if options[:verbose]
if s == :ok
exit 0
else
$stderr.puts "\n#{app} could not start properly!\nTry running with the --verbose option for details."
case s
when :missing_pid
exit 4
when :not_running
exit 3
when :dead
exit 1
else
exit 4
end
end
end
def stop
if File.exists? @options[:pid_file]
pid = open(@options[:pid_file]).read.to_i
begin
Process.kill("TERM", pid)
exit 0
rescue Errno::ESRCH
$stderr.puts "#{app} process '#{pid}' does not exist."
exit 1
end
else
$stderr.puts "#{@options[:pid_file]} not found. Is #{app} running?"
exit 4
end
end
def status
case get_state
when :ok
puts "#{app} appears to be up and running."
exit 0
when :missing_pid
$stderr.puts "#{app} does not appear to be running (pid file not found)."
exit 3
when :empty_pid
$stderr.puts "#{app} does not appear to be running (pid file exists but is empty)."
when :not_running
$stderr.puts "#{app} is not running."
exit 1
when :dead
$stderr.puts "#{app} is dead or unresponsive."
exit 102
end
end
def get_state
# FIXME: This is a poor attempt at trying to fix a problem where occassionally
# an empty pid_file is read, probably because it has not yet been
# fully written.
sleep 0.5
if File.exists? @options[:pid_file]
pid = File.read(@options[:pid_file]).strip
return :empty_pid unless pid and !pid.empty? # pid file exists but is empty
state = `ps -p #{pid} -o state=`.strip
if state == ''
return :not_running
elsif state == 'R' || state == 'S'
return :ok
else
return :dead
end
else
# TODO: scan through the process table to see if server is running without pid file
return :missing_pid
end
end
end
end