What configuration was in use to get that exact error message. If
dnsmasq is binding the wildcard address (0.0.0.0), I'd expect to see a
message  like

dnsmasq: failed to create listening socket for port 53

Whilst if dnsmasq is configured to bind the hosts addresses, I'd expect
to see something like

dnsmasq: failed to create listening socket for 192.168.151.1

So I'm confused how you're getting the message with an IP address, but
for the 0.0.0.0 wildcard address.

Cheers,

Simon


On 02/10/15 17:24, Karl-Philipp Richter wrote:
> Public bug reported:
> 
> The error message "dnsmasq: failed to create listening socket for
> 0.0.0.0: Address already in use" doesn't explain which port number it
> refers to. In case it's an OS message it needs to be catched and
> enhanced with necessary information (in order to get any use of the
> message).
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: dnsmasq 2.72-3ubuntu0.1
> ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
> Uname: Linux 3.19.0-30-generic x86_64
> NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx
> ApportVersion: 2.17.2-0ubuntu1.5
> Architecture: amd64
> Date: Fri Oct  2 18:22:22 2015
> InstallationDate: Installed on 2015-04-20 (165 days ago)
> InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)a 
> PackageArchitecture: all
> ProcEnviron:
>  TERM=screen
>  PATH=(custom, no user)dig @172.17.42.1
> d8607ce495db.node.aws-us-east-1.consul
>  XDG_RUNTIME_DIR=<set>
>  LANG=de_DE.UTF-8
>  SHELL=/bin/bash
> SourcePackage: dnsmasq
> UpgradeStatus: Upgraded to vivid on 2015-04-24 (160 days ago)
> mtime.conffile..etc.dnsmasq.conf: 2015-06-13T18:46:46.597888
> 
> ** Affects: dnsmasq (Ubuntu)dig @172.17.42.1
> d8607ce495db.node.aws-us-east-1.consul
>      Importance: Undecided
>          Status: New
> 
> 
> ** Tags: amd64 apport-bug vivid
> 
> ** Description changed:
> 
> - error message "dnsmasq: failed to create listening socket for 0.0.0.0:
> - Address already in use" doesn't explain which port number it refers to
> + The error message "dnsmasq: failed to create listening socket for
> + 0.0.0.0: Address already in use" doesn't explain which port number it
> + refers to. In case it's an OS message it needs to be catched and
> + enhanced with necessary information (in order to get any use of the
> + message).
>   
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: dnsmasq 2.72-3ubuntu0.1
>   ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
>   Uname: Linux 3.19.0-30-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx
>   ApportVersion: 2.17.2-0ubuntu1.5
>   Architecture: amd64
>   Date: Fri Oct  2 18:22:22 2015
>   InstallationDate: Installed on 2015-04-20 (165 days ago)
>   InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)
>   PackageArchitecture: all
>   ProcEnviron:
> -  TERM=screendig @172.17.42.1
> d8607ce495db.node.aws-us-east-1.consul
> -  PATH=(custom, no user)
> -  XDG_RUNTIME_DIR=<set>
> -  LANG=de_DE.UTF-8
> -  SHELL=/bin/bash
> +  TERM=screen
> +  PATH=(custom, no user)
> +  XDG_RUNTIME_DIR=<set>
> +  LANG=de_DE.UTF-8
> +  SHELL=/bin/bash
>   SourcePackage: dnsmasq
>   UpgradeStatus: Upgraded to vivid on 2015-04-24 (160 days ago)
>   mtime.conffile..etc.dnsmasq.conf: 2015-06-13T18:46:46.597888
>