[SOLVED] Cannot update mpd database after upgrade

d_fajardo · 2017-08-25 19:17:46

I have searched the forums and the internet but cannot get a satisfactory answer. My mpd, nmcpcpp, Cantata were all working fine, very well in fact. After mpd upgrade however, I first noticed I cannot update database in Cantata. Second, nmcpcpp shows old database, and if I try to update it, I get 'Connection refused' error. Then when I try to update the mpd database via mpc update --wait, 'I get Connection closed by server.'
Any help? What has happened? I haven't change any settings in my configuration files. Mpd works - I can play music. It just refuses to update database.

Last edited by d_fajardo (2017-09-05 10:26:07)

jasonwryan · 2017-08-25 19:23:19

Please provide some details of your setup: configs, errors, journal, etc: https://bbs.archlinux.org/viewtopic.php?id=57855

Moving to NC...

d_fajardo · 2017-08-25 19:40:30

This is my mpd.conf

 An example configuration file for MPD.
# Read the user manual for documentation: http://www.musicpd.org/doc/user/


# Files and directories #######################################################
#
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This 
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
#
music_directory		"/home/DataPool/Music"
#
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use 
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
#
playlist_directory		"~/.config/mpd/playlists"
#
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the 
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
#
db_file			"~/.config/mpd/database"
# 
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
#
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
#
log_file			"~/.config/mpd/log"
#
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
#
pid_file			"~/.config/mpd/pid"
#
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server 
# state will be reset on server start up.
#
state_file			"~/.config/mpd/state"
#
# The location of the sticker database.  This is a database which
# manages dynamic information attached to songs.
#
sticker_file			"~/.config/mpd/sticker.sql"
#
###############################################################################


# General music daemon options ################################################
#
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
#
user				"dipswitch"
#
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#
#group				"nogroup"
#
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon. Not effective if
# systemd socket activiation is in use.
#
# For network
bind_to_address		"127.0.0.1"
#
# And for Unix Socket
#bind_to_address		"~/.mpd/socket"
#
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
#
#
port				"6600"
#
# This setting controls the type of information which is logged. Available 
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
#
#log_level			"default"
#
# If you have a problem with your MP3s ending abruptly it is recommended that 
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
#
#gapless_mp3_playback			"yes"
#
# Setting "restore_paused" to "yes" puts MPD into pause mode instead
# of starting playback after startup.
#
#restore_paused "no"
#
# This setting enables MPD to create playlists in a format usable by other
# music players.
#
#save_absolute_paths_in_playlists	"no"
#
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. The complete list of possible values can be
# found in the user manual.
#metadata_to_use	"artist,album,title,track,name,genre,date,composer,performer,disc"
#
# This setting enables automatic update of MPD's database when files in 
# music_directory are changed.
#
#auto_update	"yes"
#
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself.  There is no limit by default.
#
#auto_update_depth "3"
#
###############################################################################


# Symbolic link behavior ######################################################
#
# If this setting is set to "yes", MPD will discover audio files by following 
# symbolic links outside of the configured music_directory.
#
follow_outside_symlinks	"yes"
#
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#
follow_inside_symlinks		"yes"
#
###############################################################################


# Zeroconf / Avahi Service Discovery ##########################################
#
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#
#zeroconf_enabled		"yes"
#
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#
#zeroconf_name			"Music Player"
#
###############################################################################


# Permissions #################################################################
#
# If this setting is set, MPD will require password authorization. The password
# setting can be specified multiple times for different password profiles.
#
#password                        "password@read,add,control,admin"
#
# This setting specifies the permissions a user has who has not yet logged in. 
#
#default_permissions             "read,add,control,admin"
#
###############################################################################


# Database #######################################################################
#

#database {
#       plugin "proxy"
#       host "other.mpd.host"
#       port "6600"
#}

# Input #######################################################################
#

input {
        plugin "curl"
#       proxy "proxy.isp.com:8080"
#       proxy_user "user"
#       proxy_password "password"
}

#
###############################################################################

# Audio Output ################################################################
#
# MPD supports various audio output types, as well as playing through multiple 
# audio outputs at the same time, through multiple audio_output settings 
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
#
# An example of an ALSA output:
#
audio_output {
	type		     "alsa"
	name		     "My Alsa Device"
	device		     "hw:0,0"	# optional
	mixer_type       "hardware"	# optional
	mixer_device	 "default"	# optional
	mixer_control	 "PCM"		# optional
	mixer_index	      "0"		# optional
}
audio_output {
	type		     "alsa"
	name		     "MPD Jack Output"
	device		     "jackplugmpd"	# optional
	mixer_type       "software"	# optional
	mixer_device	 "default"	# optional
	mixer_control	 "PCM"		# optional
##	mixer_index	"0"		# optional
}
audio_output {
    type             "fifo"
    name             "my_fifo"
    path             "/tmp/mpd.fifo"
    format           "44100:16:2"
}

When I try to run mpc update --wait, I get this:

mpd error: Connection closed by the server

And once I get that, I can't run anything - not nmcpcpp nor Cantata. The only way I can play music again is by killing the process with pkill mpd, and restarting mpd.

jasonwryan · 2017-08-25 22:07:58

What is /DataPool?

Paste the output of:

mpd --no-daemon --stdout --verbose

d_fajardo · 2017-08-25 22:37:39

/DataPool is my zfs mount directory.

mpd --no-daemon --stdout --verbose:

config_file: loading file /home/dipswitch/.config/mpd/mpd.conf
exception: Failed to bind to '127.0.0.1:6600'
exception: nested: Failed to bind socket: Address already in use

This is while mpd is already running...

And as I said, everything was working fine before.

Last edited by d_fajardo (2017-08-25 22:38:20)

Slithery · 2017-08-25 22:54:19

https://bbs.archlinux.org/viewtopic.php?id=228901

Switching to a socket instead of a network connection fixed my mpd issues.
Still no idea whats preventing mpd from binding to localhost though.

Last edited by Slithery (2017-08-25 22:54:59)

loqs · 2017-08-25 23:30:59

@slithery has this issue been reported upstream?

d_fajardo · 2017-08-26 06:57:23

Just to clarify, my mpd is setup on a personal basis so I'm not using systemd to control it.

jasonwryan wrote:

Paste the output of:
mpd --no-daemon --stdout --verbose

If I kill mpd first with pkill mpd, then I run mpd --no-daemon --stdout --verbose, I get this:

config_file: loading file /home/dipswitch/.config/mpd/mpd.conf
libsamplerate: libsamplerate converter 'Fastest Sinc Interpolator'
vorbis: Xiph.Org libVorbis 1.3.5
opus: libopus 1.2.1
sndfile: libsndfile-1.0.28
simple_db: reading DB
curl: version 7.55.1
curl: with OpenSSL/1.1.0f
avahi: Initializing interface
avahi: Client changed to state 2
avahi: Client is RUNNING
avahi: Registering service _mpd._tcp/Music Player
avahi: Service group changed to state 0
avahi: Service group is UNCOMMITED
state_file: Loading state file /home/dipswitch/.config/mpd/state
avahi: Service group changed to state 1
avahi: Service group is REGISTERING
avahi: Service group changed to state 2
avahi: Service 'Music Player' successfully established.

So it seems mpd runs OK. But why is it refusing update? I can play music via nmcpcpp but the database remains as it was when I first used it and I have since added a lot more music. Meanwhiler Cantata always flags 'Connection to personal failed' where I used to just click 'Refresh Database' and my music folders will be updated.

slthery wrote:

Switching to a socket instead of a network connection fixed my mpd issues.

I'll have a look at this. It is starting to look like a server issue than mpd.

seth · 2017-08-26 08:16:43

My money is on the avahi daemon being the culprit.

d_fajardo · 2017-08-26 08:42:04

seth wrote:

My money is on the avahi daemon being the culprit.

Why do you think that is? Any debug options?

d_fajardo · 2017-08-26 08:58:49

slithery wrote:

Switching to a socket instead of a network connection fixed my mpd issues.

I've decided to give unix socket a try because when I try to browse music directory via nmcpcpp, I get flagged:

For browsing local filesystem connection to MPD via UNIX Socket is required

How do you create a Unix Socket?

Slithery · 2017-08-26 09:08:22

Edit the bind_to_address option in the mpd config and the mpd_host option in the ncmpcpp config.

Last edited by Slithery (2017-08-26 09:09:38)

d_fajardo · 2017-08-26 09:55:05

But shouldn't I have a socket defined in my mpd directory? Otherwise if I run

bind_to_address "~/.config/mpd/socket"

this seems like pointing to a socket configuration. Also what about Cantata, do I do the same binding?

[EDIT]

I got the socket working fine with nmcpcpp. I'll see how it will work with Cantata...

Last edited by d_fajardo (2017-08-26 10:07:49)

seth · 2017-08-26 10:11:20

d_fajardo wrote:

seth wrote:
My money is on the avahi daemon being the culprit.
Why do you think that is? Any debug options?

My gut told me ;-)

https://bbs.archlinux.org/viewtopic.php … #p1723064#
https://bbs.archlinux.org/viewtopic.php … 0#p1714350

Inspect the nsswitch config, disable avahi and restart mpd - see what happens.

d_fajardo · 2017-08-26 11:18:54

This is where things currently stands. MPD is working, meaning I can play music with no sound issues. With the unix socket, i can use nmcpcpp to navigate to my home folder, locate any track I want to play and play it with no problem. However it's database is not updated. With Cantata, I still get 'Connection to personal failed' problem. And with mpc update, I just get mpd error: Connection refused. Same behaviour whether avahi is running or not.
So basically the unix socket was a minor improvement but the actual problem is not solved. Why can't I update the database when 36 hours ago I could?
My intuition also tells me unless I can update via mpc, Cantata will continue to have update problem as well.
If it's Connection refused, is this a permission issue? Where to look?

Slithery · 2017-08-26 11:28:46

Have you told mpc to use the socket (using either using the -h flag or the MPD_HOST environment variable)?

Cantana may have a setting for the mpd host as well.

Last edited by Slithery (2017-08-26 11:31:48)

d_fajardo · 2017-08-26 11:34:25

Another question is if I delete the current DB, how can I generate a new one with mpd?

WorMzy · 2017-08-26 11:47:23

You stop being a help vampire and read the wiki.

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

d_fajardo · 2017-08-26 12:13:18

WorMzy wrote:

You stop being a help vampire and read the wiki.

Believe me WorMzy, I have read this many times. And this is HOW I got things working in the first place in the beginning. Like as I said, everything was working 36 hours ago. But why not now?
I can retrace the whole thing, delete everything and reinstall. But a bit anxious that nothing might not work anymore. At least now I can still play music. Just trying to understand what makes the database updating problem occur suddenly so I can perhaps avoid it in future upgrade.

seth · 2017-08-26 14:04:59

Ensure to kill any mpd daemon, undo the unix socket setup (since it's probably not the ideal solution anyway? No way to remote control it)
Next run "mpd --no-daemon --stdout --verbose 2>&1 | tee mpd.log" again and then try to connect it from a second shell using "mpc -v status 2>&1 | tee mpc.log" or "mpc -v update 2>&1 | tee mpc.log"

Post the actual and complete outputs from both shells (tee should have logged them in the files)

d_fajardo · 2017-08-26 22:37:38

Ok. Thanks seth. Here are the outputs:

mpd --no-daemon --stdout --verbose 2>&1 | tee mpd.log

config_file: loading file /home/dipswitch/.config/mpd/mpd.conf
exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
libsamplerate: libsamplerate converter 'Fastest Sinc Interpolator'
vorbis: Xiph.Org libVorbis 1.3.5
opus: libopus 1.2.1
sndfile: libsndfile-1.0.28
simple_db: reading DB
curl: version 7.55.1
curl: with OpenSSL/1.1.0f
avahi: Initializing interface
avahi: Client changed to state 2
avahi: Client is RUNNING
avahi: Registering service _mpd._tcp/Music Player
avahi: Service group changed to state 0
avahi: Service group is UNCOMMITED
state_file: Loading state file /home/dipswitch/.config/mpd/state
avahi: Service group changed to state 1
avahi: Service group is REGISTERING
avahi: Service group changed to state 2
avahi: Service 'Music Player' successfully established.
client: [0] opened from [::1]:49626
client: [0] process command list
client: process command "status"
client: command returned 0
client: process command "currentsong"
client: command returned 0
client: [0] process command list returned 0
client: [0] closed

And mpc -v status 2>&1 | tee mpc.log:

volume: 54%   repeat: off   random: off   single: off   consume: off

I'm suspecting you are on to something about avahi. First I kill avahi-daemon and socket entirely:
This is avahi-daemon status:

● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Sat 2017-08-26 23:26:11 BST; 14s ago
  Process: 10870 ExecStart=/usr/bin/avahi-daemon -s (code=exited, status=0/SUCCESS)
 Main PID: 10870 (code=exited, status=0/SUCCESS)
   Status: "avahi-daemon 0.7 starting up."

Aug 26 23:24:09 TUF-Z270 avahi-daemon[10870]: Network interface enumeration completed.
Aug 26 23:24:09 TUF-Z270 avahi-daemon[10870]: Registering new address record for fdb0:8900:7867:b200:2e56:dcff:fe39:e220 on bond0.*.
Aug 26 23:24:09 TUF-Z270 avahi-daemon[10870]: Registering new address record for 192.168.1.6 on bond0.IPv4.
Aug 26 23:24:10 TUF-Z270 avahi-daemon[10870]: Server startup complete. Host name is TUF-Z270.local. Local service cookie is 3649450365.
Aug 26 23:26:11 TUF-Z270 avahi-daemon[10870]: Got SIGTERM, quitting.
Aug 26 23:26:11 TUF-Z270 avahi-daemon[10870]: Leaving mDNS multicast group on interface bond0.IPv6 with address fdb0:8900:7867:b200:2e56:dcff:fe39:e220.
Aug 26 23:26:11 TUF-Z270 systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Aug 26 23:26:11 TUF-Z270 avahi-daemon[10870]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.1.6.
Aug 26 23:26:11 TUF-Z270 avahi-daemon[10870]: avahi-daemon 0.7 exiting.
Aug 26 23:26:11 TUF-Z270 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.

And the avahi-daemon.socket status:

● avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.socket; enabled; vendor preset: disabled)
   Active: inactive (dead) since Sat 2017-08-26 23:26:11 BST; 2min 27s ago
   Listen: /run/avahi-daemon/socket (Stream)

Aug 26 23:24:09 TUF-Z270 systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Aug 26 23:26:11 TUF-Z270 systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.

It looks like avahi is now inactive.

Now I run mpd again without avahi:

config_file: loading file /home/dipswitch/.config/mpd/mpd.conf
exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in use
libsamplerate: libsamplerate converter 'Fastest Sinc Interpolator'
vorbis: Xiph.Org libVorbis 1.3.5
opus: libopus 1.2.1
sndfile: libsndfile-1.0.28
simple_db: reading DB
curl: version 7.55.1
curl: with OpenSSL/1.1.0f
avahi: Initializing interface
avahi: Client changed to state 1
avahi: Client is REGISTERING
state_file: Loading state file /home/dipswitch/.config/mpd/state
avahi: Client changed to state 2
avahi: Client is RUNNING
avahi: Registering service _mpd._tcp/Music Player
avahi: Service group changed to state 0
avahi: Service group is UNCOMMITED
avahi: Service group changed to state 1
avahi: Service group is REGISTERING
avahi: Service group changed to state 2
avahi: Service 'Music Player' successfully established.

It looks like mpd starts avahi automatically. Is this normal?

Another thing I tried is to add the --wait flag to the mpc update to see what happens.
And now when I issue the command mpc -v update --wait 2>&1 | tee mpc.log, I get this:

mpd error: Connection closed by the server

Lend me your thoughts.

Last edited by d_fajardo (2017-08-26 22:38:06)

progandy · 2017-08-26 22:51:42

Do you have write permissions for your "~/.config/mpd/database? You might want to try to start mpd with a fresh empty database, so temporarily backup and remove the old database.

d_fajardo · 2017-08-26 22:59:30

I am using mpd as per user basis and not using systemd so yes I practically own the directory. I'll double check anyway.
And yes, I'll have ago at deleting the database (I'll back it up of course!) and try to recreate one. To recreate one, I assume one just needs to run mpd /path/to/config. Am I right or am I not?

Last edited by d_fajardo (2017-08-26 23:00:46)

seth · 2017-08-27 05:30:29

mpd doesn't start avahi for me - I'd suspect the socket is still lingering around or so (at least I don't have it explicitly disabled in the config - you might try) and my avahi related mpd output is just

avahi: Initializing interface
avahi: Client changed to state 101
avahi: Client is CONNECTING

However, there seems to be no connection error indicated in post #21 - is the (remaining?) problem *only* with database updates then?
What if you try to trigger "mpc update" instead?

d_fajardo · 2017-08-27 06:47:51

Yes, the remaining error is simply updating the database.

If I trigger mpc update --wait, I get:

mpd error: Connection closed by the server

I'm starting to look at resolv.conf. Currently this is what I have:

# Generated by resolvconf
domain lan
nameserver 192.168.1.1

Should I have a local (127.0.0.1) defined in this as well? Don't know much about DNS but I was just following your previous leads on avahi.

Last edited by d_fajardo (2017-08-27 07:02:17)

Arch Linux

#1 2017-08-25 19:17:46

[SOLVED] Cannot update mpd database after upgrade

#2 2017-08-25 19:23:19

Re: [SOLVED] Cannot update mpd database after upgrade

#3 2017-08-25 19:40:30

Re: [SOLVED] Cannot update mpd database after upgrade

#4 2017-08-25 22:07:58

Re: [SOLVED] Cannot update mpd database after upgrade

#5 2017-08-25 22:37:39

Re: [SOLVED] Cannot update mpd database after upgrade

#6 2017-08-25 22:54:19

Re: [SOLVED] Cannot update mpd database after upgrade

#7 2017-08-25 23:30:59

Re: [SOLVED] Cannot update mpd database after upgrade

#8 2017-08-26 06:57:23

Re: [SOLVED] Cannot update mpd database after upgrade

#9 2017-08-26 08:16:43

Re: [SOLVED] Cannot update mpd database after upgrade

#10 2017-08-26 08:42:04

Re: [SOLVED] Cannot update mpd database after upgrade

#11 2017-08-26 08:58:49

Re: [SOLVED] Cannot update mpd database after upgrade

#12 2017-08-26 09:08:22

Re: [SOLVED] Cannot update mpd database after upgrade

#13 2017-08-26 09:55:05

Re: [SOLVED] Cannot update mpd database after upgrade

#14 2017-08-26 10:11:20

Re: [SOLVED] Cannot update mpd database after upgrade

#15 2017-08-26 11:18:54

Re: [SOLVED] Cannot update mpd database after upgrade

#16 2017-08-26 11:28:46

Re: [SOLVED] Cannot update mpd database after upgrade

#17 2017-08-26 11:34:25

Re: [SOLVED] Cannot update mpd database after upgrade

#18 2017-08-26 11:47:23

Re: [SOLVED] Cannot update mpd database after upgrade

#19 2017-08-26 12:13:18

Re: [SOLVED] Cannot update mpd database after upgrade

#20 2017-08-26 14:04:59

Re: [SOLVED] Cannot update mpd database after upgrade

#21 2017-08-26 22:37:38

Re: [SOLVED] Cannot update mpd database after upgrade

#22 2017-08-26 22:51:42

Re: [SOLVED] Cannot update mpd database after upgrade

#23 2017-08-26 22:59:30

Re: [SOLVED] Cannot update mpd database after upgrade

#24 2017-08-27 05:30:29

Re: [SOLVED] Cannot update mpd database after upgrade

#25 2017-08-27 06:47:51

Re: [SOLVED] Cannot update mpd database after upgrade

Board footer