package amavisd-new 1:2.11.0-1ubuntu1 failed to install/upgrade: installed amavisd-new package post-installation script subprocess returned error exit status 1

[vbif-nfyz]

1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: amavisd-new 1:2.11.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 chromium-codecs-ffmpeg-extra:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Aug 18 12:20:41 2018
ErrorMessage: installed amavisd-new package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-11 (98 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.11.0-1ubuntu1 failed to install/upgrade: installed amavisd-new package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-06-21 (57 days ago)

[Christian Ehrhardt  (paelzer)]

From your log:
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: Starting amavisd: head: cannot open '/etc/mailname' for reading: No such file or directory
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: The value of variable $myhostname is "vbif-System-Product-Name", but should have been
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: a fully qualified domain name; perhaps uname(3) did not provide such.
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: You must explicitly assign a FQDN of this host to variable $myhostname
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: network name!

amavis has to guess your hostname for a valid config and it does so from your hostname.
If that doesn't qualify as FQDN it will fail.

Please adapt the config and the service as well as the upgrade will work

[Christian Ehrhardt  (paelzer)]

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

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

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.

[Juhani Numminen (jsonic)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #1792178, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.