Dropbear processes getting into uninterruptible I/O process "D" state

[Matt Johnston]

Hi Binny,

I don't think it's related to 2019.78

Usually D state means something else is wrong on the system, bad NFS mounts or IO devices. Can you strace the stuck processes?

Cheers,
Matt

On 9 October 2019 10:53:56 am GMT+07:00, "Jeshan, Binny" <Binny.Jeshan at netscout.com> wrote:
>Dear all in the mailing list,
>
>We are seeing a problem with 2018.76 version of the dropbear SSH server
>which exhibits the following:
>
>
>The processes go into uninterruptible "D" state and lies there,
>couldn't be killed nor shutdown.
>[cid:image001.jpg at 01D57E82.261498F0]
>
>The stuck processes in the bad state show the below behavior of two
>open pipes that are not closed.
>
>[cid:image002.jpg at 01D57E82.261498F0]
>
>The last process with PID 394 seems to work fine, and has no open IPCs.
>
>
>When I look at the release notes of 2019.78, I see this: "2019.78 - 27
>March 2019
>
>- Fix dbclient regression in 2019.77. After exiting the terminal would
>be left
>  in a bad state. Reported by Ryan Woodsmall
>"
>
>Is the problem that we see is same as you fixed? Please suggest. Your
>feedback and ideas will help.
>
>
>Thanks
>Binny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20191009/b3bddba2/attachment-0001.htm