package apache2 2.4.29-1ubuntu4.5 failed to install/upgrade: end of file on stdin at conffile prompt

Bug #1816334 reported by Luke H on 2019-02-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

Error occurred while upgrading AWS EC2 instance from 16.04 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apache2 2.4.29-1ubuntu4.5
ProcVersionSignature: Ubuntu 4.4.0-1075.85-aws 4.4.167
Uname: Linux 4.4.0-1075-aws x86_64
Apache2ConfdDirListing: False

ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Mon Feb 18 03:07:39 2019
Ec2AMI: ami-79873901
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2a
Ec2InstanceType: t2.micro
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: end of file on stdin at conffile prompt
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
 apt 1.6.8
SourcePackage: apache2
Title: package apache2 2.4.29-1ubuntu4.5 failed to install/upgrade: end of file on stdin at conffile prompt
UpgradeStatus: Upgraded to bionic on 2019-02-18 (0 days ago)
modified.conffile..etc.apache2.apache2.conf: [modified]
modified.conffile..etc.apache2.mods-available.cern_meta.load: [modified]
modified.conffile..etc.apache2.mods-available.dir.conf: [modified]
modified.conffile..etc.apache2.mods-available.http2.load: [deleted]
modified.conffile..etc.apache2.mods-available.imagemap.load: [modified]
modified.conffile..etc.apache2.mods-available.proxy_hcheck.load: [deleted]
modified.conffile..etc.apache2.mods-available.proxy_http2.load: [deleted]
modified.conffile..etc.apache2.sites-available.000-default.conf: [modified]
modified.conffile..etc.apache2.sites-available.default-ssl.conf: [modified]
mtime.conffile..etc.apache2.apache2.conf: 2018-02-27T02:31:58.893393
mtime.conffile..etc.apache2.mods-available.cern_meta.load: 2019-02-18T02:59:57.471017
mtime.conffile..etc.apache2.mods-available.dir.conf: 2018-02-14T05:16:43.207354
mtime.conffile..etc.apache2.mods-available.imagemap.load: 2019-02-18T02:59:57.475017
mtime.conffile..etc.apache2.sites-available.000-default.conf: 2018-02-28T01:40:10.007915
mtime.conffile..etc.apache2.sites-available.default-ssl.conf: 2018-02-28T01:50:49.869977

Luke H (lukehenry4) wrote :
Paride Legovini (legovini) wrote :

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

From DpkgTerminalLog.gz looks like the upgrade process got interrupted while waiting for input from your side (e.g. ssh disconnected during the upgrade):

Configuration file '/etc/apache2/apache2.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : start a shell to examine the situation
 The default action is to keep your current version.
*** apache2.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package apache2 (--configure):
 end of file on stdin at conffile prompt

Since there isn't enough information in your report to differentiate between a local configuration problem and 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:

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" 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
Luke H (lukehenry4) wrote :

@legovini I believe you are right. I was able to complete this process without issue later, and it being a client-side interrupt makes sense to me.

Thanks for the response!

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  Edit
Everyone can see this information.

Other bug subscribers