The purpose of this post is to document how to create init script in CentOS 6 to be used with the usual service management commands such as service and chkconfig.
Introduction
After being somewhat dissatisfied with the service script provided by GlassFish, I decided to learn how to create my own service script to start, stop, and view the status of non-packaged applications.
Learn Shell Scripting
I began by looking at other service scripts that has been already provided by CentOS such as /etc/init.d/httpd and /etc/init.d/iptables for ideas.
To help understand the scripts, I had to start learning shell scripting. A very good tutorial can be found here.
Writing the script
The skeleton script
There is a file inside CentOS that explains a bit about how to write init scripts. The path to the file is /usr/share/doc/initscripts-*/sysvinitfiles. You can open this file in a text editor, and have a read.
Included in this file is a base outline of an init script that we can base our script on. The following is the content of the outline:
#!/bin/bash
#
# /etc/rc.d/init.d/<servicename>
#
# <description of the *service*>
# <any general comments about this init script>
#
# <tags -- see below for tag definitions. *Every line* from the top
# of the file to the end of the tags section must begin with a #
# character. After the tags section, there should be a blank line.
# This keeps normal comments in the rest of the file from being
# mistaken for tags, should they happen to fit the pattern.>
# Source function library.
. /etc/init.d/functions
<define any local shell functions used by the code that follows>
start() {
echo -n "Starting <servicename>: "
<start daemons, perhaps with the daemon function>
touch /var/lock/subsys/<servicename>
return <return code of starting daemon>
}
stop() {
echo -n "Shutting down <servicename>: "
<stop daemons, perhaps with the killproc function>
rm -f /var/lock/subsys/<servicename>
return <return code of stopping daemon>
}
case "$1" in
start)
start
;;
stop)
stop
;;
status)
<report the status of the daemons in free-form format,
perhaps with the status function>
;;
restart)
stop
start
;;
reload)
<cause the service configuration to be reread, either with
kill -HUP or by restarting the daemons, in a manner similar
to restart above>
;;
condrestart)
<Restarts the servce if it is already running. For example:>
[ -f /var/lock/subsys/<service> ] && restart || :
probe)
<optional. If it exists, then it should determine whether
or not the service needs to be restarted or reloaded (or
whatever) in order to activate any changes in the configuration
scripts. It should print out a list of commands to give to
$0; see the description under the probe tag below.>
;;
*)
echo "Usage: <servicename> {start|stop|status|reload|restart[|probe]"
exit 1
;;
esac
exit $?
Create init script by modifying the skeleton script
Using the skeleton script as a base, and comparing it with other established init scripts, I have come up with the following for GlassFish 4:
#!/bin/bash
#
# glassfish4 GlassFish Server Open Source Edition 4.0
#
# chkconfig: 345 70 30
# description: GlassFish Server is a Java EE Application Server Platform
# processname: glassfish4
# Source function library.
. /etc/init.d/functions
RETVAL=0
prog="glassfish4"
LOCKFILE=/var/lock/subsys/$prog
# Declare variables for GlassFish Server
GLASSFISH_DIR=/home/gfish/glassfish4
GLASSFISH_USER=gfish
ASADMIN=$GLASSFISH_DIR/bin/asadmin
DOMAIN=domain1
start() {
echo -n "Starting $prog: "
daemon --user $GLASSFISH_USER $ASADMIN start-domain $DOMAIN
RETVAL=$?
[ $RETVAL -eq 0 ] && touch $LOCKFILE
echo
return $RETVAL
}
stop() {
echo -n "Shutting down $prog: "
$ASADMIN stop-domain domain1 && success || failure
RETVAL=$?
[ $RETVAL -eq 0 ] && rm -f $LOCKFILE
echo
return $RETVAL
}
status() {
echo -n "Checking $prog status: "
$ASADMIN list-domains | grep $DOMAIN
RETVAL=$?
return $RETVAL
}
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status
;;
restart)
stop
start
;;
*)
echo "Usage: $prog {start|stop|status|restart}"
exit 1
;;
esac
exit $RETVAL
Using the script
Add the script to chkconfig
The script is placed inside the /etc/init.d/ directory, and given the name glassfish4.
Then, the script is added to the list using the chkconfig command.
[root@server ~]# chkconfig --add glassfish4
[root@server ~]# chkconfig --list glassfish4
glassfish4 0:off 1:off 2:off 3:on 4:on 5:on 6:off
Use the start operand
[root@server ~]# service glassfish4 start Starting glassfish4: Waiting for domain1 to start ......................... Successfully started the domain : domain1 domain Location: /home/gfish/glassfish4/glassfish/domains/domain1 Log File: /home/gfish/glassfish4/glassfish/domains/domain1/logs/server.log Admin Port: 4848 Command start-domain executed successfully. [ OK ]
Use the stop operand
[root@server ~]# service glassfish4 stop Shutting down glassfish4: Waiting for the domain to stop ...... Command stop-domain executed successfully. [ OK ]
Use the restart operand
[root@server ~]# service glassfish4 restart Shutting down glassfish4: Waiting for the domain to stop .. Command stop-domain executed successfully. [ OK ] Starting glassfish4: Waiting for domain1 to start ...................... Successfully started the domain : domain1 domain Location: /home/gfish/glassfish4/glassfish/domains/domain1 Log File: /home/gfish/glassfish4/glassfish/domains/domain1/logs/server.log Admin Port: 4848 Command start-domain executed successfully. [ OK ]
Use the status operand
[root@server ~]# service glassfish4 status
Checking glassfish4 status: domain1 running
Use any other operands
[root@server ~]# service glassfish4 lalala
Usage: glassfish4 {start|stop|status|restart}