tornado + nginx + supervisord 环境部署

学习tornado有一周多了，自己按着demo中的例子手动搬代码，收获还是有的，加深了理解。demo: http://demo.pythoner.com/itt2zh/ch8.html

大概明白了它怎么工作后，开始部署一个线上环境跑跑。

nginx: 分配客户端请求给upstream组中列出的Tornado实例。其中静态目录的文件由nginx直接提供。

supervisord: tornado进程管理。

tornado: 功能实现。

关于nginx

在/etc/nginx/site-enable/default中 新增：

upstream frontends{
    server 127.0.0.1:;
}

server {
    listen ;

    location / {
        proxy_read_timeout ;
        proxy_pass_header Server;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_pass http://frontends;
    }
}

关于supervisord

确认是否已install supervisord，安装后可查看状态“sudo supervisorctl status”;

$ vi /etc/supervisor/supervisord.conf

; supervisor config file

[unix_http_server]
file=/var/run/supervisor.sock   ; (the path to the socket file)
chmod=                       ; sockef file mode (default )

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket

; The [include] section can just contain the "files" setting.  This
; setting can list multiple files (separated by whitespace or
; newlines).  It can also contain wildcards.  The filenames are
; interpreted as relative to this file.  Included files *cannot*
; include files themselves.

[include]
files = /etc/supervisor/conf.d/*.conf

"

[include]
files = /etc/supervisor/conf.d/*.conf

"

把supervisord 加入 /etc/init.d 中， 把保存为 supervisord , 内容如下：

    #! /bin/sh
    #
    # skeleton  example file to build /etc/init.d/ scripts.
    #       This file should be used to construct scripts for /etc/init.d.
    #
    #       Written by Miquel van Smoorenburg <miquels@cistron.nl>.
    #       Modified for Debian
    #       by Ian Murdock <imurdock@gnu.ai.mit.edu>.
    #               Further changes by Javier Fernandez-Sanguino <jfs@debian.org>
    #
    # Version:  @(#)skeleton  1.9  26-Feb-2001  miquels@cistron.nl
    #
    ### BEGIN INIT INFO
    # Provides:          supervisor
    # Required-Start:    $remote_fs $network $named
    # Required-Stop:     $remote_fs $network $named
    # Default-Start:     2 3 4 5
    # Default-Stop:      0 1 6
    # Short-Description: Start/stop supervisor
    # Description:       Start/stop supervisor daemon and its configured
    #                    subprocesses.
    ### END INIT INFO

    . /lib/lsb/init-functions

    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
    DAEMON=/usr/bin/supervisord
    NAME=supervisord
    DESC=supervisor

    test -x $DAEMON || exit 0

    LOGDIR=/var/log/supervisor
    PIDFILE=/var/run/$NAME.pid
    DODTIME=5                   # Time to wait for the server to die, in seconds
                                # If this value is set too low you might not
                                # let some servers to die gracefully and
                                # 'restart' will not work

    # Include supervisor defaults if available
    if [ -f /etc/default/supervisor ] ; then
        . /etc/default/supervisor
    fi
    DAEMON_OPTS="-c /etc/supervisor/supervisord.conf $DAEMON_OPTS"

    set -e

    running_pid()
    {
        # Check if a given process pid's cmdline matches a given name
        pid=$1
        name=$2
        [ -z "$pid" ] && return 1
        [ ! -d /proc/$pid ] &&  return 1
        (cat /proc/$pid/cmdline | tr "\000" "\n"|grep -q $name) || return 1
        return 0
    }

    running()
    {
    # Check if the process is running looking at /proc
    # (works for all users)

        # No pidfile, probably no daemon present
        [ ! -f "$PIDFILE" ] && return 1
        # Obtain the pid and check it against the binary name
        pid=`cat $PIDFILE`
        running_pid $pid $DAEMON || return 1
        return 0
    }

    force_stop() {
    # Forcefully kill the process
        [ ! -f "$PIDFILE" ] && return
        if running ; then
            kill -15 $pid
            # Is it really dead?
            [ -n "$DODTIME" ] && sleep "$DODTIME"s
            if running ; then
                kill -9 $pid
                [ -n "$DODTIME" ] && sleep "$DODTIME"s
                if running ; then
                    echo "Cannot kill $LABEL (pid=$pid)!"
                    exit 1
                fi
            fi
        fi
        rm -f $PIDFILE
        return 0
    }

    case "$1" in
      start)
        echo -n "Starting $DESC: "
        start-stop-daemon --start --quiet --pidfile $PIDFILE \
            --startas $DAEMON -- $DAEMON_OPTS
        test -f $PIDFILE || sleep 1
            if running ; then
                echo "$NAME."
            else
                echo " ERROR."
            fi
        ;;
      stop)
        echo -n "Stopping $DESC: "
        start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE
        echo "$NAME."
        ;;
      force-stop)
        echo -n "Forcefully stopping $DESC: "
            force_stop
            if ! running ; then
                echo "$NAME."
            else
                echo " ERROR."
            fi
        ;;
      #reload)
        #
        #   If the daemon can reload its config files on the fly
        #   for example by sending it SIGHUP, do it here.
        #
        #   If the daemon responds to changes in its config file
        #   directly anyway, make this a do-nothing entry.
        #
        # echo "Reloading $DESC configuration files."
        # start-stop-daemon --stop --signal 1 --quiet --pidfile \
        #   /var/run/$NAME.pid --exec $DAEMON
      #;;
      force-reload)
        #
        #   If the "reload" option is implemented, move the "force-reload"
        #   option to the "reload" entry above. If not, "force-reload" is
        #   just the same as "restart" except that it does nothing if the
        #   daemon isn't already running.
        # check wether $DAEMON is running. If so, restart
        start-stop-daemon --stop --test --quiet --pidfile $PIDFILE \
            --startas $DAEMON \
        && $0 restart \
        || exit 0
        ;;
      restart)
        echo -n "Restarting $DESC: "
        start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE
        [ -n "$DODTIME" ] && sleep $DODTIME
        start-stop-daemon --start --quiet --pidfile $PIDFILE \
            --startas $DAEMON -- $DAEMON_OPTS
        echo "$NAME."
        ;;
      status)
        echo -n "$LABEL is "
        if running ;  then
            echo "running"
        else
            echo " not running."
            exit 1
        fi
        ;;
      *)
        N=/etc/init.d/$NAME
        # echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
        echo "Usage: $N {start|stop|restart|force-reload|status|force-stop}" >&2
        exit 1
        ;;
    esac

    exit 0

同时 也参见 https://github.com/Supervisor/initscripts

完成后即可在/etc/supervisor/conf.d/ 目录下$vi tornado_demo.conf

[program:tornado_demo]
command=python /var/www/tornado_example/munger/main.py --port=
autostart=true
autorestart=true
redirect_stderr=true
stdout_logfile = /var/log/munger/munger.log
stderr_logfile = /var/log/munger/error.log

关于tornado

实例使用 http://demo.pythoner.com/itt2zh/ch2.html

2.3 复杂示例：The Alpha Munger 例子即可。

其中 重点需要关注的是supervisord的用法。

1. sudo supervisorctl stop tornado_demo

2. sudo supervisorctl start tornado_demo

3. sudo supervisorctl status

4. sudo /etc/init.d/supervisor start/stop/restart/reload

修改*.conf文件后，需要reload

参考链接：

1. http://gracece.com/2014/03/Tornado-supervisor+nginx/

2. http://blog.csdn.net/tengzhaorong/article/details/12833157

3. https://serholiu.com/tornado-nginx-supervisord

4. http://serverfault.com/questions/718689/how-to-configure-a-newer-version-of-supervisord-to-start-on-system-boot-in-ubunt