package amavisd-new 1:2.11.0-1ubuntu1 failed to install/upgrade: Unterprozess installed amavisd-new package post-installation script gab den Fehler-Ausgangsstatus 1 zurück

Bug #1767709 reported by Juergen Gross
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
amavisd-new (Ubuntu)
Expired
Low
Unassigned

Bug Description

?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: amavisd-new 1:2.11.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat Apr 28 20:54:37 2018
ErrorMessage: Unterprozess installed amavisd-new package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2018-04-27 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
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.1
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.11.0-1ubuntu1 failed to install/upgrade: Unterprozess installed amavisd-new package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Juergen Gross (highlander-bhv) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in amavisd-new (Ubuntu):
status: New → Confirmed
Revision history for this message
Joshua Powers (powersj) wrote :

From terminal log:

Apr 28 20:54:37 HPhome amavis[386]: Starting amavisd: head: cannot open '/etc/mailname' for reading: No such file or directory
Apr 28 20:54:37 HPhome amavis[386]: The value of variable $myhostname is "HPhome", but should have been
Apr 28 20:54:37 HPhome amavis[386]: a fully qualified domain name; perhaps uname(3) did not provide such.
Apr 28 20:54:37 HPhome amavis[386]: You must explicitly assign a FQDN of this host to variable $myhostname
Apr 28 20:54:37 HPhome amavis[386]: in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
Apr 28 20:54:37 HPhome amavis[386]: network name!

Revision history for this message
Joshua Powers (powersj) wrote :

Hey, thanks for filing a bug, howerver if you take a look at the pasted output above, you need to complete the setup and configuration of amavis before it will work properly.

Changed in amavisd-new (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
Simon (simon-2) wrote :

Hey, I have the same issue on Ubuntu Server 18.04, however, hostname --fqdn clearly returns a FQDN, which also points to the IP address of my server, and /etc/mailname exists with valid content.
I guess it's a bug, however, I couldn't find any evidence or log.

information type: Public → Public Security
information type: Public Security → Public
cesar (curbina)
Changed in amavisd-new (Ubuntu):
status: Incomplete → Fix Committed
Robie Basak (racb)
Changed in amavisd-new (Ubuntu):
status: Fix Committed → 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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.