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

Bug #1687376 reported by John Replogle
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
amavisd-new (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Creating config file /etc/default/postgrey with new version
Setting up re2c (0.16-1) ...
Setting up spamassassin (3.4.1-3) ...
Adding system user `debian-spamd' (UID 129) ...
Adding new group `debian-spamd' (GID 138) ...
Adding new user `debian-spamd' (UID 129) with group `debian-spamd' ...
Creating home directory `/var/lib/spamassassin' ...
Setting up sa-compile (3.4.1-3) ...
Running sa-compile (may take a long time)
Setting up spamc (3.4.1-3) ...
Setting up zoo (2.10-28) ...
Setting up amavisd-new (1:2.10.1-2ubuntu1) ...
Creating/updating amavis user account...
Job for amavis.service failed because the control process exited with error code. See "systemctl status amavis.service" and "journalctl -xe" for details.
invoke-rc.d: initscript amavis, action "start" failed.
● amavis.service - LSB: Starts amavisd-new mailfilter
   Loaded: loaded (/etc/init.d/amavis; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-05-01 01:04:07 PDT; 9ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 14931 ExecStart=/etc/init.d/amavis start (code=exited, status=1/FAILURE)

May 01 01:04:07 john-Aspire-5742 amavis[14931]: Starting amavisd: The value of variable $myhostname is "john-Aspire-5742", but should have been
May 01 01:04:07 john-Aspire-5742 amavis[14931]: a fully qualified domain name; perhaps uname(3) did not provide such.
May 01 01:04:07 john-Aspire-5742 amavis[14931]: You must explicitly assign a FQDN of this host to variable $myhostname
May 01 01:04:07 john-Aspire-5742 amavis[14931]: in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
May 01 01:04:07 john-Aspire-5742 amavis[14931]: network name!
May 01 01:04:07 john-Aspire-5742 amavis[14931]: (failed).
May 01 01:04:07 john-Aspire-5742 systemd[1]: amavis.service: Control process exited, code=exited status=1
May 01 01:04:07 john-Aspire-5742 systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
May 01 01:04:07 john-Aspire-5742 systemd[1]: amavis.service: Unit entered failed state.
May 01 01:04:07 john-Aspire-5742 systemd[1]: amavis.service: Failed with result 'exit-code'.
dpkg: error processing package amavisd-new (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
 mariadb-server-10.0
 mariadb-server
 amavisd-new
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: amavisd-new 1:2.10.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 1 01:04:07 2017
DuplicateSignature:
 package:amavisd-new:1:2.10.1-2ubuntu1
 Setting up mariadb-server-10.0 (10.0.29-0ubuntu0.16.04.1) ...
 dpkg: error processing package mariadb-server-10.0 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
John Replogle (firestonesmith) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
from the Log
Starting amavisd: The value of variable $myhostname is "john-Aspire-5742", but should have been
 a fully qualified domain name; perhaps uname(3) did not provide such.
 You must explicitly assign a FQDN of this host to variable $myhostname
 in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
 network name!

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

In general a misconfigured service lets the upgrade fail as services are usually restarted on upgrade.

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

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

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