mpd won't properly install untill localhost changed to 127.0.0.1 in /etc/mpd.conf

[Tiva]

I am using Jaunty AMD64 Xubuntu fully updated.

this bug happened in the mpd 0.13 -> 0.14 update.

attempting a normal apt-get install of mpd on Jaunty leads to the following:

$ sudo apt-get install mpd
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
icecast2
The following NEW packages will be installed:
mpd
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B/180kB of archives.
After this operation, 545kB of additional disk space will be used.
Selecting previously deselected package mpd.
(Reading database ... 199197 files and directories currently installed.)
Unpacking mpd (from .../mpd_0.14.2-2ubuntu1_amd64.deb) ...
Processing triggers for man-db ...
Setting up mpd (0.14.2-2ubuntu1) ...
* Starting Music Player Daemon mpd * creating /var/lib/mpd/tag_cache...
unable to bind port 6600: Address already in use
maybe MPD is still running?
Trace/breakpoint trap (core dumped)
[fail]
invoke-rc.d: initscript mpd, action "start" failed.
dpkg: error processing mpd (--configure):
subprocess post-installation script returned error exit status 133
Errors were encountered while processing:
mpd
E: Sub-process /usr/bin/dpkg returned an error code (1)

The fix is to edit /etc/mpd.conf and change the bind_to_address from "localhost" to "127.0.0.1" - thanks to BwackNinja for the info

after the change a:
sudo dpkg --configure -a
fixes the installation and allows MPD to properly bind to the port.

[Thomas Coppi (tcoppi)]

Is there an entry in /etc/hosts for localhost to point to 127.0.0.1 ?

[Tiva (ugkbunb)]

yes

[waldschrat (unumsaxum)]

I can confirm that bug.
Same version, same bug, same fix.

But there is one strange thing:
when using the original mpd.conf with
bind_to_address set to "localhost",
even thought mpd does not install properly, it starts up well on system startup. Only when restarting it by "/etc/init.d/mpd restart" (this is exactly what dpkg does) the bug occurs.

regards,
H. Stephan

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Alessio Treglia (quadrispro)]

 status inprogress
 assignee quadrispro

--
Alessio Treglia <email address hidden>
Ubuntu MOTU Developer | Homepage: http://www.alessiotreglia.com
0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0

[Alessio Treglia (quadrispro)]

The patch should solve this and the package has been built fine in my PPA, please use it for testing.

[Alessio Treglia (quadrispro)]

PPA: http://ppa.launchpad.net/quadrispro/testing/ubuntu

[Iulian Udrea (iulian)]

I would like to see some testing using that patch before approving it.

[Alessio Treglia (quadrispro)]

I'm using a chroot for tests and ALSA doesn't work correctly, so at the moment I can't do any useful test.

[StefanPotyra (sistpoty)]

hm... why is 127.0.0.1 working, but not localhost?

Thanks for testing, but I don't think a chroot can produce any reliable result for this bug. Can you repeat your tests in a non-chroot environment?

P.S.: I just took a glimpse at -3ubuntu1, please make sure to use a real address as changelog entry in the future (current one: Ubuntu Merge-o-Matic <email address hidden>). Thanks.

[Andy Hauser (andy-ubuntu-bugzilla)]

The PPA fixes the issue for me in a fresh jaunty installation.

[Alessio Treglia (quadrispro)]

Stephan, really I don't why it doesn't work with localhost, probably we should forward this to upstream || debian.

About the last upload, I'm sorry, it was my little mistake :)

[fabtagon (fabtagon)]

I can't confirm that bug on Debian Testing (mpd 0.14.2-3).

[StefanPotyra (sistpoty)]

I also don't have the slightest clue why 127.0.0.1 would work but localhost not, and I fear that this fix is at best a workaround.

However at this stage, if the workaround is working (as testing seems to indicate), let's go for it, and try to address the real problem in karmic.

Feel free to upload, but please also watch out for other upgrade problem reports, in case this was not a good workaround, thanks.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mpd - 0.14.2-3ubuntu2

---------------
mpd (0.14.2-3ubuntu2) jaunty; urgency=low

  * Change bind_to_address from localhost to 127.0.0.1 (LP: #332332).

 -- Alessio Treglia <email address hidden> Sun, 12 Apr 2009 11:41:14 +0200

[Max Kellermann (max-duempel)]

That is not a fix, because this breaks IPv6 support.

[Alessio Treglia (quadrispro)]

I've just uploaded the merge with latest debian version to my testing PPA, please test it.

deb http://ppa.launchpad.net/quadrispro/testing/ubuntu karmic main

[Steve Langasek (vorlon)]

Has this bug really been in progress since June? Has no one tested the PPA?

[Kiri (kiri)]

I was going to test this package but it is not in the PPA.

[Alessio Treglia (quadrispro)]

I'm updating the merge, uploading to my PPA.

[Alessio Treglia (quadrispro)]

It's ready, please test.

[Alessio Treglia (quadrispro)]

Looks working fine, attaching install log.

[Scott Kitterman (kitterman)]

Up until Universe final freeze, this doesn't need an FFe. Unsubscribing motu-release.

[Alessio Treglia (quadrispro)]

Ok, I'm going ahead.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mpd - 0.15.4-1ubuntu1

---------------
mpd (0.15.4-1ubuntu1) karmic; urgency=low

  * Merge from debian unstable, Ubuntu remaining changes:
    - debian/control:
      + Don't build-depends on libmikmod2-dev (Debian bug #510675).
      + Move avahi-daemon from Suggests field to Recommends field.
    - debian/mpd.init.d:
      + Read mpd user from mpd.conf.
  * Also fixes LP: #332332.

mpd (0.15.4-1) unstable; urgency=low

  * New upstream release (Closes: #550757)

mpd (0.15.3-1.1) unstable; urgency=low

  * Non-maintainer upload.
  * Apply patch taken from upstream to workaround tremor headers
    (Closes: #547525)

mpd (0.15.3-1) unstable; urgency=low

  * New upstream release

mpd (0.15.2-1) unstable; urgency=low

  * New upstream release

mpd (0.15.1-1) unstable; urgency=low

  * New upstream release
    - Fix crash on discarding db with bad charset (Closes: #535076)
  * Re-enable ffmpeg (Closes: #534726)

mpd (0.15-2) unstable; urgency=low

  * Enable SQLite, libcue, sidplay, and libmms.
  * Enable state file by default in mpd.conf.

mpd (0.15-1) unstable; urgency=low

  * New upstream release

mpd (0.15~beta2-1) experimental; urgency=low

  * New upstream release
  * Nicer message when systemwide daemon is disabled (Closes: #521701,
    #529524)
  * Update mpd.conf from upstream
    - Configure an ALSA output by default
  * Fix section of mpd-debug

mpd (0.15~beta1-1) experimental; urgency=low

  * New upstream beta release

mpd (0.15~alpha1-1) experimental; urgency=low

  * New upstream alpha release

 -- Alessio Treglia <email address hidden> Fri, 23 Oct 2009 12:38:20 +0200

[Jean-Baptiste Lallement (jibel)]

Alessio, according to bug 500001 and after checking the latest source package (0.15.4-1ubuntu1) this doesn't look like being fixed.
In mpd.conf there's still 'bind_to_address "localhost"'
Could you please take a look at this ?

Thanks.

[Alessio Treglia (quadrispro)]

Forwarded to Debian.

[Fabián Rodríguez (magicfab)]

The comments in the config file indicate "any" should be the default value. MPD started fine once I set it to "any".

# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
#
# For network
bind_to_address "any"

So, I guess this should be reverted back to "any".

I was using 10.04 LTS in my tests.

[Mark Nevill (nevillm)]

This Bug is *still* present in Ubuntu Lucid (mpd 0.15.4-1ubuntu3).

@Fabián: The recommendation is problematic, as it will allow remote users to control your mpd. Do *NOT* set your bind_to_address to "any" unless you know what you are doing.

[Florian Schlichting (fschlich)]

The problem is really in /etc/hosts, but mpd 0.15 released with a workaround ("bind failure on secondary address is non-fatal")