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

[Mike McNally]

Did routine update, After update I was prompted to restart. System booted OK but reported detecting a problem. The problem was related to amavisd-new. Prompt suggesting reporting the problem came up. I selected report. Now that I go to look for the detail of what went wrong it has disappeared.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: amavisd-new 1:2.10.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Mar 26 17:28:39 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-02-16 (405 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
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: Upgraded to xenial on 2016-08-21 (218 days ago)

[Robie Basak (racb)]

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

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: 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.

[Mike McNally (mmcnally)]

HI Robie:

Thanks for looking at my problem.

First I should be clear that I am no expert on computers. I have used
and enjoyed Ubuntu for many years. But though I can use it my skills on
the terminal are minimal

My problem with with amavisid-new has been around for some time. I
cannot say for sure when it first appeared but it may have arrived when
I updated to Ubuntu 16.

Now, whenever I accept an update package the system goes through its
routine and then advises that a package has failed to install. Generally
it identifies amavisid-new as the problem. Sometimes it offers to send
data to help resolve the problem. sometimes it just proceeds.

It does not give me any information that I can understand to do
troubleshooting.

To try to get information that you can use I just ran sudo apt-get
install amavisd-new on the terminal. This is the output:

mike@mike-UX305FA:~$ sudo apt-get install amavisd-new
Reading package lists... Done
Building dependency tree
Reading state information... Done
amavisd-new is already the newest version (1:2.10.1-2ubuntu1).
The following packages were automatically installed and are no longer
required:
   kde-l10n-engb libcdaudio1 libdirectfb-1.2-9 libfaac0 libslv2-9
   linux-headers-4.4.0-34 linux-headers-4.4.0-34-generic
linux-headers-4.4.0-36
   linux-headers-4.4.0-36-generic linux-headers-4.4.0-45
   linux-headers-4.4.0-45-generic linux-headers-4.4.0-51
   linux-headers-4.4.0-51-generic linux-headers-4.4.0-53
   linux-headers-4.4.0-53-generic linux-headers-4.4.0-57
   linux-headers-4.4.0-57-generic linux-headers-4.4.0-59
   linux-headers-4.4.0-59-generic linux-headers-4.4.0-66
   linux-headers-4.4.0-66-generic linux-image-4.2.0-42-generic
   linux-image-4.4.0-34-generic linux-image-4.4.0-36-generic
   linux-image-4.4.0-45-generic linux-image-4.4.0-51-generic
   linux-image-4.4.0-53-generic linux-image-4.4.0-57-generic
   linux-image-4.4.0-59-generic linux-image-4.4.0-66-generic
   linux-image-extra-4.2.0-42-generic linux-image-extra-4.4.0-34-generic
   linux-image-extra-4.4.0-36-generic linux-image-extra-4.4.0-45-generic
   linux-image-extra-4.4.0-51-generic linux-image-extra-4.4.0-53-generic
   linux-image-extra-4.4.0-57-generic linux-image-extra-4.4.0-59-generic
   linux-image-extra-4.4.0-66-generic linux-signed-image-4.2.0-42-generic
   linux-signed-image-4.4.0-34-generic linux-signed-image-4.4.0-36-generic
   linux-signed-image-4.4.0-45-generic linux-signed-image-4.4.0-51-generic
   linux-signed-image-4.4.0-53-generic linux-signed-image-4.4.0-57-generic
   linux-signed-image-4.4.0-59-generic linux-signed-image-4.4.0-66-generic
   ubuntu-core-launcher
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
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.servic...

[Joshua Powers (powersj)]

Hi Mike,

Can you get the full output of the following commands by running:

systemctl status amavis.service
journalctl -xe

Both appear cut off in your last post because of the "..." at the end of the lines. I ask because I believe these lines will help you out:

Mar 28 13:58:20 mike-UX305FA amavis[30675]: The value of variable
$myhostn...n
Mar 28 13:58:20 mike-UX305FA amavis[30675]: a fully qualified domain
name;....
Mar 28 13:58:20 mike-UX305FA amavis[30675]: You must explicitly assign
a F...e

You probably still need to set the FQDN in the amavisd config file.

[Mike McNally (mmcnally)]

Thanks for your attention Joshua:

I ran the command. The output is pasted below:

If I need to put in FQDN could you please coach me on how to?

Regards

Mike

mike@mike-UX305FA:~$
mike@mike-UX305FA:~$ systemctl status amavis.service
● amavis.service - LSB: Starts amavisd-new mailfilter
    Loaded: loaded (/etc/init.d/amavis; bad; vendor preset: enabled)
    Active: failed (Result: exit-code) since Tue 2017-03-28 13:58:20
EDT; 22h ago
      Docs: man:systemd-sysv-generator(8)
   Process: 30675 ExecStart=/etc/init.d/amavis start (code=exited,
status=1/FAILU

Mar 28 13:58:20 mike-UX305FA amavis[30675]: The value of variable
$myhostname
Mar 28 13:58:20 mike-UX305FA amavis[30675]: a fully qualified domain
name; per
Mar 28 13:58:20 mike-UX305FA amavis[30675]: You must explicitly assign
a FQDN
Mar 28 13:58:20 mike-UX305FA amavis[30675]: in
/etc/amavis/conf.d/05-node_id,
Mar 28 13:58:20 mike-UX305FA amavis[30675]: network name!
Mar 28 13:58:20 mike-UX305FA amavis[30675]: (failed).
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Control process
exited,
Mar 28 13:58:20 mike-UX305FA systemd[1]: Failed to start LSB: Starts
amavisd-new
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Unit entered
failed sta
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Failed with
result 'exi
...skipping...
● amavis.service - LSB: Starts amavisd-new mailfilter
    Loaded: loaded (/etc/init.d/amavis; bad; vendor preset: enabled)
    Active: failed (Result: exit-code) since Tue 2017-03-28 13:58:20
EDT; 22h ago
      Docs: man:systemd-sysv-generator(8)
   Process: 30675 ExecStart=/etc/init.d/amavis start (code=exited,
status=1/FAILU

Mar 28 13:58:20 mike-UX305FA amavis[30675]: The value of variable
$myhostname
Mar 28 13:58:20 mike-UX305FA amavis[30675]: a fully qualified domain
name; per
Mar 28 13:58:20 mike-UX305FA amavis[30675]: You must explicitly assign
a FQDN
Mar 28 13:58:20 mike-UX305FA amavis[30675]: in
/etc/amavis/conf.d/05-node_id,
Mar 28 13:58:20 mike-UX305FA amavis[30675]: network name!
Mar 28 13:58:20 mike-UX305FA amavis[30675]: (failed).
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Control process
exited,
Mar 28 13:58:20 mike-UX305FA systemd[1]: Failed to start LSB: Starts
amavisd-new
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Unit entered
failed sta
Mar 28 13:58:20 mike-UX305FA systemd[1]: amavis.service: Failed with
result 'exi
~
~
~
~
~
~
~
...skipping...
● amavis.service - LSB: Starts amavisd-new mailfilter
    Loaded: loaded (/etc/init.d/amavis; bad; vendor preset: enabled)
    Active: failed (Result: exit-code) since Tue 2017-03-28 13:58:20
EDT; 22h ago
      Docs: man:systemd-sysv-generator(8)
   Process: 30675 ExecStart=/etc/init.d/amavis start (code=exited,
status=1/FAILU

Mar 28 13:58:20 mike-UX305FA amavis[30675]: The value of variable
$myhostname
Mar 28 13:58:20 mike-UX305FA amavis[30675]: a fully qualified domain
name; per
Mar 28 13:58:20 mike-UX305FA amavis[30675]: You must explicitly assign
a FQDN
Mar 28 13:58:20 mike-UX305FA amavis[30675]: in
/etc/amavis/conf.d/05-node_id,
Mar 28 13:58:20 mike-UX305FA amavis[30675]: network name!
Mar 2...

[Launchpad Janitor (janitor)]

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