celery守护进程(生产服务器进行部署)

本文主要是介绍celery守护进程(生产服务器进行部署)，对大家解决编程问题具有一定的参考价值，需要的程序猿们随着小编来一起学习吧！

celery守护进程(Shell 脚本方式)

django + redis + celery
redis同时作为broker和backend

脚本名字 : celeryd
在 /etc/init.d/新建celeryd

命令使用方法 :
    /etc/init.d/celeryd {start|stop|restart|status}

配置文件 :
    /etc/default/celeryd

编写worker启动脚本
此文件直接粘贴到/etc/init.d/celeryd, 通用, 文件来自celery官网

#!/bin/sh -e
# ============================================
#  celeryd - Starts the Celery worker daemon.
# ============================================
#
# :Usage: /etc/init.d/celeryd {start|stop|force-reload|restart|try-restart|status}
# :Configuration file: /etc/default/celeryd (or /usr/local/etc/celeryd on BSD)
#
# See http://docs.celeryproject.org/en/latest/userguide/daemonizing.html#generic-init-scripts


### BEGIN INIT INFO
# Provides:          celeryd
# Required-Start:    $network $local_fs $remote_fs
# Required-Stop:     $network $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: celery task worker daemon
### END INIT INFO
#
#
# To implement separate init-scripts, copy this script and give it a different
# name.  That is, if your new application named "little-worker" needs an init,
# you should use:
#
#   cp /etc/init.d/celeryd /etc/init.d/little-worker
#
# You can then configure this by manipulating /etc/default/little-worker.
#
VERSION=10.1
echo "celery init v${VERSION}."
if [ $(id -u) -ne 0 ]; then
    echo "Error: This program can only be used by the root user."
    echo "       Unprivileged users must use the 'celery multi' utility, "
    echo "       or 'celery worker --detach'."
    exit 1
fi

origin_is_runlevel_dir () {
    set +e
    dirname $0 | grep -q "/etc/rc.\.d"
    echo $?
}

# Can be a runlevel symlink (e.g., S02celeryd)
if [ $(origin_is_runlevel_dir) -eq 0 ]; then
    SCRIPT_FILE=$(readlink "$0")
else
    SCRIPT_FILE="$0"
fi
SCRIPT_NAME="$(basename "$SCRIPT_FILE")"

DEFAULT_USER="celery"
DEFAULT_PID_FILE="/var/run/celery/%n.pid"
DEFAULT_LOG_FILE="/var/log/celery/%n%I.log"
DEFAULT_LOG_LEVEL="INFO"
DEFAULT_NODES="celery"
DEFAULT_CELERYD="-m celery worker --detach"

if [ -d "/etc/default" ]; then
    CELERY_CONFIG_DIR="/etc/default"
else
    CELERY_CONFIG_DIR="/usr/local/etc"
fi

# 配置文件的位置
CELERY_DEFAULTS=${CELERY_DEFAULTS:-"$CELERY_CONFIG_DIR/${SCRIPT_NAME}"}

# Make sure executable configuration script is owned by root
_config_sanity() {
    local path="$1"
    local owner=$(ls -ld "$path" | awk '{print $3}')
    local iwgrp=$(ls -ld "$path" | cut -b 6)
    local iwoth=$(ls -ld "$path" | cut -b 9)

    if [ "$(id -u $owner)" != "0" ]; then
        echo "Error: Config script '$path' must be owned by root!"
        echo
        echo "Resolution:"
        echo "Review the file carefully, and make sure it hasn't been "
        echo "modified with mailicious intent.  When sure the "
        echo "script is safe to execute with superuser privileges "
        echo "you can change ownership of the script:"
        echo "    $ sudo chown root '$path'"
        exit 1
    fi

    if [ "$iwoth" != "-" ]; then  # S_IWOTH
        echo "Error: Config script '$path' cannot be writable by others!"
        echo
        echo "Resolution:"
        echo "Review the file carefully, and make sure it hasn't been "
        echo "modified with malicious intent.  When sure the "
        echo "script is safe to execute with superuser privileges "
        echo "you can change the scripts permissions:"
        echo "    $ sudo chmod 640 '$path'"
        exit 1
    fi
    if [ "$iwgrp" != "-" ]; then  # S_IWGRP
        echo "Error: Config script '$path' cannot be writable by group!"
        echo
        echo "Resolution:"
        echo "Review the file carefully, and make sure it hasn't been "
        echo "modified with malicious intent.  When sure the "
        echo "script is safe to execute with superuser privileges "
        echo "you can change the scripts permissions:"
        echo "    $ sudo chmod 640 '$path'"
        exit 1
    fi
}

if [ -f "$CELERY_DEFAULTS" ]; then
    _config_sanity "$CELERY_DEFAULTS"
    echo "Using config script: $CELERY_DEFAULTS"
    # 加载配置文件的信息到该脚本程序中
    . "$CELERY_DEFAULTS"
fi

# Sets --app argument for CELERY_BIN
CELERY_APP_ARG=""
if [ ! -z "$CELERY_APP" ]; then
    CELERY_APP_ARG="--app=$CELERY_APP"
fi

# Options to su
# can be used to enable login shell (CELERYD_SU_ARGS="-l"),
# or even to use start-stop-daemon instead of su.
CELERYD_SU=${CELERY_SU:-"su"}
CELERYD_SU_ARGS=${CELERYD_SU_ARGS:-""}

CELERYD_USER=${CELERYD_USER:-$DEFAULT_USER}

# Set CELERY_CREATE_DIRS to always create log/pid dirs.
CELERY_CREATE_DIRS=${CELERY_CREATE_DIRS:-0}
CELERY_CREATE_RUNDIR=$CELERY_CREATE_DIRS
CELERY_CREATE_LOGDIR=$CELERY_CREATE_DIRS
if [ -z "$CELERYD_PID_FILE" ]; then
    CELERYD_PID_FILE="$DEFAULT_PID_FILE"
    CELERY_CREATE_RUNDIR=1
fi
if [ -z "$CELERYD_LOG_FILE" ]; then
    CELERYD_LOG_FILE="$DEFAULT_LOG_FILE"
    CELERY_CREATE_LOGDIR=1
fi

CELERYD_LOG_LEVEL=${CELERYD_LOG_LEVEL:-${CELERYD_LOGLEVEL:-$DEFAULT_LOG_LEVEL}}
CELERY_BIN=${CELERY_BIN:-"celery"}
CELERYD_MULTI=${CELERYD_MULTI:-"$CELERY_BIN multi"}
CELERYD_NODES=${CELERYD_NODES:-$DEFAULT_NODES}

export CELERY_LOADER

if [ -n "$2" ]; then
    CELERYD_OPTS="$CELERYD_OPTS $2"
fi

CELERYD_LOG_DIR=`dirname $CELERYD_LOG_FILE`
CELERYD_PID_DIR=`dirname $CELERYD_PID_FILE`

# Extra start-stop-daemon options, like user/group.
if [ -n "$CELERYD_CHDIR" ]; then
    DAEMON_OPTS="$DAEMON_OPTS --workdir=$CELERYD_CHDIR"
fi


check_dev_null() {
    if [ ! -c /dev/null ]; then
        echo "/dev/null is not a character device!"
        exit 75  # EX_TEMPFAIL
    fi
}


maybe_die() {
    if [ $? -ne 0 ]; then
        echo "Exiting: $* (errno $?)"
        exit 77  # EX_NOPERM
    fi
}

create_default_dir() {
    if [ ! -d "$1" ]; then
        echo "- Creating default directory: '$1'"
        mkdir -p "$1"
        maybe_die "Couldn't create directory $1"
        echo "- Changing permissions of '$1' to 02755"
        chmod 02755 "$1"
        maybe_die "Couldn't change permissions for $1"
        if [ -n "$CELERYD_USER" ]; then
            echo "- Changing owner of '$1' to '$CELERYD_USER'"
            chown "$CELERYD_USER" "$1"
            maybe_die "Couldn't change owner of $1"
        fi
        if [ -n "$CELERYD_GROUP" ]; then
            echo "- Changing group of '$1' to '$CELERYD_GROUP'"
            chgrp "$CELERYD_GROUP" "$1"
            maybe_die "Couldn't change group of $1"
        fi
    fi
}


check_paths() {
    if [ $CELERY_CREATE_LOGDIR -eq 1 ]; then
        create_default_dir "$CELERYD_LOG_DIR"
    fi
    if [ $CELERY_CREATE_RUNDIR -eq 1 ]; then
        create_default_dir "$CELERYD_PID_DIR"
    fi
}

create_paths() {
    create_default_dir "$CELERYD_LOG_DIR"
    create_default_dir "$CELERYD_PID_DIR"
}

export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"


_get_pidfiles () {
    # note: multi < 3.1.14 output to stderr, not stdout, hence the redirect.
    ${CELERYD_MULTI} expand "${CELERYD_PID_FILE}" ${CELERYD_NODES} 2>&1
}


_get_pids() {
    found_pids=0
    my_exitcode=0

    for pidfile in $(_get_pidfiles); do
        local pid=`cat "$pidfile"`
        local cleaned_pid=`echo "$pid" | sed -e 's/[^0-9]//g'`
        if [ -z "$pid" ] || [ "$cleaned_pid" != "$pid" ]; then
            echo "bad pid file ($pidfile)"
            one_failed=true
            my_exitcode=1
        else
            found_pids=1
            echo "$pid"
        fi

    if [ $found_pids -eq 0 ]; then
        echo "${SCRIPT_NAME}: All nodes down"
        exit $my_exitcode
    fi
    done
}


_chuid () {
    ${CELERYD_SU} ${CELERYD_SU_ARGS} "$CELERYD_USER" -c "$CELERYD_MULTI $*"
}


start_workers () {
    if [ ! -z "$CELERYD_ULIMIT" ]; then
        # 设置该程序打开文件数
        ulimit -n $CELERYD_ULIMIT
    fi
    _chuid $* start $CELERYD_NODES $DAEMON_OPTS     \
                 --pidfile="$CELERYD_PID_FILE"      \
                 --logfile="$CELERYD_LOG_FILE"      \
                 --loglevel="$CELERYD_LOG_LEVEL"    \
                 $CELERY_APP_ARG                    \
                 $CELERYD_OPTS
}


dryrun () {
    (C_FAKEFORK=1 start_workers --verbose)
}


stop_workers () {
    _chuid stopwait $CELERYD_NODES --pidfile="$CELERYD_PID_FILE"
}


restart_workers () {
    _chuid restart $CELERYD_NODES $DAEMON_OPTS      \
                   --pidfile="$CELERYD_PID_FILE"    \
                   --logfile="$CELERYD_LOG_FILE"    \
                   --loglevel="$CELERYD_LOG_LEVEL"  \
                   $CELERY_APP_ARG                  \
                   $CELERYD_OPTS
}


kill_workers() {
    _chuid kill $CELERYD_NODES $DAEMON_OPTS --pidfile="$CELERYD_PID_FILE"
}


restart_workers_graceful () {
    echo "WARNING: Use with caution in production"
    echo "The workers will attempt to restart, but they may not be able to."
    local worker_pids=
    worker_pids=`_get_pids`
    [ "$one_failed" ] && exit 1

    for worker_pid in $worker_pids; do
        local failed=
        kill -HUP $worker_pid 2> /dev/null || failed=true
        if [ "$failed" ]; then
            echo "${SCRIPT_NAME} worker (pid $worker_pid) could not be restarted"
            one_failed=true
        else
            echo "${SCRIPT_NAME} worker (pid $worker_pid) received SIGHUP"
        fi
    done

    [ "$one_failed" ] && exit 1 || exit 0
}


check_status () {
    my_exitcode=0
    found_pids=0

    local one_failed=
    for pidfile in $(_get_pidfiles); do
        if [ ! -r $pidfile ]; then
            echo "${SCRIPT_NAME} down: no pidfiles found"
            one_failed=true
            break
        fi

        local node=`basename "$pidfile" .pid`
        local pid=`cat "$pidfile"`
        local cleaned_pid=`echo "$pid" | sed -e 's/[^0-9]//g'`
        if [ -z "$pid" ] || [ "$cleaned_pid" != "$pid" ]; then
            echo "bad pid file ($pidfile)"
            one_failed=true
        else
            local failed=
            kill -0 $pid 2> /dev/null || failed=true
            if [ "$failed" ]; then
                echo "${SCRIPT_NAME} (node $node) (pid $pid) is down, but pidfile exists!"
                one_failed=true
            else
                echo "${SCRIPT_NAME} (node $node) (pid $pid) is up..."
            fi
        fi
    done

    [ "$one_failed" ] && exit 1 || exit 0
}


case "$1" in
    start)
        check_dev_null
        check_paths
        start_workers
    ;;

    stop)
        check_dev_null
        check_paths
        stop_workers
    ;;

    reload|force-reload)
        echo "Use restart"
    ;;

    status)
        check_status
    ;;

    restart)
        check_dev_null
        check_paths
        restart_workers
    ;;

    graceful)
        check_dev_null
        restart_workers_graceful
    ;;

    kill)
        check_dev_null
        kill_workers
    ;;

    dryrun)
        check_dev_null
        dryrun
    ;;

    try-restart)
        check_dev_null
        check_paths
        restart_workers
    ;;

    create-paths)
        check_dev_null
        create_paths
    ;;

    check-paths)
        check_dev_null
        check_paths
    ;;

    *)
        echo "Usage: /etc/init.d/${SCRIPT_NAME} {start|stop|restart|graceful|kill|dryrun|create-paths}"
        exit 64  # EX_USAGE
    ;;
esac

exit 0

celeryd

改变权限:

chmod +x /etc/init.d/celeryd

编写worker的配置文件，位置：/etc/default/celeryd

# 节点名字【标识作用】，日志也会以这个名字开头，自定义即可，启动多个的写法：CELERYD_NODES="worker1 worker2 worker3" 或 CELERYD_NODES=10
CELERYD_NODES="worker1"

# 配置celery的位置，查看位置：which celery
CELERY_BIN="/usr/local/bin/celery"

# 配置实例化app，一般指的创建app实例的文件，django项目则配置项目名，完整的配置方法：CELERY_APP="proj.tasks:app"
# 这里写自己django的项目名字即可
CELERY_APP="proj"

# 进入哪个workerr的目录   绝对路径: django项目比如结构是: /home/mypro/mypro/celery.py    那这里填的就是如下所示
CELERYD_CHDIR="/home/mypro/mypro/"

# --time-limit ： 限制处理任务的时长
# --concurrency ： 设置最高的并发数
# 多个启动worker,对每个woker进行单独的配置方法：CELERYD_OPTS="--time-limit=300 -c 8 -c:worker2 4 -c:worker3 2 -Ofair:worker1"
CELERYD_OPTS=" --time-limit=300 --concurrency=8"

# 设置日志的级别：开发环境：DEBUG，生产环境：INFO
CELERYD_LOG_LEVEL="DEBUG"

# 设置存放目志位置
CELERYD_LOG_FILE="/var/log/celery/%n%I.log"

# 设置启动程序存放pid文件
CELERYD_PID_FILE="/var/run/celery/%n.pid"

# 设置启动程序的用户，需要手动创建用户和组
CELERYD_USER="runyi"
CELERYD_GROUP="runyi"

# 1：自动创建需要的目录文件并且设置运行程序所需的用户和组，0：需要手动处理
CELERY_CREATE_DIRS=1

# 设置celery最大的文件打开数
CELERYD_ULIMIT=65535

# 指明django的配置文件
export DJANGO_SETTINGS_MODULE="settings"
# 导出路径
export PYTHONPATH="$PYTHONPATH:/home/mypro"

创建celery用户和组

useradd celery

启动

root@hecs01:/var/log# /etc/init.d/celeryd start
celery init v10.1.
Using config script: /etc/default/celeryd
- Creating default directory: '/var/log/celery'
- Changing permissions of '/var/log/celery' to 02755
- Changing owner of '/var/log/celery' to 'celery'
- Changing group of '/var/log/celery' to 'celery'
- Creating default directory: '/var/run/celery'
- Changing permissions of '/var/run/celery' to 02755
- Changing owner of '/var/run/celery' to 'celery'
- Changing group of '/var/run/celery' to 'celery'
celery multi v5.0.5 (singularity)
> Starting nodes...
	> worker1@hecs01: OK

检查启动的进程

root@hecs01:/var/log# ps -ef | grep python
root         590       1  0 18:06 ?        00:00:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
root         788       1  0 18:06 ?        00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
celery     2389       1  0 18:17 ?        00:00:03 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2392    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2393    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2394    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2395    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2396    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2397    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2398    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
celery     2399    2389  0 18:17 ?        00:00:00 /usr/bin/python3 -m celery --app=runyi --workdir=/home/runyi/runyi/runyi/ worker --pidfile=/var/run/celery/worker1.pid --logfile=/var/log/celery/worker1%I.log --loglevel=DEBUG --time-limit=300 --concurrency=8 -n worker1@hecs01 --executable=/usr/bin/python3
root        3215    2048  0 18:37 pts/2    00:00:00 grep --color=auto python

在配置的过程中遇到了许多问题,都一一记录在我的其他celery文章中,有问题可以去找找, 懒得贴了

抱拳

这篇关于celery守护进程(生产服务器进行部署)的文章就介绍到这儿，希望我们推荐的文章对大家有所帮助，也希望大家多多支持为之网！

C/C++教程

celery守护进程(生产服务器进行部署)

celery守护进程(Shell 脚本方式)

前端开发

后端开发

移动端开发

数据库

服务器运维

人工智能

区块链

游戏开发

网站运营

大数据/云计算

软件工程

软件/开发工具使用

资讯