dnsproxy 1.16-0.1 package fails to install

Bug #681303 reported by Stefano Lenzi
34
This bug affects 13 people
Affects Status Importance Assigned to Milestone
dnsproxy (Ubuntu)
Opinion
Undecided
Unassigned

Bug Description

Binary package hint: dnsproxy

On fresh Ubuntu Maverik 10.10

when installing the dnsproxy package i get the following message and package remains in a "broken" status.

ERROR MESSAGE
Setting up dnsproxy (1.16-0.1) ...
 * Starting dnsproxy dnsproxy unable to bind socket: Cannot assign requested address
                                                                                                                 [fail]
invoke-rc.d: initscript dnsproxy, action "start" failed.
dpkg: error processing dnsproxy (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dnsproxy
E: Sub-process /usr/bin/dpkg returned an error code (1)

PACKAGE INFORMATION
Package: dnsproxy
Priority: optional
Section: universe/net
Installed-Size: 124
Maintainer: Ubuntu Developers <email address hidden>
Original-Maintainer: Patrick Schoenfeld <email address hidden>
Architecture: i386
Version: 1.16-0.1
Depends: libc6 (>= 2.4), libevent-1.4-2 (>= 1.4.13-stable), adduser, lsb-base
Filename: pool/universe/d/dnsproxy/dnsproxy_1.16-0.1_i386.deb
Size: 15722
MD5sum: 64b22c014b386675eb444417253bec66
SHA1: ed83509b08d755a43ec6b4cbd4efe41c6366f324
SHA256: fd92162c29e63bbee71ad399ae07bfbad5e7c7b3201c6683306c701f05894af0

Tags: i386 maverik
Revision history for this message
Stefano Lenzi (kismet-sl) wrote :

I have reported the issue as a new bug because all the other where bugs ( #604273, #634880, #636597, #651079, #674186) referring to a different package version

summary: - dnsproxy package fails to install
+ dnsproxy 1.16-0.1 package fails to install
Revision history for this message
Stefano Lenzi (kismet-sl) wrote :

The problem in the installation phase of the package is caused by the following part of the dnsproxy.postinst script

if [ -x "/etc/init.d/dnsproxy" ]; then
        update-rc.d dnsproxy defaults >/dev/null
        if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then
                invoke-rc.d dnsproxy start || exit $?
        else
                /etc/init.d/dnsproxy start || exit $?
        fi
fi

which try to start the dnsproxy deamon. Unfortunatly the default configuration that comes with the dnsproxy is not generic. In fact, the package file
/etc/dnsproxy.conf
contains the following line
listen 192.168.168.1
which avoid the starting of the deamon if the host has different IP address.

I believe that the dnsproxy.postinst script should not start the deamon but it should provide a message such as "Please configure the dnsproxy to tailor your need and then start it with the sudo /etc/init.d/dnsproxy start"

Revision history for this message
Stefano Lenzi (kismet-sl) wrote :
Revision history for this message
Stefano Lenzi (kismet-sl) wrote :

The patch above is not agains the installation script, because by browsing the bzr maverik branch I figured out that the buggy part of the postinst script is generated automatically by the DEBHELPER "toolchain" so I decided to modify the default network configuration of dnsproxy to be more generic

A better solution would be the modification of the configuratin uppon the actual configuration of the host (but it could be too risky)

Revision history for this message
Stefano Lenzi (kismet-sl) wrote :

Please change it to fix released if you think that is valid

Changed in dnsproxy (Ubuntu):
status: New → Opinion
tags: added: i386 maverik
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.