Date: Wed, 05 Jul 2017 18:01:25 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect Message-ID: <bug-186114-2472-XsUNPkaj9e@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 --- Comment #103 from Eugene Grosbein <eugen@freebsd.org> --- (In reply to Cassiano Peixoto from comment #101) In fact, a zombie process is not a process anymore. It does not prevent your from restarting new instance of mpd5. Did you look at ps output to check re= al state of mpd5 or tried to restart it? Also, a process may become a zombie only if it did not detach properly at s= tart as normal daemons do (and mpd5 does it) AND its parent does not properly re= ap its children. init(8) does it just fine for normal daemons including mpd5. Do you run mpd5 in detached mode using -b flag? If so, I highly doubt it be= came a zombie. More likely, it could stuck in some uninterruptable system call b= ut that's pretty unusual too. If you run mpd5 in "foreground" mode using another supervising daemon like init(8) itself, that's another story. And what did you have in the log of mpd5 corresponding that time? You showed no diagnostics: ps -l output, mpd logs, kernel dmesg logs, something? And system reboot cleans it all, so it seems you had some external problem = just that took more time to disappear and second reboot just gave it that time. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-186114-2472-XsUNPkaj9e>