Ubuntu

package aiccu 20070115-9 failed to install/upgrade: subproces post-installation script werd gedood door signaal (Interrupt)

Reported by b-art on 2009-10-22
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aiccu (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: aiccu

E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: subproces post-installation script werd gedood door signaal (Interrupt)
NonfreeKernelModules: fglrx
Package: aiccu 20070115-9
SourcePackage: aiccu
Title: package aiccu 20070115-9 failed to install/upgrade: subproces post-installation script werd gedood door signaal (Interrupt)
Uname: Linux 2.6.28-16-generic x86_64

b-art (ubuntu-b-art) wrote :
Jeroen Massar (massar) wrote :

> ErrorMessage: subproces post-installation script werd gedood door signaal (Interrupt)

Is Dutch for: "subprocess post-installation script was killed by signal (Interrupt)"

I assume somebody thus hit CTRL-C.

Note that the Terminal Log contains:

"Warning: Couldn't find global Tunnel Brokers List, please check your DNS settings and read the FAQ."

This tends to indicate that the user has a problem with their DNS resolver (or one of that resolvers upstreams) which fail to pass large TXT records.

Do a:
for i in `cat /etc/resolv.conf | grep nameserver | cut -f2 -d' '`; do echo -e "\n\n$i =========="; dig +short @$i _aiccu.sixxs.net txt; done

The one which does not properly respond is the broken one. This might cause most of your IPv6 resolving (AAAA records) to likely fail too, although that is just a 'might' as the problem here is long DNS responses which can be caused by the TCP-response that is needed and thus a firewall blocking DNS requests over TCP could be the culprit.

Example response of the above:

192.168.0.1 ==========
;; Truncated, retrying in TCP mode.
"UKERNA" "tsp://broker.ipv6.ac.uk" "http://www.broker.ipv6.ac.uk" "gb"
"Hexago / Freenet6" "tsp://broker.freenet6.net" "http://www.freenet6.net" "ca"
"ECS Southampton" "tsp://broker.ecs.soton.ac.uk" "http://broker.ecs.soton.ac.uk" "gb"
"ACADEMIA Sinica Computing Centre" "tsp://tb2.ipv6.ascc.net" "http://tb2.ipv6.ascc.net" "tw"
"Wanadoo France" "tsp://ts.ipv6.wanadoo.fr" "http://www.ipv6.wanadoo.fr" "fr"
"# http://www.sixxs.net/tools/aiccu/brokers/"
"AARNet" "tsp://broker.aarnet.net.au" "http://broker.aarnet.net.au" "au"
"# AICCU TIC/TSP Servers"
"# <name> | <url> | website | tld's"
"SixXS" "tic://tic.sixxs.net" "http://www.sixxs.net" "be de ee fi gb ie it nl nz pl pt si se us"

Note that the results might return in a different order. The same content should be returned though.

Marcin Cieślak (saperski) wrote :

I have run into this recently on one of the Ubuntu servers. However, this does not seem to be related
to Ubuntu or Debian at all.

The problem is that upstream DNS is running:

$ dig +short chaos txt version.bind.
"PowerDNS Recursor 3.1.4 $Id: pdns_recursor.cc 917 2006-11-07 12:23:51Z ahu $"

PowerDNS 3.1.4 is known not to support multi-line TXT entries.
For details see my collection of links here:

http://delicious.com/saper/powerdns+txt+bug

The results returned are:

; <<>> DiG 9.5.1-P2.1 <<>> in txt _aiccu.sixxs.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29033
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_aiccu.sixxs.net. IN TXT

;; ANSWER SECTION:
_aiccu.sixxs.net. 2478 IN TXT "# http://www.sixxs.net/tools/aiccu/brokers/"
_aiccu.sixxs.net. 2478 IN TXT "SixXS"
_aiccu.sixxs.net. 2478 IN TXT "# AICCU TIC/TSP Servers"
_aiccu.sixxs.net. 2478 IN TXT "# <name> | <url> | website | tld's"

;; Query time: 10 msec
;; SERVER: 213.134.134.134#53(213.134.134.134)
;; WHEN: Fri May 7 23:01:53 2010
;; MSG SIZE rcvd: 191

And consequently, "aiccu brokers" returns only "SixXS|".

While this is not per se a bug in AICCU, I think we can make it a bit more careful
about what is returned from DNS and to ignore all records shorter than 4 "columns".

Attached patch does this and fixes the debian package issue (I have re-generated
the package and it installs and configures fine).

I didn't check whether it compiles on Windows.

Lars Düsing (lars.duesing) wrote :

Thank you for reporting this bug to Ubuntu. Jaunty Jackalope (9.04) reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Precise Pangolin (10.04) and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

Changed in aiccu (Ubuntu):
status: New → Incomplete
Marcin Cieślak (saperski) wrote :

Lars,

this bug is about how broken environment (for example, problem with DNS resolution) breaks the installation process
(when it probably shouldn't).

Did you try to reproduce this bug with a broken DNS resolver? You can use PowerDNS 3.1.4 to test for this bug
(like installing PowerDNS locally and pointing /etc/resolv.conf to it).

Installation script should fallback to something sane when the package is being installed on host
with broken or no network connectivity.

If you need more help in reproducing this bug, please let me know.

Marcin,

Ok, this may be a problem, but who installs an IPv6-tunnel on a machine
without a working networking stack? And how should aiccu react if
anybody does it either?
About powerdns - 3.1.4 ? precise has 3.0-1ubuntu1. Homepage has 3.1-1.

And the problem described should be no problem with powerdns any more -
since 2007/03/25 - see http://wiki.powerdns.com/trac/changeset/996/trunk

Launchpad Janitor (janitor) wrote :

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

Changed in aiccu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers