Music Player Daemon/トラブルシューティング - 版の履歴

Kusakata: カテゴリ変更

2019-02-28T16:47:34Z

カテゴリ変更

← 古い版		2019年3月1日 (金) 01:47時点における版
1行目:		1行目:
	[[Category:~~プレイヤー~~]]		[[Category:音楽]]
	[[en:Music Player Daemon/Troubleshooting]]		[[en:Music Player Daemon/Troubleshooting]]
	メインの記事は [[Music Player Daemon]]。		メインの記事は [[Music Player Daemon]]。

Kusakata: 同期

2017-01-24T12:03:26Z

同期

← 古い版		2017年1月24日 (火) 21:03時点における版
5行目:		5行目:
	== トラブルシューティング ==		== トラブルシューティング ==
	=== Autodetection failed ===		=== Autodetection failed ===
	MPD を起動すると、セットアップが自動検出されて、アウトプットやボリュームコントロールが設定されます。大抵はこれで上手くいきますが、システムによっては上手く行かないことがあります。アウトプットやミキサーコントロールを MPD に手動で指定することが可能です。{{ic\|/etc/mpd.conf.example}} から {{ic\|/etc/mpd.conf}} をコピーした場合、以下をアンコメントしてください:		MPD を起動すると、セットアップが自動検出されて、アウトプットやボリュームコントロールが設定されます。大抵はこれで上手くいきますが、システムによっては上手く行かないことがあります。アウトプットやミキサーコントロールを MPD に手動で指定することが可能です。{{ic\|/etc/mpd.conf.example}} から {{ic\|/etc/mpd.conf}} をコピーした場合、以下をアンコメントしてください (alsa 出力と alsa ミキサーの例):

	Example for alsa output type and alsa mixer:
	audio_output {		audio_output {
	type "alsa"		type "alsa"
18行目:		16行目:
	}		}

			MPD で ESD を使用した場合にパーミッションの問題が起こる場合は root で以下のコマンドを実行してください:
	'''Note:''' in case of permission problems when using ESD with MPD run this as root:
	# chsh -s /bin/true mpd		# chsh -s /bin/true mpd

42行目:		40行目:
	::1 localhost.localdomain localhost		::1 localhost.localdomain localhost

			=== mpd にクライアントで接続できない問題 ===
	=== Other issues when attempting to connect to mpd with a client ===
			一部のユーザーは以下のようなエラーが表示されてクライアントから mpd にアクセスできないと報告しています:
	Some have reported being unable to access mpd with various clients, for example seeing errors like these:
	$ ncmpcpp		$ ncmpcpp
	Cannot connect to mpd: Connection closed by the server		Cannot connect to mpd: Connection closed by the server
51行目:		49行目:
	2011-02-13 18:33:05 Not connected		2011-02-13 18:33:05 Not connected

	~~Please see posts on~~ ncmpcpp ~~on the~~ Arch ~~Forums~~ [https://bbs.archlinux.org/viewtopic.php?id=109962 ~~HERE~~] ~~and~~ [https://bbs.archlinux.org/viewtopic.php?id=113493 ~~HERE~~]~~. Also~~ ~~see~~ {{Bug\|22071}}.		ncmpcpp に関する Arch フォーラムの [https://bbs.archlinux.org/viewtopic.php?id=109962] や [https://bbs.archlinux.org/viewtopic.php?id=113493] の投稿や {{Bug\|22071}} を参照してください。

	==== ~~First~~ ~~fix~~ ====		==== 解決方法 1 ====
	~~Check~~ {{ic\|mpd.conf}} ~~for a line like~~ {{ic\|mpd.error}} ~~and remove it. The~~ mpd ~~error file is deprecated and has been removed.~~		{{ic\|mpd.conf}} に {{ic\|mpd.error}} という行があったら削除してください。mpd エラーファイルは廃止され削除されました。

	==== ~~Second~~ ~~fix~~ ====		==== 解決方法 2 ====
	{{Note\|I'm not so sure this is a good idea. There is a warning about changing the address to bind to in the default mpd.conf. If this does not help, you might want to comment out the changes.}}		{{Note\|I'm not so sure this is a good idea. There is a warning about changing the address to bind to in the default mpd.conf. If this does not help, you might want to comment out the changes.}}
			上記の設定で直らない場合、以下を {{ic\|mpd.conf}} に追加してください:
	If that doesn't help, add the following to {{ic\|mpd.conf}}:
	{{bc\|
	bind_to_address "127.0.0.1"		bind_to_address "127.0.0.1"
	port "6600"		port "6600"
⚫	}}

			その後、クライアントから 127.0.0.1 で接続してみてください。例えば ncmpcpp の設定ファイルに以下を追加:
	Afterwards, instruct your client to connect via 127.0.0.1. For example, add the following to the ncmpcpp config file:
	{{bc\|
	mpd_host "127.0.0.1"		mpd_host "127.0.0.1"
	mpd_port "6600"		mpd_port "6600"
	}}

	=== ~~Binding~~ to ~~IPV6~~ ~~before IPV4~~ ===		=== IPv4 よりも前に IPv6 が使われる ===
	起動時に、mpd が以下のメッセージを表示する場合:		起動時に、mpd が以下のメッセージを表示する場合:
	listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)		listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
			MPD は IPv4 にバインドする前に IPv6 インターフェイスにバインドしようとしています。IPv4 インターフェイスを使いたい場合、{{ic\|mpd.conf}} で以下のようにハードコードしてください:
	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"		bind_to_address "127.0.0.1"
			複数のバインドを指定することもできます。localhost やネットワークカードの外部 IP を listen させるには:
	Several binds can also be specified, for example, to have MPD listen on localhost and the external IP of your network card:
	bind_to_address "127.0.0.1"		bind_to_address "127.0.0.1"
	bind_to_address "192.168.1.13"		bind_to_address "192.168.1.13"
90行目:		84行目:
	The error is stating that mpd can't set the group. This is if you have set any other group in {{ic\|/etc/mpd.conf}} than the default: mpd. This is because of the default {{ic\|mpd.service}} file. It starts mpd as user mpd (and if no group specified with the default group of this user as stated in your {{ic\|/etc/passwd}}) and therefore mpd does not have any rights to change his group.		The error is stating that mpd can't set the group. This is if you have set any other group in {{ic\|/etc/mpd.conf}} than the default: mpd. This is because of the default {{ic\|mpd.service}} file. It starts mpd as user mpd (and if no group specified with the default group of this user as stated in your {{ic\|/etc/passwd}}) and therefore mpd does not have any rights to change his group.

	==== ~~First~~ ~~fix~~ ====		==== 解決方法 1 ====
	In {{ic\|/etc/mpd.conf}} ~~comment out the~~ {{ic\|1=group=}} ~~part or change it to~~ {{ic\|1=group=mpd}}		{{ic\|/etc/mpd.conf}} で {{ic\|1=group=}} をコメントアウトするか {{ic\|1=group=mpd}} と変更してください。

	==== ~~Second~~ ~~fix~~ ====		==== 解決方法 2 ====
			{{ic\|/etc/systemd/system/}} に {{ic\|mpd.service}} ファイルを作成して適切なグループを追加してください。例えば "audio" グループ mpd を実行する場合:
	Create a custom {{ic\|mpd.service}} file in {{ic\|/etc/systemd/system/}} and add your desired group. E. g. run mpd with the group "audio":
	{{hc\|/etc/systemd/system/mpd.service\|2=		{{hc\|/etc/systemd/system/mpd.service\|2=
	.include /usr/lib/systemd/system/mpd.service		.include /usr/lib/systemd/system/mpd.service
101行目:		95行目:
	}}		}}

	==== ~~Third~~ ~~fix~~ ====		==== 解決方法 3 ====
			{{ic\|/etc/passwd}} で mpd ユーザーのデフォルトグループを変更してください。
	Change the default group of the user mpd in your {{ic\|/etc/passwd}}.

	===MPD & ALSA===		===MPD & ALSA===
122行目:		116行目:
	options "dev=dmixer"		options "dev=dmixer"
	device "plug:dmix"		device "plug:dmix"
		⚫	}
	}}		}}

2015年7月8日 (水) 02:49にKusakataによる

2015-07-08T02:49:39Z

← 古い版		2015年7月8日 (水) 11:49時点における版
5行目:		5行目:
	== トラブルシューティング ==		== トラブルシューティング ==
	=== Autodetection failed ===		=== Autodetection failed ===
			MPD を起動すると、セットアップが自動検出されて、アウトプットやボリュームコントロールが設定されます。大抵はこれで上手くいきますが、システムによっては上手く行かないことがあります。アウトプットやミキサーコントロールを MPD に手動で指定することが可能です。{{ic\|/etc/mpd.conf.example}} から {{ic\|/etc/mpd.conf}} をコピーした場合、以下をアンコメントしてください:
	During the start of MPD, it tries to autodetect your set-up and configure output and volume control accordingly. Though this mostly goes well, it will fail for some systems. It may help to tell MPD specifically what to use as output and mixer control. If you copied {{ic\|/etc/mpd.conf}} over from {{ic\|/etc/mpd.conf.example}} as mentioned above, you can simply uncomment:

	Example for alsa output type and alsa mixer:		Example for alsa output type and alsa mixer:
83行目:		83行目:
	The error is stating that the user starting the process does not have permissions to become another user (mpd) which the configuration has told the process to run as.		The error is stating that the user starting the process does not have permissions to become another user (mpd) which the configuration has told the process to run as.

			この問題を解決するには、mpd を root で起動してください:
	To solve the issue, simply start mpd as root.
	{{bc\|# systemctl start mpd}}		{{bc\|# systemctl start mpd}}

2015年2月27日 (金) 03:44にKusakataによる

2015-02-27T03:44:29Z

← 古い版		2015年2月27日 (金) 12:44時点における版
21行目:		21行目:
	# chsh -s /bin/true mpd		# chsh -s /bin/true mpd

	=== MPD ~~hangs on first startup~~ ===		=== 最初の起動時に MPD がフリーズする ===
			mp3 タグが壊れているときによく起こるエラーです。以下にこの問題を解決する実験的な方法を記述します。必要なのは:
	This is a common error that's caused by corrupt mp3 tags.
	Here is an experimental way to solve this issue.
	Requirements:
	* kid3		* kid3
	* easytag		* easytag

			この方法は非常に長い時間がかかります (特にデータベースが巨大な場合)。大体、16GB のデータベースを修復するのに 2.5 時間くらいかかります。
	This method is very tedious, especially with a huge database. Just as a baseline it took 2.5h to fix a 16GB database.

	==== Easy Tag ====		==== Easy Tag ====
41行目:		39行目:

	=== Cannot connect to mpd: host "localhost" not found: Temporary failure in name resolution ===		=== Cannot connect to mpd: host "localhost" not found: Temporary failure in name resolution ===
			ネットワークから切断されていると、(ncmpcpp を使って) MPD に接続することはできません。解決方法は [[IPv6#IPv6 の無効化\|IPv6]] を無効化するか以下の行を {{ic\|/etc/hosts}} に追加することです:
	Cannot connect to MPD (with ncmpcpp), if you are disconnected from network. Solution is [[IPv6 - Disabling the Module\|disable IPv6]] or add line to /etc/hosts
	::1 localhost.localdomain localhost		::1 localhost.localdomain localhost

73行目:		71行目:

	=== Binding to IPV6 before IPV4 ===		=== Binding to IPV6 before IPV4 ===
			起動時に、mpd が以下のメッセージを表示する場合:
	If on startup, mpd displays the following message:
	listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)		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:		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:
87行目:		85行目:
	To solve the issue, simply start mpd as root.		To solve the issue, simply start mpd as root.
	{{bc\|# systemctl start mpd}}		{{bc\|# systemctl start mpd}}


	=== daemon: fatal_error: Failed to set group NN: Operation not permitted ===		=== daemon: fatal_error: Failed to set group NN: Operation not permitted ===
129行目:		126行目:
	To make the changes have effect, restart mpd (e.g. {{ic\|systemctl restart mpd}}, if it is a global configuration).		To make the changes have effect, restart mpd (e.g. {{ic\|systemctl restart mpd}}, if it is a global configuration).

	====~~High~~ CPU ~~usage with ALSA~~====		====ALSA で CPU の使用量が高くなる====
			ALSA で MPD を使用しているとき、MPD が CPU を大量に消費する場合があります (20-30%)。これはほとんどのサウンドカードがサポートしているのが 48kHz なのに対してほとんどの音楽は 44.1kHz であるために、MPD がリサンプリングを行ってしまうのが原因です。リサンプリングには CPU サイクルが大量に必要で、結果として使用量が高くなります。
	When using MPD with ALSA, users may experience MPD taking up lots of CPU (around 20-30%). This is caused by most sound cards supporting 48kHz and most music being 44.1kHz, thus forcing MPD to resample it. This operation takes lots of CPU cycles and results into high usage.

			{{ic\|/etc/mpd.conf}} の audio_output に {{ic\|auto_resample "no"}} を追加して MPD にリサンプリングを使わないようにすれば大抵は問題が解決します。
	For most users the problem should be solved by telling MPD not to use resampling by adding {{ic\|auto_resample "no"}} into audio_output-part of {{ic\|/etc/mpd.conf}}.

	{{hc\|mpd.conf\|2=		{{hc\|mpd.conf\|2=

Kusakata: ページの作成:「Category:プレイヤー en:Music Player Daemon/Troubleshooting メインの記事は Music Player Daemon。 == トラブルシューティング == === Auto...」

2015-02-12T06:05:40Z

ページの作成:「Category:プレイヤー en:Music Player Daemon/Troubleshooting メインの記事は Music Player Daemon。 == トラブルシューティング == === Auto...」

新規ページ

[[Category:プレイヤー]]
[[en:Music Player Daemon/Troubleshooting]]
メインの記事は [[Music Player Daemon]]。

== トラブルシューティング ==
=== Autodetection failed ===
During the start of MPD, it tries to autodetect your set-up and configure output and volume control accordingly. Though this mostly goes well, it will fail for some systems. It may help to tell MPD specifically what to use as output and mixer control. If you copied {{ic|/etc/mpd.conf}} over from {{ic|/etc/mpd.conf.example}} as mentioned above, you can simply uncomment:

Example for alsa output type and alsa mixer:
audio_output {
type "alsa"
name "My ALSA Device"
device "hw:0,0" # optional
format "44100:16:2" # optional
mixer_type "hardware"
mixer_device "default"
mixer_control "PCM"
}

'''Note:''' in case of permission problems when using ESD with MPD run this as root:
# chsh -s /bin/true mpd

=== MPD hangs on first startup ===
This is a common error that's caused by corrupt mp3 tags.
Here is an experimental way to solve this issue.
Requirements:
* kid3
* easytag

This method is very tedious, especially with a huge database. Just as a baseline it took 2.5h to fix a 16GB database.

==== Easy Tag ====
The purpose of {{pkg|easytag}} here is that easytag detects the error in the tags, but like MPD it hangs and dies. The trick here is that easy tags actually tells you what file is causing the problem on the status bar.
Before starting easytag make sure to have a terminal close to be ready to kill easy tag to avoid a hang. Once you are ready, on the tree view select the directory where all your music is located. By default easytag starts to search all subdirectories for mp3 files. Once you notice that easytag stopped scanning for songs, make note of the culprit and kill easytag.
{{Note|This task can also be achieved by editing mpd's config file and setting "log_level" from "default" to "verbose". restart mpd and look up the last entry in mpd's log file after mpd hangs. It is recommended to set "log_level" back to "default" after debugging, since the log file grows fast.}}

==== Kid3 ====
Here's where {{pkg|kid3}} comes in handy. With kid3 go to the offending song and rewrite one of the tags. then save the file. This should force kid3 to rewrite the whole tag again fixing the problem with MPD and easy tag hanging.

Repeat this procedure until your music library is done.

=== Cannot connect to mpd: host "localhost" not found: Temporary failure in name resolution ===
Cannot connect to MPD (with ncmpcpp), if you are disconnected from network. Solution is [[IPv6 - Disabling the Module|disable IPv6]] or add line to /etc/hosts
::1 localhost.localdomain localhost

=== Other issues when attempting to connect to mpd with a client ===
Some have reported being unable to access mpd with various clients, for example seeing errors like these:
$ ncmpcpp
Cannot connect to mpd: Connection closed by the server
$ sonata
2011-02-13 18:33:05 Connection lost while reading MPD hello
2011-02-13 18:33:05 Not connected
2011-02-13 18:33:05 Not connected

Please see posts on ncmpcpp on the Arch Forums [https://bbs.archlinux.org/viewtopic.php?id=109962 HERE] and [https://bbs.archlinux.org/viewtopic.php?id=113493 HERE]. Also see {{Bug|22071}}.

==== First fix ====
Check {{ic|mpd.conf}} for a line like {{ic|mpd.error}} and remove it. The mpd error file is deprecated and has been removed.

==== Second fix ====
{{Note|I'm not so sure this is a good idea. There is a warning about changing the address to bind to in the default mpd.conf. If this does not help, you might want to comment out the changes.}}
If that doesn't help, add the following to {{ic|mpd.conf}}:
{{bc|
bind_to_address "127.0.0.1"
port "6600"
}}

Afterwards, instruct your client to connect via 127.0.0.1. For example, add the following to the ncmpcpp config file:
{{bc|
mpd_host "127.0.0.1"
mpd_port "6600"
}}

=== Binding to IPV6 before IPV4 ===
If on startup, mpd displays the following 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"
Several binds can also be specified, for example, to have MPD listen on localhost and the external IP of your network card:
bind_to_address "127.0.0.1"
bind_to_address "192.168.1.13"

=== daemon: cannot setgid for user "mpd": Operation not permitted ===

The error is stating that the user starting the process does not have permissions to become another user (mpd) which the configuration has told the process to run as.

To solve the issue, simply start mpd as root.
{{bc|# systemctl start mpd}}

=== daemon: fatal_error: Failed to set group NN: Operation not permitted ===

The error is stating that mpd can't set the group. This is if you have set any other group in {{ic|/etc/mpd.conf}} than the default: mpd. This is because of the default {{ic|mpd.service}} file. It starts mpd as user mpd (and if no group specified with the default group of this user as stated in your {{ic|/etc/passwd}}) and therefore mpd does not have any rights to change his group.

==== First fix ====
In {{ic|/etc/mpd.conf}} comment out the {{ic|1=group=}} part or change it to {{ic|1=group=mpd}}

==== Second fix ====
Create a custom {{ic|mpd.service}} file in {{ic|/etc/systemd/system/}} and add your desired group. E. g. run mpd with the group "audio":
{{hc|/etc/systemd/system/mpd.service|2=
.include /usr/lib/systemd/system/mpd.service
[Service]
Group=audio
}}

==== Third fix ====
Change the default group of the user mpd in your {{ic|/etc/passwd}}.

===MPD & ALSA===
Sometimes, when using other audio outputs, e.g: some web pages containing Flash applets, MPD is rendered unable to play (until it is restarted). The error comes up in mpd's log:

Error opening alsa device "hw:0,0": Device or resource busy

Reasons for this may be:
* The sound card does not support hardware mixing (uses '''dmix''' plugin)
* An application does not work with ALSA's default settings

For a detailed description, it is recommended to take a look at [http://mpd.wikia.com/wiki/Alsa this] link.

This problem may be solved by adding the following lines to {{ic|mpd.conf}}:
{{hc|mpd.conf|2=
audio_output {
type "alsa"
name "Sound Card"
options "dev=dmixer"
device "plug:dmix"
}}

To make the changes have effect, restart mpd (e.g. {{ic|systemctl restart mpd}}, if it is a global configuration).

====High CPU usage with ALSA====
When using MPD with ALSA, users may experience MPD taking up lots of CPU (around 20-30%). This is caused by most sound cards supporting 48kHz and most music being 44.1kHz, thus forcing MPD to resample it. This operation takes lots of CPU cycles and results into high usage.

For most users the problem should be solved by telling MPD not to use resampling by adding {{ic|auto_resample "no"}} into audio_output-part of {{ic|/etc/mpd.conf}}.

{{hc|mpd.conf|2=
audio_output {
type "alsa"
name "My ALSA Device"
auto_resample "no"
}
}}

Although it may not give as drastic a speedup, enabling mmap may still speed things up:
{{hc|mpd.conf|2=
audio_output {
type "alsa"
name "My ALSA Device"
use_mmap "yes"
}
}}

Some users might also want to tell dmix to use 44kHz as well. More info about tuning performance of your MPD can be found on the [http://mpd.wikia.com/wiki/Tuning MPD wiki]

====Playing audio files with different rate (works for EMU 0202/0204/0404)====
To play audio files of different rate with automatic card rate change install pulseaudio and pulseaudio-alsa and keep using ALSA as output:
{{hc|mpd.conf|2=
audio_output {
type "alsa"
name "Emu 0202 USB"
device "hw:2,0"
}
}}