Nginx挂起使用“服务nginx启动”

我编译nginx与我的生产服务器的自定义path，当我尝试启动/重新启动服务使用：

service nginx start 

要么

 service nginx restart 

它在不返回shell的情况下进入一个新行：

所以问题是我不能使用service命令来控制nginx。 该服务实际上运行，但它不会返回一个壳给我，所以我总是不得不按Ctrl + C把它拿回来。

• 你如何命名docker集装箱？
• 如何将文件添加到没有root权限的docker容器？
• 无法使用RUN从Dockerfile写入/ etc / hosts文件
• 在Ubuntu 15.04上启动docker-systemd与systemd
• 如何获得php-fpm在docker容器中运行时login到stdout / stderr

我也不得不提到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 (eg "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的输出strace -o log -f service nginx start和journalctl -xe ：

strace -o log -f service nginx start 日志输出[太长，不能在这里发表]

  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 

 sudo nginx start 

 sudo updatedb 

 locate "nginx.pid" 

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

 systemctl daemon-reload 

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

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

 # pidfile: /var/run/nginxd.pid 

 PIDFile=/var/run/nginx.pid