为什么更新arangoDB会导致nginx错误？

我有3.3.5版，想升级到3.3.11。使用了以下脚本：

#Step 1 Copy the whole data directory of arango to another location, basically a backup

cp -R /var/lib/arangodb3 /folder

#Step 2 Stop the current running process

service arangodb3 stop

#Step 3 Installing new ArangoDB, adding the key and stuff (the below is for 16.04 Ubuntu)

curl -OL https://download.arangodb.com/arangodb33/xUbuntu_16.04/Release.key
sudo apt-key add - < Release.key
sudo apt-get install apt-transport-https

sudo apt-get update
read -p "Enter the version zou want to upgrade to (For example 3.3.5)" version
sudo apt-get install arangodb3=$version

#Step 4 Start the process again with auto-upgrade option on
service arangodb3 start --database.auto-upgrade

---

一个nginx错误。我的问题是nginx在arango升级中扮演什么角色？（似乎arango无法启动自己的nginx）

问题与nginx无关。您的arangodb安装似乎没有正确完成。因此，

systemctl deamon reload

出错。。。请跑

sudo dpkg重新配置arangodb3

---

请用输出更新您的问题。

ArangoDB和Nginx在您的系统中有何关联？是否有人为ArangoDB中运行的Foxx服务设置了反向代理，升级后可能不再工作（胡乱猜测）？因此这不是arango更新的预期行为，nginx不是内部ArangoDB的一部分，对吗？ArangoDB不使用nginx中的任何内容。您可以在这里查看第三方库：集成HTTP服务器是自定义编写的。它使用的是

Boost.Asio

，但肯定没有来自Nginx的组件。问题是别的。

Setting up nginx-core (1.10.3-0ubuntu0.16.04.3) ...
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Do 2018-11-22 11:07:07 CET; 8ms ago
  Process: 16614 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
  Process: 16610 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
 Main PID: 1328 (code=exited, status=0/SUCCESS)

Nov 22 11:07:05 SB28 nginx[16614]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)
Nov 22 11:07:06 SB28 nginx[16614]: nginx: [emerg] listen() to 0.0.0.0:80, backlog 511 failed (98: Address already in use)
Nov 22 11:07:06 SB28 nginx[16614]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)
Nov 22 11:07:06 SB28 nginx[16614]: nginx: [emerg] listen() to 0.0.0.0:80, backlog 511 failed (98: Address already in use)
Nov 22 11:07:06 SB28 nginx[16614]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)
Nov 22 11:07:07 SB28 nginx[16614]: nginx: [emerg] still could not bind()
Nov 22 11:07:07 SB28 systemd[1]: nginx.service: Control process exited, code=exited status=1
Nov 22 11:07:07 SB28 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Nov 22 11:07:07 SB28 systemd[1]: nginx.service: Unit entered failed state.
Nov 22 11:07:07 SB28 systemd[1]: nginx.service: Failed with result 'exit-code'.
dpkg: error processing package nginx-core (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up arangodb3 (3.3.11) ...
Database files are up-to-date.
Errors were encountered while processing:
 nginx-core
E: Sub-process /usr/bin/dpkg returned an error code (1)