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

Asked by crazy_j

Binary package hint: amavisd-new

Upgrades seem to be an issue with all kubuntu major things. adept it's self seems to be very buggy, although it may be charter communications(my cable internet). Kind of doubtful as I did an Install of 7.10 on my mothers computer and she has a diffrent provider, and still had update issues, inside of 7.10, now upgrading to 8.04 seems even tugher.

ProblemType: Package
Architecture: i386
Date: Mon Mar 24 06:06:44 2008
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: amavisd-new 1:2.4.2-6.2ubuntu1
PackageArchitecture: all
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.4.2-6.2ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux Bobbie-Jo 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu amavisd-new Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
crazy_j (slapping-monkeys) said :
#1
Revision history for this message
Scott Kitterman (kitterman) said :
#2

Did you read the error message:

  The value of variable $myhostname is "Bobbie-Jo", 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!

Do what it says and the package installation will finish.

Revision history for this message
crazy_j (slapping-monkeys) said :
#3

I'm new to linux so how do I do that?

Revision history for this message
Scott Kitterman (kitterman) said :
#4

I'm going to convert this over to a support question then so you can get help with it.

Revision history for this message
Scott Kitterman (kitterman) said :
#5

Bug reporter needs help editing his configuration file.

Revision history for this message
Daniel Hahler (blueyed) said :
#6

In fact, it's a bug in amavis, which does not accept hyphens in the hostname, which is valid according to http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names (and otherwise "hostname --fqdn" would not output it, which gets done in the conf file mentioned above).

Revision history for this message
Daniel Hahler (blueyed) said :
#7

Bleh.. mixed hostname with top level domain, which gets checked.
Although "foo.bar-bar" is a valid FQDN according to "hostname --fqdn", allowing a hyphen there would not fix the problem for crazy_j: there's no TLD at all.

Converting to a question again, sorry.

Revision history for this message
Daniel Hahler (blueyed) said :
#8

crazy_j, instead of editing amavisd-new's config file, you should make sure that "hostname --fqdn" returns a FullyQualifiedDomainName.

To accomplish this, please open the file /etc/hosts and edit the first line starting with "127.0.0.1", so that it contains a FQDN (which is "hostname.TLD", TLD=TopLevelDomain).
Mine looks like this:
127.0.0.1 base.local localhost.localdomain localhost base

You need to edit the file as "root"/superuser, so in KDE do it by entering the following into the application starter, which you can invoke by pressing "Alt-F2":
kdesudo kate /etc/hosts

This opens kate as the superuser. Edit and save the file.
Now "hostname -f" should output the first entry from your 127.0.0.1 line and amavisd will be happy, if it's a FQDN.

Hope that helps, and sorry for the initial confusion.

Can you help with this problem?

Provide an answer of your own, or ask crazy_j for more information if necessary.

To post a message you must log in.