package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: alamprotsess installed post-installation script tagastas lõpetamisel veakoodi 1

Bug #1747255 reported by sven.katkosilt@gmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

synaptic

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apache2 2.4.18-2ubuntu3.5
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Apache2ConfdDirListing: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sun Feb 4 14:02:51 2018
ErrorMessage: alamprotsess installed post-installation script tagastas lõpetamisel veakoodi 1
InstallationDate: Installed on 2018-02-03 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: apache2
Title: package apache2 2.4.18-2ubuntu3.5 failed to install/upgrade: alamprotsess installed post-installation script tagastas lõpetamisel veakoodi 1
UpgradeStatus: No upgrade log present (probably fresh install)
error.log:

Revision history for this message
sven.katkosilt@gmail.com (sven-katkosilt) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Sven,
From your log:
insserv: warning: script 'jabber-irc' missing LSB tags and overrides
insserv: There is a loop between service LazyLibrarian and jabber-irc if stopped
insserv: loop involving service jabber-irc at depth 2
insserv: loop involving service LazyLibrarian at depth 1
insserv: Stopping jabber-irc depends on lazylibrarian and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!

On upgrade of apache it needs to be restarted and maybe startup files adapted.
But something else on your system seems broken and causing a loop.

jabber-irc is from the archive, but LazyLibrarian is not and likely there is a conflict in the headers of that init script.
You might take a look at /etc/init.d/LazyLibrarian but since it is not part of Ubuntu I'd know of there is not more I can do for you atm.

I'd recommend either fixing the LazyLibrarian file or if you don't need it just getting rid of it.
That as well I can't help a lot as I don't know how you installed it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

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

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or 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 apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in apache2 (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.