package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
amavisd-new (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Setting up amavisd-new (1:2.10.1-4ubuntu1) ...
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.
Active: failed (Result: exit-code) since Sat 2016-12-10 17:36:07 CST; 6ms ago
Docs: man:systemd-
Process: 4329 ExecStart=
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Dec 10 17:36:07 vkmore-
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package amavisd-new (--configure):
subprocess installed post-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: amavisd-new 1:2.10.1-4ubuntu1
ProcVersionSign
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sat Dec 10 17:28:38 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-10-29 (42 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitec
RelatedPackageV
dpkg 1.18.10ubuntu1
apt 1.3.1
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-08 (32 days ago)
tags: | removed: need-duplicate-check |
Hello and thank you for reporting this bug.
I am unable to reproduce this in a LXD yakkety container. To rule out a configuration issue, can you please provide the output of:
systemctl status amavis.service
journalctl -xe
upon the failure; as well as, possibly, the output from runing
sudo systemctl start amavis.service
and then move this bug back to New?