我已经为我的生产服务器编译了具有自定义路径的 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 容器时该问题仍然存在。
更新2strace -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
答案1
我在源代码中遇到了与 Ubuntu 16.04、systemd 和 NginX 1.10.1 相同的问题。
我使用的是默认nginx.service文件：
https://www.nginx.com/resources/wiki/start/topics/examples/systemd/
问题出在nginx.pid位置上。为了解决这个问题，我：
在没有服务的情况下启动 Nginx
sudo nginx start更新了定位数据库
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一切就都好了。希望这对你有帮助。
答案2
由于以下错误它挂起了：
PID file /var/run/nginx.pid not readable (yet?) after start
较新的 Linux 发行版附带systemd。如果您使用与发行版捆绑在一起的服务，那么您将已经为 systemd 配置了它。
由于您正在从源代码编译 nginx，并且您正在使用 SysV init 文件（/etc/init.d/nginx），systemd 将使用生成器来解析它（systemd-sysv-生成器）。
在您的 SysV 脚本中，您定义 pid 文件并使用以下命令启动该进程：
NGINX_PID=/var/run/nginx.pid
...
/sbin/startproc -p $NGINX_PID $NGINX_BIN
如果我没记错的话，你在 Ubuntu 上使用了一个 SUSE Linux 初始化脚本（因为启动过程命令），startproc 命令只读取 pid 文件（由-p由于 systemd 无法找到 pid 文件，因此它会挂起。
对于你的情况，解决方案要么是在 SysV init 脚本中创建 pid 文件（在/var/运行/nginx.pid位置），使用 Ubuntu SysV init 脚本，或者 systemd 脚本。
当您拥有正确的 SysV init 脚本并创建 pid 文件时，也可能会发生这种情况（不是您遇到的情况），但该文件与文件顶部注释的文件不同。systemd 生成器会读取注释，例如这个：
# pidfile: /var/run/nginxd.pid
并使用那里定义的pidfile。
更多信息：
- nginx启动脚本用于 SysV init、systemd 等。
- SysV 生成器处理pidfile 注释。
- systemd 如何读SysV 启动脚本。
- SysV 生成器手册页。
- 启动过程来源代码（SUSE FTP 站点）。
答案3
听起来像是/usr/lib/systemd/system/nginx.service格式错误。请确保设置了此行：
PIDFile=/var/run/nginx.pid
或者，您可以将该[Service]部分复制到名为 的新文件中/etc/systemd/system/nginx.service。放置在 中的单元文件/etc/systemd/system允许您覆盖部分，而无需复制包管理器安装的整个文件。
答案4
灵感https://serverfault.com/a/788576和https://askubuntu.com/a/733604
Ubuntu 20.04
我改变了两件事
首先：我运行了 service NetworkManager-wait
sudo systemctl enable NetworkManager-wait-online.service
sudo systemctl start NetworkManager-wait-online.service
第二：我在路径 PIDFile （和 pidfile）前缀中添加了var
[Service]
...
PIDFile=/var/run/nginx.pid
...
ExecStop=-/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /var/run/nginx.pid
..