On Mon, 09 Jun 2014 02:02:02 -0400
Teresa e Junior <teresaejun...@gmail.com> wrote:
> On Mon, 9 Jun 2014 09:53:31 +0400, Reco wrote:
> > Your network configuration may be the cause of this. Can you please run
> > mpc like this, and show the result:
> >
> > strace -e trace=network mpc
>
> $ strace -e trace=network mpc
> socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
> connect(3, {sa_family=AF_FILE, path="/var/run/mpd/socket"}, 110) = -1
> ENOENT (No such file or directory)
So, mpc tries standard mpd socket and fails. Adding said socket to
mpd.conf (via bind_address) should solve the issue.
> socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_TCP) = 3
> connect(3, {sa_family=AF_INET, sin_port=htons(6600),
> sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in
> progress)
> getsockopt(3, SOL_SOCKET, SO_ERROR, [111], [4]) = 0
> error: Connection refused
And that's interesting. mpc tries to connect to 127.0.0.1:6600 and
fails, but the error shows 'connection refused', not 'failed to resolve
hostname'. Is your mpd running?
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20140609103009.4808500efc2461a74d363...@gmail.com
