apt-cacher-ng start displays an invalid error message

[João Pinto]

Binary package hint: apt-cacher-ng

Description: Ubuntu jaunty (development branch)
Release: 9.04

Starting apt-cacher-ng services produces an incorrect error message:
Couldn't bind socket: Address already in use

root@janito-desktop:~# netstat -nap | more | grep "3142"
root@janito-desktop:~# /etc/init.d/apt-cacher-ng start
 * Starting apt-cacher-ng apt-cacher-ng Couldn't bind socket: Address already in use
                                                                                                                                                                             [ OK ]
root@janito-desktop:~# netstat -nap | more | grep "3142"
tcp 0 0 0.0.0.0:3142 0.0.0.0:* LISTEN 3591/apt-cacher-ng
root@janito-desktop:~#

[Christoph Korn (c-korn)]

I can confirm the issue:
korn@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
 * Starting apt-cacher-ng apt-cacher-ng Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could be create/prepared. Check the network, check or unset the BindAddress directive.
                                                                                          [fail]
korn@ubuntu:~/Desktop/apt-cacher-ng$ sudo netstat -nap | more | grep "3142"
tcp 0 0 0.0.0.0:3142 0.0.0.0:* LISTEN 4087/apt-cacher-ng

apt-cacher-ng:
  Installed: 0.3.3-1
  Candidate: 0.3.3-1
  Version table:
 *** 0.3.3-1 0
        500 http://de.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

[Eduard Bloch (edi-gmx)]

That's correct. The error message is about the IPv6 socket not being created. Unfortunately the order of libc (getaddrinfo result) seems to have been changed and that causes the problem now.

If you need IPv6, there is a quick workaround: put all your interface IPs (in v4 and v6 versions) into the BindAddress list in the config.

Better workaround: integrate the current Debian Unstable 0.3.4 version into Ubuntu.

[Christoph Korn (c-korn)]

The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168

[Christoph Korn (c-korn)]

Already got one ACK in bug 344168.

[Christoph Korn (c-korn)]

Second ACK.
FFe granted.

[Christoph Korn (c-korn)]

bug 344168

The new version fixes the bug.

[marcobra (Marco Braida) (marcobra)]

With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.

Thanks

[Pietro Battiston (toobaz)]

I also confirm the bug is reproduced under jaunty with version 0.3.4-1.

sudo /etc/init.d/apt-cacher-ng start
 * Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could be create/prepared. Check the network, check or unset the BindAddress directive.
                                                                         [fail]

[Pietro Battiston (toobaz)]

(to use apt-cacher-ng, I have to manually identify and kill the apt-cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)

[Fabián Rodríguez (magicfab)]

Workaround:

1) Find the apt-cacher-ng process:
ps aux | grep apt

Example output:
124 3035 0.0 0.1 175928 3616 ? Ssl 18:02 0:01 /usr/sbin/apt-cacher-ng -c /etc/apt-cacher-ng pidfile=/var/run/apt-cacher-ng/pid SocketPath=/var/run/apt-cacher-ng/socket foreground=0
magicfab 12958 0.0 0.0 7528 916 pts/2 S+ 19:09 0:00 grep apt

2) Kill it:
magicfab@tiara:~$ sudo kill -9 3035
[sudo] password for magicfab:

3) Restart it:
magicfab@tiara:~$ sudo service apt-cacher-ng start
 * Starting apt-cacher-ng apt-cacher-ng [ OK ]

[João Pinto (joaopinto)]

Closing the bug because it was fixed in Karmic.