SOLVED - mpd client can't connect (timeout)

VastOne · 2011-09-30 00:48:09

machinebacon wrote:

OMG, maybe that's the point: /etc/mpd.conf vs. /.mpdconf

All I am trying to do is point out what is working...

machinebacon · 2011-09-30 01:04:35

^ Oh I didn't mean your setup being problematic, VastOne, but pointing at el_koraco's problem. Sorry that I didn't quote him I have read through the thread and didn't find a 100% statement if /etc/mpd.conf and/or .mpdconf is used, and I remember there was a problem like ths a few weeks/months ago with a user editing the wrong file.

VastOne · 2011-09-30 01:20:16

^ I knew as much machinebacon...

I had been ranting on and on about mine and wanted to qualify the reason why I was doing it...

77 messages to read... I know

No offense taken whatsoever.. I knew your intent...

machinebacon · 2011-09-30 01:32:43

^ but yours works, doesn't it?

VastOne · 2011-09-30 01:43:15

machinebacon wrote:

^ but yours works, doesn't it?

Like a pig in a blanket! Perfectly...

I have always believed that when you get to what is wrong and hit the road block, the best/obvious course is to then get to what is right...

Last edited by VastOne (2011-09-30 01:45:23)

el_koraco · 2011-09-30 08:11:03

machinebacon wrote:

Timeout error could be related to localhost in the host file. God knows what mpd thinks/does..... (later more about this)
bind_to_address        "localhost"
what if this is changed to 127.0.0.1

If it's changed to 127..., it fails to start. If I put :: in, it starts, but the clients get the same error. WIth regard to IPv6, I think it's enabled globally, at least I didnt't disable it manually.

xaos52 · 2011-09-30 19:30:07

@VastOne:

Binding to IPV6 before IPV4
If on startup, you see this message:
listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
MPD is attempting to bind to the ipv6 interface before binding to ipv4. If you want to use your ipv4 interface, hardcode it in mpd.conf, like so:
bind_to_address "127.0.0.1"

hardcode it in your user config file if you start mpd as a user, not as a system daemon.

Edit: extracted from archlinux wiki: https://wiki.archlinux.org/index.php/Mu … yer_Daemon

Last edited by xaos52 (2011-09-30 19:32:17)

VastOne · 2011-09-30 19:41:13

xaos52 wrote:

@VastOne:
Binding to IPV6 before IPV4
If on startup, you see this message:
listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
MPD is attempting to bind to the ipv6 interface before binding to ipv4. If you want to use your ipv4 interface, hardcode it in mpd.conf, like so:
bind_to_address "127.0.0.1"
hardcode it in your user config file if you start mpd as a user, not as a system daemon.
Edit: extracted from archlinux wiki: https://wiki.archlinux.org/index.php/Mu … yer_Daemon

Thanks for that xaos52.. I did make the change and no more errors..

xaos52 · 2011-10-01 10:20:52

@VastOne:
To get rid of the remaining error(or warning), remove the 'user' entry from your mpd config file, since you already run mpd as your user.
Found that here https://bbs.archlinux.org/viewtopic.php?id=118255
I had that too, and it is gone after the modification.
hth

xaos52 · 2011-10-01 10:27:30

@el_koraco
I installed mpd/mpc on a fresh copy of #!, and up until now I have not been able to create a situation where the client can NOT connect to the daemon. Tried all sorts of combinations of config options. Same after dist-upgrade. Same after including backport sources.

Edit: may I suggest adding

log_level            "verbose"

to your $HOME/.mpdconf file, if you have not done so already.

Last edited by xaos52 (2011-10-01 10:33:25)

VastOne · 2011-10-01 14:02:00

xaos52 wrote:

@VastOne:
To get rid of the remaining error(or warning), remove the 'user' entry from your mpd config file, since you already run mpd as your user.
Found that here https://bbs.archlinux.org/viewtopic.php?id=118255
I had that too, and it is gone after the modification.
hth

Thanks xaos52

I found that same thread and made those changes earlier.. Should have posted it like you did..

hhh · 2011-10-04 02:21:27

@el_koraco, just in case you didn't think of it, I had all the same symptoms as you till I did this...
http://crunchbanglinux.org/forums/post/150347/#p150347

Hoping that will help. *crosses fingers*

el_koraco · 2011-10-04 09:35:56

hhh wrote:

@el_koraco, just in case you didn't think of it, I had all the same symptoms as you till I did this...
http://crunchbanglinux.org/forums/post/150347/#p150347
Hoping that will help. *crosses fingers*

YES!!!! YOU'RE A FREAKING GENIUS!!!!
Makes perfect sense, I didn't even think to mention my connectivity type. Network manager, wicd and others handle this automatically, that's why noone could reproduce the problem.

Edit @xaos - I missed your last message, sorry. Thanks for your help again, we did cover a lot of ground with config options, which won't be in vain.

Last edited by el_koraco (2011-10-04 11:36:07)

xaos52 · 2011-10-04 12:18:58

No problem
Glad it is solved.
I did not think of that, no.
And Yes, hhh is a GENIUS

VastOne · 2011-10-04 14:25:47

xaos52 wrote:

No problem
Glad it is solved.
I did not think of that, no.
And Yes, hhh is a GENIUS

Well done with all your work on this xaos52!

hhh is awesome... with a much bigger head now too!

rhowaldt · 2011-10-04 16:20:57

ah, 4 pages of stuff and solved in the end. been following this thread like a thriller :)

mark it solved!

el_koraco · 2011-10-04 17:10:42

rhowaldt wrote:

mark it solved!

Yup, forgot about it. I've changed the title as well, so someone can find it via keywords if the need ever arises.

hhh · 2011-10-04 17:35:35

el_koraco wrote:

YES!!!! YOU'RE A FREAKING GENIUS!!!!

Supergenius, please.

But seriously, I'm so glad that worked for you as well. After fighting with mpd and uninstalling/reinstalling/logging out/logging in/rebooting for three days with no luck, finally hearing sound made me wet my pants a little.

Cheers!

el_koraco · 2011-10-04 17:40:38

hhh wrote:

But seriously, I'm so glad that worked for you as well. After fighting with mpd and uninstalling/reinstalling/logging out/logging in/rebooting for three days with no luck, finally hearing sound made me wet my pants a little.

I'd already gone and started tweaking the MOC colors, and suddenly, I'm in ncmpcpp, lol.

hhh · 2011-10-04 21:58:39

The cow knows.

CrunchBang Linux

SEARCH

#76 2011-09-30 00:48:09

Re: SOLVED - mpd client can't connect (timeout)

#77 2011-09-30 01:04:35

Re: SOLVED - mpd client can't connect (timeout)

#78 2011-09-30 01:20:16

Re: SOLVED - mpd client can't connect (timeout)

#79 2011-09-30 01:32:43

Re: SOLVED - mpd client can't connect (timeout)

#80 2011-09-30 01:43:15

Re: SOLVED - mpd client can't connect (timeout)

#81 2011-09-30 08:11:03

Re: SOLVED - mpd client can't connect (timeout)

#82 2011-09-30 19:30:07

Re: SOLVED - mpd client can't connect (timeout)

#83 2011-09-30 19:41:13

Re: SOLVED - mpd client can't connect (timeout)

#84 2011-10-01 10:20:52

Re: SOLVED - mpd client can't connect (timeout)

#85 2011-10-01 10:27:30

Re: SOLVED - mpd client can't connect (timeout)

#86 2011-10-01 14:02:00

Re: SOLVED - mpd client can't connect (timeout)

#87 2011-10-04 02:21:27

Re: SOLVED - mpd client can't connect (timeout)

#88 2011-10-04 09:35:56

Re: SOLVED - mpd client can't connect (timeout)

#89 2011-10-04 12:18:58

Re: SOLVED - mpd client can't connect (timeout)

#90 2011-10-04 14:25:47

Re: SOLVED - mpd client can't connect (timeout)

#91 2011-10-04 16:20:57

Re: SOLVED - mpd client can't connect (timeout)

#92 2011-10-04 17:10:42

Re: SOLVED - mpd client can't connect (timeout)

#93 2011-10-04 17:35:35

Re: SOLVED - mpd client can't connect (timeout)

#94 2011-10-04 17:40:38

Re: SOLVED - mpd client can't connect (timeout)

#95 2011-10-04 21:58:39

Re: SOLVED - mpd client can't connect (timeout)

Board footer