MPD fails to start upon boot

arthd · 2011-01-26 15:38:55

When I boot up and the mpd daemon is supposed to start, it returns an error

/etc/rc.d/mpd       line 6     1449 aborted
/usr/bin/mpd    /etc/mpd.conf &> /dev/null [FAIL]

However, when I start it after the computer has booted up, it works without a problem. It's only during bootup.

ilusi0n · 2011-01-26 16:22:18

It says there is a error on line 6 of the daemon. Did you change anything there? Or you checked what that line have?

Last edited by ilusi0n (2011-01-26 16:22:44)

Inxsible · 2011-01-26 16:23:44

you need to start network before you start mpd in the DAEMONS array. Are you doing that?

ewaller · 2011-01-26 16:24:02

What is your DAEMONS array in /etc/rc.conf ?? It might require that alsa be started first. It might also want the network to have been started, but I am not sure.

edit: Arrg.... beat by 42 seconds. I hate it when that happens.

Last edited by ewaller (2011-01-26 16:25:46)

Inxsible · 2011-01-26 16:27:35

ewaller wrote:

edit: Arrg.... beat by 42 seconds. I hate it when that happens.

Do your math again. Its 18 seconds. Just so you will hate it even more

arthd · 2011-01-26 16:28:21

Nope, didn't change anything there, and it's odd as it does start when I manually /etc/rc.d/mpd start

arthd · 2011-01-26 16:41:30

Even if it starts after network it won't start, and when I disable network and then reboot and manually /etc/rc.d/mpd start it works as well.

Inxsible · 2011-01-26 16:52:02

Can you post your DAEMONS array?

arthd · 2011-01-26 16:58:54

DAEMONS=(syslog-ng network alsa mpd dbus netfs crond hal)

Inxsible · 2011-01-26 17:01:53

and your hostname is set up correctly in the rc.conf, /etc/hosts and mpd.conf?

arthd · 2011-01-26 17:05:47

The hostname is set up correctly in rc.conf and hosts, but I didn't set it in mpd.conf, as specifying audio output doesn't seem to be necessary to play back audio.

Inxsible · 2011-01-26 17:08:15

now you have me beat. Off the top of my head, try starting dbus and hal before mpd. I honestly do not think it would matter since mpd, AFAIK, is not dependent on either of them, but its worth a try.
Make it like this

DAEMONS=(syslog-ng network dbus hal alsa mpd netfs crond)

I think dbus does start hal on its own, so you might not need to start it explicitly. Or at least that was the case a while back.

arthd · 2011-01-26 17:12:25

I gave it a try, but sadly it didn't help.

ewaller · 2011-01-26 17:12:53

Inxsible wrote:

Do your math again. Its 18 seconds. Just so you will hate it even more

Time for another cup of coffee for me :-/

Back on topic. Any chance that /etc/conf.d/mpd is set to use remote files that will require netfs? (i.e. is your library on this machine, or elsewhere on the network?)

arthd · 2011-01-26 17:15:24

It's all on this machine, so starting network before mpd probably shouldn't be necessary either.

Inxsible · 2011-01-26 17:17:54

arthd wrote:

It's all on this machine, so starting network before mpd probably shouldn't be necessary either.

Nope, you are wrong on that one. mpd is a client server architecture. you would need a client like ncmpcc or some gui mpd client like sonata to be able to connect to the mpd server. Therefore the network definitely needs to be up and running before mpd can.

ewaller · 2011-01-26 17:19:13

Were this me, I would consider temporarily changing /etc/rc.d/mpd to not send the output of the daemon to /dev/null (around line 10 IIRC) and instead send it someplace where you can see it (a console, a file someplace, whatever)

ilusi0n · 2011-01-26 17:23:10

Inxsible wrote:

Therefore the network definitely needs to be up and running before mpd can.

Really? I have almost sure that mpd connects before I even get network access. Because before I login I don't have internet but mpd daemon have already started. And my music is on the computer. I can be wrong though...

Last edited by ilusi0n (2011-01-26 17:24:33)

Inxsible · 2011-01-26 17:26:45

by network i don't mean the internet, but the network driver which controls your connection needs to be up. The mpd client will talk to the mpd server using "localhost" if they are on the same machine. So internet is not needed but the lan needs to be up.

easy to test. I am not on my Arch box so I can't test this.

# /etc/rc.d/mpd stop
# /etc/rc.d/network stop
# /etc/rc.d/mpd start

See what it tells you.

arthd · 2011-01-26 17:45:02

ewaller wrote:

Were this me, I would consider temporarily changing /etc/rc.d/mpd to not send the output of the daemon to /dev/null (around line 10 IIRC) and instead send it someplace where you can see it (a console, a file someplace, whatever)

Good idea, I should've done that right away.

Bootup:

listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
output: No "audio_output" defined in config file
output: Attempt to detect audio output device
output: Attempting to detect a alsa audio device
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4154:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4633:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM default
alsa: Error opening default ALSA device: No such file or directory
output: Attempting to detect a oss audio device
oss: Error opening OSS device "/dev/dsp": Permission denied
oss: Error opening OSS device "/dev/sound/dsp": No such file or directory
output: Attempting to detect a pulse audio device
Assertion 'm' failed at pulse/thread-mainloop.c:172, function pa_threaded_mainloop_lock(). Aborting.

Start after boot

listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
output: No "audio_output" defined in config file
output: Attempt to detect audio output device
output: Attempting to detect a alsa audio device
output: Successfully detected a alsa audio device

Seems like it can't detect alsa on boot even though it starts after alsa.

Inxsible · 2011-01-26 17:50:13

output: No "audio_output" defined in config file

This tells me that defining an audio_output = ALSA in the config file would circumvent the problem.

However, I still don understand why it can't detect alsa during bootup. you don't have it backgrounded either. Strange.

arthd · 2011-01-26 17:55:41

Yep, uncommented the ALSA output section and it works now.
Should I tag this as solved or not? It's more of a workaround than a solution.

ilusi0n · 2011-01-26 18:01:24

Not sure if I'm wrong but commenting the ALSA output will not mean that you have no sound?

edit: nevermind, I though you had commented it and not uncomment...

Last edited by ilusi0n (2011-01-26 18:03:32)

Inxsible · 2011-01-26 18:02:45

ilusi0n wrote:

Not sure if I'm wrong but commenting the ALSA output will not mean that you have no sound?

He means that he uncommented the ALSA section in mpd.conf. So alsa was working for all other apps.

He had mpd auto-detect the sound architecture (which for some reason didn't work during boot), but now is defining it in the mpd.conf file and now things work.

ilusi0n · 2011-01-26 18:06:55

Inxsible wrote:

ilusi0n wrote:
Not sure if I'm wrong but commenting the ALSA output will not mean that you have no sound?
He means that he uncommented the ALSA section in mpd.conf. So alsa was working for all other apps.
He had mpd auto-detect the sound architecture (which for some reason didn't work during boot), but now is defining it in the mpd.conf file and now things work.

Damn, you answer before I could edit my post. Yeah I misunderstood what he said. Yeah I never though of that. I have alsa uncommented in the mpd.conf as well. So is not a workaround but I think is the way things must be done. But will try and comment to see if I have problems as well. But well glad it work

Arch Linux

#1 2011-01-26 15:38:55

MPD fails to start upon boot

#2 2011-01-26 16:22:18

Re: MPD fails to start upon boot

#3 2011-01-26 16:23:44

Re: MPD fails to start upon boot

#4 2011-01-26 16:24:02

Re: MPD fails to start upon boot

#5 2011-01-26 16:27:35

Re: MPD fails to start upon boot

#6 2011-01-26 16:28:21

Re: MPD fails to start upon boot

#7 2011-01-26 16:41:30

Re: MPD fails to start upon boot

#8 2011-01-26 16:52:02

Re: MPD fails to start upon boot

#9 2011-01-26 16:58:54

Re: MPD fails to start upon boot

#10 2011-01-26 17:01:53

Re: MPD fails to start upon boot

#11 2011-01-26 17:05:47

Re: MPD fails to start upon boot

#12 2011-01-26 17:08:15

Re: MPD fails to start upon boot

#13 2011-01-26 17:12:25

Re: MPD fails to start upon boot

#14 2011-01-26 17:12:53

Re: MPD fails to start upon boot

#15 2011-01-26 17:15:24

Re: MPD fails to start upon boot

#16 2011-01-26 17:17:54

Re: MPD fails to start upon boot

#17 2011-01-26 17:19:13

Re: MPD fails to start upon boot

#18 2011-01-26 17:23:10

Re: MPD fails to start upon boot

#19 2011-01-26 17:26:45

Re: MPD fails to start upon boot

#20 2011-01-26 17:45:02

Re: MPD fails to start upon boot

#21 2011-01-26 17:50:13

Re: MPD fails to start upon boot

#22 2011-01-26 17:55:41

Re: MPD fails to start upon boot

#23 2011-01-26 18:01:24

Re: MPD fails to start upon boot

#24 2011-01-26 18:02:45

Re: MPD fails to start upon boot

#25 2011-01-26 18:06:55

Re: MPD fails to start upon boot

Board footer