出现 Apache2 Ubuntu 默认页面

Question

一直在使用 Rails 5 并通过 Vagrant 设置一切。我已经成功地让我的网站通过 Nginx 和 Webrick 运行。当我尝试使用 Unicorn 时，它会显示 Apache2 默认页面。我删除了sites-available 中的默认值，并在sites-enabled 下创建了一个链接到nginx.conf 的默认值。

这是我的nginx.conf 文件：

upstream unicorn {
  server unix:/tmp/unicorn.mysiteNginx.sock fail_timeout=0;
}

server {
  listen 80 default deferred;
  # server_name projectname.com;
  root /vagrant/public;
  try_files $uri/home.html $uri @unicorn;
  location @unicorn {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
    proxy_pass http://unicorn;
  }

  error_page 500 502 503 504 /500.html;
  client_max_body_size 4G;
  keepalive_timeout 10;
  }

unicorn.rb 文件：

working_directory "/vagrant"
pid "/vagrant/tmp/pids/unicorn.pid"
stderr_path "/vagrant/log/unicorn.log"
stdout_path "/vagrant/log/unicorn.log"

listen "/tmp/unicorn.mysiteNginx.sock"
worker_processes 2
timeout 30

unicorn_init.sh文件：

#!/bin/sh
set -e
# Example init script, this can be used with nginx, too,
# since nginx and unicorn accept the same signals

# Feel free to change any of the following variables for your app:
# Remember -E production flag for production & sudo -c "$CMD" - user so it's not run as root!
TIMEOUT=${TIMEOUT-60}
APP_ROOT=/vagrant
PID=$APP_ROOT/tmp/pids/unicorn.pid
CMD="/home/vagrant/.rvm/bin/ruby-2.3.1_unicorn -D -c $APP_ROOT/config/unicorn.rb -E production"
action="$1"
set -u

old_pid="$PID.oldbin"

cd $APP_ROOT || exit 1

sig () {
        test -s "$PID" && kill -$1 `cat $PID`
}

oldsig () {
        test -s $old_pid && kill -$1 `cat $old_pid`
}

case $action in
start)
        sig 0 && echo >&2 "Already running" && exit 0
        su -c "$CMD" - vagrant
        ;;
stop)
        sig QUIT && exit 0
        echo >&2 "Not running"
        ;;
force-stop)
        sig TERM && exit 0
        echo >&2 "Not running"
        ;;
restart|reload)
        sig HUP && echo reloaded OK && exit 0
        echo >&2 "Couldn't reload, starting '$CMD' instead"
        su -c "$CMD" - vagrant
        ;;
upgrade)
        if sig USR2 && sleep 2 && sig 0 && oldsig QUIT
        then
                n=$TIMEOUT
                while test -s $old_pid && test $n -ge 0
                do
                        printf '.' && sleep 1 && n=$(( $n - 1 ))
                done
                echo

                if test $n -lt 0 && test -s $old_pid
                then
                        echo >&2 "$old_pid still exists after $TIMEOUT seconds"
                        exit 1
                fi
                exit 0
        fi
        echo >&2 "Couldn't upgrade, starting '$CMD' instead"
        su -c "$CMD" - vagrant
        ;;
reopen-logs)
        sig USR1
        ;;
*)
        echo >&2 "Usage: $0 <start|stop|restart|upgrade|force-stop|reopen-logs>"
        exit 1
        ;;
esac

在提交此问题之前，我对堆栈溢出进行了一些研究，并对类似问题进行了一些故障排除，但到目前为止没有成功。任何帮助将不胜感激！

---更新 1---

当我执行sudo service unicorn restart 时，这就是error.log 中显示的内容：

017/08/07 22:41:17 [notice] 2387#2387: signal process started
2017/08/07 22:41:18 [emerg] 2391#2391: bind() to 0.0.0.0:80 failed (98: Address already in use)
2017/08/07 22:41:18 [emerg] 2391#2391: bind() to 0.0.0.0:80 failed (98: Address already in use)
2017/08/07 22:41:18 [emerg] 2391#2391: bind() to 0.0.0.0:80 failed (98: Address already in use)
2017/08/07 22:41:18 [emerg] 2391#2391: bind() to 0.0.0.0:80 failed (98: Address already in use)
2017/08/07 22:41:18 [emerg] 2391#2391: bind() to 0.0.0.0:80 failed (98: Address already in use)
2017/08/07 22:41:18 [emerg] 2391#2391: still could not bind()

---更新 2---

在sudo lsof -i:80之后登录

COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nginx   1854     root    6u  IPv4  11471      0t0  TCP *:http (LISTEN)
nginx   1855 www-data    6u  IPv4  11471      0t0  TCP *:http (LISTEN)

Answer 1

首先你应该运行 ***

sudo systemctl stop apache2

---

之后

sudo systemctl 重启 nginx

sudo systemctl reload nginx

Answer 2

EADDRINUSE (98) 错误非常明显。您不能将多个网络服务器绑定 (2) 到端口 80。其中一个必须离开，以便为您喜欢的一个腾出空间。

使用sudo lsof -i:80 来识别已经绑定到该TCP 端口的进程。 Root 应该发出kill 或类似service apache stop 的命令来临时允许另一台服务器获取端口。从长远来看，systemctl disable apache 之类的东西将确保端口 80 在重新启动后仍然可用。或者在其配置文件中切换到非默认端口。