package nginx 1.10.0-0ubuntu0.16.04.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

Bug #1620627 reported by Mikle
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

problem with nginx-common or nginx-core

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nginx 1.10.0-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Sep 6 17:19:03 2016
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2016-07-05 (63 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: nginx
Title: package nginx 1.10.0-0ubuntu0.16.04.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mikle (zeronerorgb) wrote :
Revision history for this message
Nish Aravamudan (nacc) wrote :

Hello and thank you for filing this bug report! Unfortunately it's not quite obvious from the provided logs what exactly is the root-cause.

It does seem related, at least, to:

сен 06 20:17:33 Novohudonossor systemd[1]: nginx.service: PID file /run/nginx.pid not readable (yet?) after start: No such file or directory

Is /run mounted r/w? Have you seen any other fs related issues? It seems like /run is a tmpfs and is not anywhere near full based on the `df` output. Sorry for the various questions, but just trying to narrow down what might be the cause.

Changed in nginx (Ubuntu):
status: New → Incomplete
Revision history for this message
Simon Déziel (sdeziel) wrote :

Something is weird with the timestamps of the logs:

-- Logs begin at Вт 2016-09-06 20:17:29 SAMT, end at Вт 2016-09-06 17:19:17 SAMT. --
сен 06 20:17:33 Novohudonossor systemd[1]: Starting A high performance web server and a 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.
сен 06 20:17:33 Novohudonossor systemd[1]: nginx.service: PID file /run/nginx.pid not readable (yet?) after start: No such file or directory
сен 06 17:19:03 Novohudonossor systemd[1]: nginx.service: Start operation timed out. Terminating.
сен 06 17:19:03 Novohudonossor systemd[1]: Failed to start A high performance web server and a reverse proxy server.

As if time went backward or a different timezone was used.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nginx (Ubuntu) because there has been no activity for 60 days.]

Changed in nginx (Ubuntu):
status: Incomplete → Expired
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.