Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Jun 2016 00:20:17 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-threads@FreeBSD.org
Subject:   [Bug 204426] Processes terminating cannot access memory
Message-ID:  <bug-204426-16-fotT7Xha1w@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
References:  <bug-204426-16@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=3D204426

--- Comment #114 from Robert Blayzor <rblayzor@inoc.net> ---
Even with the suggested patch, now seeing processes occasionally hang in st=
ate:

dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  0  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  1  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  3  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de
dev@mta0 [~] procstat -ta | grep 7893
 7893 100155 dovecot          -                  2  120 sleep   vmf_de



When this happens we usually end up with a process that leaves a lot of
detached sockets stuck in a CLOSED state. The process normally becomes
unkillable and only a reboot clears the problem.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-fotT7Xha1w>