starting mpd: "unable to bind port 6600" & core dumped (post-installation script returned exit status 134)

Bug #357385 reported by fabtagon
2
Affects Status Importance Assigned to Milestone
mpd (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: mpd

When starting mpd (i.e. while installing the package) mpd claims port 6600 to be used and dumps core.

root@hermod:~# /usr/bin/mpd --verbose
binding to address for localhost
unable to bind port 6600: Address already in use
maybe MPD is still running?
Aborted (core dumped)

But obviously that port is free:

root@hermod:~# telnet localhost 6600
Trying ::1...
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@hermod:~#

Package version is mpd 0.14.2-3ubuntu1.
Encountered on xubuntu-9.04 development branch (jaunty)
uname: 2.6.28-11-generic #39-Ubuntu SMP i686

This should be another issue than #273721 as the messages are different and the solution proposed there does not work.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: underprocess post-installation script gav felkod 134
Package: mpd 0.14.2-3ubuntu1
SourcePackage: mpd
Title: package mpd 0.14.2-3ubuntu1 failed to install/upgrade: underprocess post-installation script gav felkod 134
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
fabtagon (fabtagon) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug. Can you look at bug 332332 and try the suggestion there to edit /etc/mpd.conf and change the bind_to_address from "localhost" to "127.0.0.1", please. If that works, is this a duplicate of that bug?

Thanks again for helping.

Changed in mpd (Ubuntu):
status: New → Incomplete
Revision history for this message
fabtagon (fabtagon) wrote : Re: [Bug 357385] Re: starting mpd: "unable to bind port 6600" & core dumped (post-installation script returned exit status 134)

Hi Charlie,

> Thanks for reporting this bug. Can you look at bug 332332 and try the
> suggestion there to edit /etc/mpd.conf and change the bind_to_address
> from "localhost" to "127.0.0.1", please. If that works, is this a
> duplicate of that bug?

Yes, it is.

I don't know how I have missed that bug when searching for the problem
in the bug database; sorry for posting a duplicate! Thanks for your
help!

best regards & wish you a hardworking Easter bunny ;-)
  Fabian

Revision history for this message
fabtagon (fabtagon) wrote :

I don't know how I have missed that bug report when searching for the problem in the bug database, but it really exactly looks like #332332 (and can be worked around the same way). Sorry for posting a duplicate; I've marked it accordingly.

Thanks for your help & a hardworking Easter bunny for you ;-)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.