package nginx-core 1.18.0-6ubuntu14.5 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1

Bug #2080915 reported by aquadevida

This bug report will be marked for expiration in 43 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

i want to install nginx in ubuntu 18 , but some error :

dpkg: error processing package nginx (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                          Errors were encountered while processing:
 nginx-core
 nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nginx-core 1.18.0-6ubuntu14.5
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Sep 17 08:06:47 2024
DpkgHistoryLog:
 Start-Date: 2024-09-17 08:06:44
 Commandline: apt install nginx
 Upgrade: libnginx-mod-http-image-filter:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), libnginx-mod-stream-geoip2:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), libnginx-mod-http-geoip2:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), nginx:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), nginx-common:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), nginx-core:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), libnginx-mod-http-xslt-filter:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), libnginx-mod-mail:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5), libnginx-mod-stream:amd64 (1.18.0-6ubuntu14.1, 1.18.0-6ubuntu14.5)
ErrorMessage: installed nginx-core package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-07-22 (787 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt 2.4.6
SourcePackage: nginx
Title: package nginx-core 1.18.0-6ubuntu14.5 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
aquadevida (aquadevida) wrote :
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you for taking the time to file a bug report.

From DpkgTerminalLog.txt:

Sep 17 08:06:47 aquadevida-IdeaPad-5-14ITL05 nginx[10522]: nginx: [emerg] getpwnam("test_domain") failed in /etc/nginx/nginx.conf:1
Sep 17 08:06:47 aquadevida-IdeaPad-5-14ITL05 nginx[10522]: nginx: configuration file /etc/nginx/nginx.conf test failed

The getpwnam call tries to find information about the user specified in its argument; in this case, "test_domain". It seems like you may have modified the configuration file by hand, since "test_domain" is not a username that the package would create/use.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Changed in nginx (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Ward (teward) wrote :

To follow up on Sergio's message, please include your `/etc/nginx/nginx.conf` file here if you believe this is a problem in the package and not your specific configuration. It's more than likely you have a `user test_domain;` option in your configuration, and that is not a valid user, meaning you're using a bad config.

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.