You are not logged in.
For some reason, MPD is unable to start as a daemon listed in rc.conf. I have tried running it as a background also and no go. MPD goes after ALSA, so I don't know what else is missing.
Also, I cannot start mpd as root after logging in immediately after my system boots up. It just tells me it fails.
However, I can start MPD after I log-in as a normal user and su into root, then manually typing /etc/rc.d/mpd start.
Could it be that it is unable to find my music database during its attempt to start as a daemon in rc.conf? (because my music directory is in an NTFS partition, which is not listed in fstab because it is automatically mounted by hal)
Could it be that I set "user" in /etc/mpd.conf as "mpd" that it is unable to start it as root?
What could be the culprit?
Last edited by orv (2007-12-24 19:22:49)
Offline
I think it is problem with config files. Double check all of them. It looks like your user config is ok but root config or global config is bad.
Offline
Have you ran /etc/rc.d/mpd create-db?
Offline
Yup. MPD works and plays my music. It just wont start up as a daemon, but I know why now.
The place where my music is located (/dev/sdb2) is an NTFS partition which isn't mounted by the time I get to the login prompt. This is because it is automounted AFTER i log-in a user account in which HAL automounts that drive.
Adding an entry in FSTAB and not relying on automount by HAL solves the problem because now when I start it as a daemon, it can actually find my music library.
Offline
I'm bumping this thread because I was having a similar problem. My config files where fine and MPD would not start as a daemon. The "solution" was strange. Running '/etc/rc.d/mpd start' failed for both root and user. Then I tried simply 'mpd' and got an error message about MPD already running. After that everything worked properly.
Offline
There is a section in the config file that lets mpd change UID if it's started as root. If the user it tries to become doesn't exist, it will fail. Make sure that user (if you use that feature) exists. I think by default it tries to become user 'mpd'.
Offline
I don't know about mpd, but for some other daemons that start as root and then drop privileges to another user you also need to have the 'capability' module loaded (rc.conf).
1000
Offline
Configured mpd as described in the wiki and everything runs fine here. I have set my UID to mpd and it starts on boot without problems. There is no need to load a module or anything. The 'mpd' user will automatically create after the installation of the package, so it exists on the system, if you don't delete it.
Offline