From owner-freebsd-net@freebsd.org  Wed Jul  5 17:25:59 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10A36D8B7F4
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed,  5 Jul 2017 17:25:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E789E64A17
 for <freebsd-net@FreeBSD.org>; Wed,  5 Jul 2017 17:25:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v65HPrP2012433
 for <freebsd-net@FreeBSD.org>; Wed, 5 Jul 2017 17:25:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect
Date: Wed, 05 Jul 2017 17:25:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: crash, needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: peixoto.cassiano@gmail.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: eugen@freebsd.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-186114-2472-Q3gaFTUU9n@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-186114-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-186114-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 17:25:59 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114

--- Comment #101 from Cassiano Peixoto <peixoto.cassiano@gmail.com> ---
(In reply to Konstantin Belousov from comment #100)
Hi guys,

I had the issue today, but with a different behavior. It didn't show on CPU
state as uwrlck anymore. The process was running as usual, but all customers
connected stopped working.

I tried to check both mpd5 console and web but didn't answer.

I tried to killall -QUIT mpd5 process with no success, I try to kill -9 the=
 pid
process with no success as well. Looks like a zombie process.

At last i tried to reboot the server, and didn't work. I had to reset the
server to boot again. :(

--=20
You are receiving this mail because:
You are on the CC list for the bug.=