< ^ txt
Tue Mar 3 10:18:49 EST 2015
Slept OK. Surprise snow storm made for a extremely slow commute.
Goals:
Work:
- Order remaining routers for remote sites
Done.
- Get licensing squared away
Done, I guess.
- Install heatsinks in new servers
Done.
- Make something happen with the maintenance phone system
Done, although it may not be fully resolved until next week.
Home:
- Work on S&W Complete re-typeset
Done.
- Shop at drug store
Done.
Questions:
- Why doesn't mpd see my music library?
The FAQ says (http://mpd.wikia.com/wiki/Music_Player_Daemon_Database_Troubleshooting) says it's usually a permissions issue. That may we true. The daemon runs as user mpd.
$ sudo groupadd music
$ sudo usermod -G music mpd
$ sudo usermod -G music paulgorman
$ sudo chgrp -R music ~/music
Nope. That didn't fix it.
The recommendation to debug it is to run `mpd --verbose --no-daemon --stdout > mpd_trouble.out`, but:
$ mpd --verbose --no-daemon --stdout > mpd_trouble.out
config_file: loading file /home/paulgorman/.mpdconf
socket: Failed to bind to '[::]:6600': Address already in use
$ sudo lsof -i :6600
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 58u IPv6 14153 0t0 TCP *:6600 (LISTEN)
$ systemctl status mpd
● mpd.service - Music Player Daemon
Loaded: loaded (/lib/systemd/system/mpd.service; disabled)
Active: inactive (dead) since Tue 2015-03-03 15:27:21 EST; 10min ago
Main PID: 12719 (code=exited, status=0/SUCCESS)
--- 633 --- falstaff ~ $ ps aux | grep mpd
paulgor+ 13367 0.0 0.0 12720 2112 pts/18 S+ 15:37 0:00 grep mpd
systemd won't let go of the socket. I tried `sudo systemctl disable mpd.service; sudo systemctl disable mpd.socket` but it's still hanging onto the socket.
Ah:
$ sudo systemctl stop mpd.socket
$ systemctl status mpd.socket
● mpd.socket
Loaded: loaded (/lib/systemd/system/mpd.socket; disabled)
Active: inactive (dead)
Listen: /run/mpd/socket (Stream)
[::]:6600 (Stream)
I was then able to do `mpd --verbose --no-daemon --stdout > mpd_trouble.out`.
It worked fine. `mpc ls` lists my music, and I can play tracks.
Is the problem that systemd is not reading ~/.mpdconf?
https://wiki.archlinux.org/index.php/Music_Player_Daemon#Autostart_with_systemd
"The package mpd provides user service file in /usr/lib/systemd/user/mpd.service. The configuration file is expected to exist either in ~/.mpdconf or ~/.config/mpd/mpd.conf"
On Debian, the unit file is /lib/systemd/system/mpd.service. It contains this line:
EnvironmentFile=/etc/default/mpd
...and /etc/defaults/mpd has no uncommented lines.
https://wiki.archlinux.org/index.php/Systemd/User
"systemd offers users the ability to manage services under the user's control with a per-user systemd instance, enabling users to start, stop, enable, and disable their own units. This is convenient for daemons and other services that are commonly run for a single user, such as mpd, or to perform automated tasks like fetching mail."
$ ps aux | grep 'systemd --user'
lightdm 1248 0.0 0.0 35768 3956 ? Ss Feb17 0:00 /lib/systemd/systemd --user
paulgor+ 1654 0.0 0.0 35768 3956 ? Ss Feb17 0:00 /lib/systemd/systemd --user
paulgor+ 13845 0.0 0.0 12724 2108 pts/22 S+ 16:31 0:00 grep systemd --user
However, it looks like the systemd --user stuff is even more in flux at the moment than the rest of systemd, and I don't see much advantage of using it to run mpd than just running it myself (from my ~/.session or whatever).
So, I'll leave mpd.service and mpd.socket disabled through systemctl.
< ^ txt