ubuntu – Nginx使用“service nginx start”挂起

前端之家收集整理的这篇文章主要介绍了ubuntu – Nginx使用“service nginx start”挂起前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我用生产服务器的自定义路径编译了Nginx,当我尝试使用以下命令启动/重启服务时:
service Nginx start

要么

service Nginx restart

它在不返回shell的情况下进入新行:

所以问题是我无法使用service命令控制Nginx.该服务实际上运行但它不会返回一个shell给我,所以我总是按ctrl c来取回它.

我还要提到Nginx在通过自己的Nginx命令调用它时运行正常,并使用Nginx -s stop / reload轻松停止或重新加载.

这个问题仍然存在使用systemctl start Nginx,但是systemctl stop Nginx工作得很好.

信息:

$lsb_release -a
    Distributor ID: Ubuntu
    Description:    Ubuntu 15.10
    Release:    15.10
    Codename:   wily

$uname -r
    4.2.0-27-generic

$Nginx -V
    Nginx version: Nginx/1.9.11
    built by gcc 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) 
    built with OpenSSL 1.0.2d 9 Jul 2015
    TLS SNI support enabled
    configure arguments: --sbin-path=/usr/bin/Nginx --conf-path=/etc/Nginx/Nginx.conf --error-log-path=/var/log/Nginx/error.log --http-log-path=/var/log/Nginx/access.log --with-debug --with-pcre --with-http_ssl_module

$cat /etc/default/Nginx
    Nginx_CONF_FILE=/etc/Nginx/Nginx.conf
    DAEMON=/usr/bin/Nginx

$cat /etc/init.d/Nginx
    Nginx_BIN=/usr/bin/Nginx
    test -x $Nginx_BIN || { echo "$Nginx_BIN not installed"; 
        if [ "$1" = "stop" ]; then exit 0;
        else exit 5; fi; }
    Nginx_PID=/var/run/Nginx.pid

    # Check for existence of needed config file and read it
    #Nginx_CONFIG=/etc/sysconfig/Nginx
    #test -r $Nginx_CONFIG || { echo "$Nginx_CONFIG not existing";
    #   if [ "$1" = "stop" ]; then exit 0;
    #   else exit 6; fi; }
    #
    # Read config   
    #. $Nginx_CONFIG

    # Source LSB init functions
    # providing start_daemon,killproc,pidofproc,# log_success_msg,log_failure_msg and log_warning_msg.
    # This is currently not used by UnitedLinux based distributions and
    # not needed for init scripts for UnitedLinux only. If it is used,# the functions from rc.status should not be sourced or used.
    #. /lib/lsb/init-functions

    # Shell functions sourced from /etc/rc.status:
    #      rc_check         check and set local and overall rc status
    #      rc_status        check and set local and overall rc status
    #      rc_status -v     be verbose in local rc status and clear it afterwards
    #      rc_status -v -r  ditto and clear both the local and overall rc status
    #      rc_status -s     display "skipped" and exit with status 3
    #      rc_status -u     display "unused" and exit with status 3
    #      rc_Failed        set local and overall rc status to Failed
    #      rc_Failed <num>  set local and overall rc status to <num>
    #      rc_reset         clear both the local and overall rc status
    #      rc_exit          exit appropriate to overall rc status
    #      rc_active        checks whether a service is activated by symlinks
    . /etc/rc.status

    # Reset status of this service
    rc_reset

    # Return values acc. to LSB for all commands but status:
    # 0   - success
    # 1       - generic or unspecified error
    # 2       - invalid or excess argument(s)
    # 3       - unimplemented feature (e.g. "reload")
    # 4       - user had insufficient privileges
    # 5       - program is not installed
    # 6       - program is not configured
    # 7       - program is not running
    # 8--199  - reserved (8--99 LSB,100--149 distrib,150--199 appl)
    # 
    # Note that starting an already running service,stopping
    # or restarting a not-running service as well as the restart
    # with force-reload (in case signaling is not supported) are
    # considered a success.

    case "$1" in
        start)
        echo -n "Starting Nginx "
        ## Start daemon with startproc(8). If this fails
        ## the return value is set appropriately by startproc.
        /sbin/startproc -p $Nginx_PID $Nginx_BIN

        # Remember status and be verbose
        rc_status -v
        ;;
        stop)
        echo -n "Shutting down Nginx "
        ## Stop daemon with killproc(8) and if this fails
        ## killproc sets the return value according to LSB.

        /sbin/killproc -p $Nginx_PID -TERM $Nginx_BIN

        # Remember status and be verbose
        rc_status -v
        ;;
        try-restart|condrestart)
        ## Do a restart only if the service was active before.
        ## Note: try-restart is now part of LSB (as of 1.9).
        ## RH has a similar command named condrestart.
        if test "$1" = "condrestart"; then
            echo "${attn} Use try-restart ${done}(LSB)${attn} rather than condrestart ${warn}(RH)${norm}"
        fi
        $0 status
        if test $? = 0; then
            $0 restart
        else
            rc_reset    # Not running is not a failure.
        fi
        # Remember status and be quiet
        rc_status
        ;;
        restart)
        ## Stop the service and regardless of whether it was
        ## running or not,start it again.
        $0 stop
        $0 start

        # Remember status and be quiet
        rc_status
        ;;
        force-reload)
        ## Signal the daemon to reload its config. Most daemons
        ## do this on signal 1 (SIGHUP).
        ## If it does not support it,restart the service if it
        ## is running.

        echo -n "Reload service Nginx "
        ## if it supports it:
        /sbin/killproc -p $Nginx_PID -HUP $Nginx_BIN
        #touch /run/Nginx.pid
        rc_status -v

        ## Otherwise:
        #$0 try-restart
        #rc_status
        ;;
        reload)
        ## Like force-reload,but if daemon does not support
        ## signaling,do nothing (!)

        # If it supports signaling:
        echo -n "Reload service Nginx "
        /sbin/killproc -p $Nginx_PID -HUP $Nginx_BIN
        #touch /run/Nginx.pid
        rc_status -v

        ## Otherwise if it does not support reload:
        #rc_Failed 3
        #rc_status -v
        ;;
        reopen)
            echo -n "Reopen the logfiles "
            /sbin/killproc -p $Nginx_PID -USR1 $Nginx_BIN
            rc_status -v
            ;;

        status)
        echo -n "Checking for service Nginx "
        ## Check status with checkproc(8),if process is running
        ## checkproc will return with exit status 0.

        # Return value is slightly different for the status command:
        # 0 - service up and running
        # 1 - service dead,but /run/  pid  file exists
        # 2 - service dead,but /var/lock/ lock file exists
        # 3 - service not running (unused)
        # 4 - service status unknown :-(
        # 5--199 reserved (5--99 LSB,100--149 distro,150--199 appl.)

        # NOTE: checkproc returns LSB compliant status values.
        /sbin/checkproc -p $Nginx_PID $Nginx_BIN
        # NOTE: rc_status knows that we called this init script with
        # "status" option and adapts its messages accordingly.
        rc_status -v
        ;;
        probe)
        ## Optional: Probe for the necessity of a reload,print out the
        ## argument to this init script which is required for a reload.
        ## Note: probe is not (yet) part of LSB (as of 1.9)

        test /etc/Nginx/Nginx.conf -nt /run/Nginx.pid && echo reload
        ;;
        *)
        echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"
        exit 1
        ;;
    esac
    rc_exit

更新:在CoreOS alpha上使用Docker容器时问题仍然存在.

更新2:以下是strace -o log -f service Nginx start和journalctl -xe的输出

strace -o log -f service Nginx start
Log output [too long to post here]

journalctl -xe
    Feb 26 07:25:38 lucifer polkitd(authority=local)[870]: Registered Authentication Agent for unix-process:8181:8813595 (system bus name :1.77 [/usr/bin/pkttyagent --notify-fd 5 --fallback],o
Feb 26 07:25:38 lucifer systemd[1]: Starting The Nginx HTTP and reverse proxy server...
-- Subject: Unit Nginx.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit Nginx.service has begun starting up.
Feb 26 07:25:38 lucifer Nginx[8211]: Nginx: the configuration file /etc/Nginx/Nginx.conf Syntax is ok
Feb 26 07:25:38 lucifer Nginx[8211]: Nginx: configuration file /etc/Nginx/Nginx.conf test is successful
Feb 26 07:25:38 lucifer systemd[1]: Nginx.service: PID file /var/run/Nginx.pid not readable (yet?) after start: No such file or directory
Feb 26 07:25:43 lucifer polkitd(authority=local)[870]: Unregistered Authentication Agent for unix-process:8181:8813595 (system bus name :1.77,object path /org/freedesktop/PolicyKit1/Authen
我在源代码中遇到了与Ubuntu 16.04,systemd和Nginx 1.10.1相同的问题.

我正在使用默认的Nginx.service文件
https://www.nginx.com/resources/wiki/start/topics/examples/systemd/

问题是Nginx.pid lcoation,修复它我:

在没有服务的情况下解雇了Nginx

sudo Nginx start

更新了定位db:

sudo updatedb

找到了pid文件的位置

locate "Nginx.pid"

并将Nginx.service文件更新到我找到它的位置

PIDFile=/usr/local/Nginx/logs/Nginx.pid

(不知道为什么它存储在我的日志目录中……)

然后运行daemon-reload以重新加载Nginx.service文件

systemctl daemon-reload

之后“systemctl start Nginx”就像魅力一样.希望这可以帮助.

原文链接:https://www.f2er.com/ubuntu/348915.html

猜你在找的Ubuntu相关文章