package nginx-core 1.18.0-0ubuntu1 failed to install/upgrade: 已安装 nginx-core 软件包 post-installation 脚本 子进程返回错误状态 1

Bug #1886173 reported by 宋泉余
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

正在设置 nginx-core (1.18.0-0ubuntu1) ...
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 Fri 2020-07-03 17:38:06 CST; 12ms
ago
       Docs: man:nginx(8)
    Process: 35740 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_proce
ss on; (code=exited, status=1/FAILURE)

7月 03 17:38:06 songquanyu-X442UR systemd[1]: Starting A high performance web se
rver and a reverse proxy server...
7月 03 17:38:06 songquanyu-X442UR nginx[35740]: nginx: [emerg] open() "/etc/ngin
x/nginx.conf" failed (2: No such file or directory)
7月 03 17:38:06 songquanyu-X442UR nginx[35740]: nginx: configuration file /etc/n
ginx/nginx.conf test failed
7月 03 17:38:06 songquanyu-X442UR systemd[1]: nginx.service: Control process exi
ted, code=exited, status=1/FAILURE
7月 03 17:38:06 songquanyu-X442UR systemd[1]: nginx.service: Failed with result
'exit-code'.
7月 03 17:38:06 songquanyu-X442UR systemd[1]: Failed to start A high performance
 web server and a reverse proxy server.
dpkg: 处理软件包 nginx-core (--configure)时出错:
 已安装 nginx-core 软件包 post-installation 脚本 子进程返回错误状态 1
在处理时有错误发生:
 nginx-core
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nginx-core 1.18.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jul 3 17:35:35 2020
ErrorMessage: 已安装 nginx-core 软件包 post-installation 脚本 子进程返回错误状态 1
InstallationDate: Installed on 2020-04-25 (68 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: nginx
Title: package nginx-core 1.18.0-0ubuntu1 failed to install/upgrade: 已安装 nginx-core 软件包 post-installation 脚本 子进程返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
宋泉余 (songquanyu-yaya) wrote :
Revision history for this message
Robie Basak (racb) wrote :

From log:

7月 03 17:35:34 songquanyu-X442UR systemd[1]: Starting A high performance web server and a reverse proxy server...
7月 03 17:35:34 songquanyu-X442UR nginx[31274]: nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
7月 03 17:35:34 songquanyu-X442UR nginx[31274]: nginx: configuration file /etc/nginx/nginx.conf test failed

Revision history for this message
Robie Basak (racb) wrote :

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu. Specifically you do not have a /etc/nginx/nginx.conf file as shipped by the package.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in nginx (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.