Nginx si blocca con "service nginx start"

Ho compilato nginx con percorsi personalizzati per il mio server di produzione e quando provo ad avviare / riavviare il servizio usando:

service nginx start

o

service nginx restart

Entra in una nuova linea senza restituire la shell:

Quindi il problema è che non riesco a controllare nginx usando il servicecomando. Il servizio in realtà funziona ma non mi restituirà una shell, quindi devo sempre premere ctrl+ cper riaverlo.

Devo anche menzionare che nginx funziona bene quando lo chiama con il suo nginxcomando e si arresta o ricarica facilmente usando nginx -s stop/reload.

Anche questo problema persiste systemctl start nginx, ma systemctl stop nginxfunziona perfettamente.

Informazioni:

$ 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

AGGIORNAMENTO : il problema persiste anche durante l'utilizzo del contenitore Docker su CoreOS alpha.

AGGIORNAMENTO 2 : Ecco le uscite per strace -o log -f service nginx starte journalctl -xe:

strace -o log -f service nginx start Log output [troppo lungo per pubblicare qui]

    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

Sto riscontrando lo stesso problema con Ubuntu 16.04, systemd e NginX 1.10.1 dalla fonte.

Stavo usando il file nginx.service predefinito: https://www.nginx.com/resources/wiki/start/topics/examples/systemd/

Il problema era la nginx.pid lcoation, per risolverlo I:

Nginx infornato senza il servizio

sudo nginx start

Aggiornato il localizzatore db:

sudo updatedb

Trovato il percorso del file pid

locate "nginx.pid"

E aggiornato il file nginx.service nella posizione in cui l'ho trovato

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

(Non ho idea del perché sia ​​archiviato nella mia directory dei registri ...)

Quindi eseguire daemon-reload per ricaricare il file nginx.service

systemctl daemon-reload

Successivamente "systemctl start nginx" funziona come un incantesimo. Spero che questo ti aiuti.

Si blocca a causa di questo errore:

PID file /var/run/nginx.pid not readable (yet?) after start

Le distribuzioni Linux più recenti vengono fornite con systemd . Se usi un servizio in bundle con la tua distribuzione, lo otterrai già configurato per systemd.

Dato che stai compilando nginx dai sorgenti e stai usando un file init SysV ( /etc/init.d/nginx ), systemd userà un generatore per analizzarlo ( systemd-sysv-generator ).

Nello script SysV, si definisce il file pid e si avvia il processo con:

NGINX_PID=/var/run/nginx.pid
...
/sbin/startproc -p $NGINX_PID $NGINX_BIN

Se non sbaglio stai usando uno script init SUSE Linux su Ubuntu (a causa del comando startproc ), quel comando startproc legge solo il file pid (specificato dal parametro -p ), non lo crea, quindi systemd non riesce a trovare un file pid e si blocca.

Nel tuo caso, la soluzione è creare il file pid nel tuo script SysV init (nella posizione /var/run/nginx.pid ), utilizzare uno script init SysV Ubuntu o uno systemd.

Questo può accadere anche (non quello che ti sta succedendo) quando hai uno script init SysV corretto che crea un file pid, ma è diverso da quello commentato nella parte superiore del file. Il generatore di systemd legge i commenti, ad esempio questo:

# pidfile: /var/run/nginxd.pid

E utilizza il file pid definito lì.

Maggiori informazioni:

• script init nginx per init SysV, systemd, ecc.
• Generatore SysV che elabora il commento del pidfile .
• Come systemd legge gli script di inizializzazione SysV.
• Pagina man del generatore SysV .
• codice sorgente startproc (sito FTP SUSE).

Sembra /usr/lib/systemd/system/nginx.servicemalformato. Assicurarsi che questa riga sia impostata:

PIDFile=/var/run/nginx.pid

In alternativa puoi copiare la [Service]sezione in un nuovo file chiamato /etc/systemd/system/nginx.service. I file di unità inseriti /etc/systemd/systemconsentono di sovrascrivere le sezioni senza duplicare l'intero file installato dal gestore pacchetti.