On 10/26/2017 06:10 PM, Michael Biebl wrote:
> Control: tags -1 moreinfo
>
> upstream requested this information at
> https://github.com/systemd/systemd/issues/7172#issuecomment-339601311:
>
> "any chance you can run strace -p1 -s 500 before this, then trigger
> this, so that we can see where
Control: tags -1 moreinfo
upstream requested this information at
https://github.com/systemd/systemd/issues/7172#issuecomment-339601311:
"any chance you can run strace -p1 -s 500 before this, then trigger
this, so that we can see where precisely the ENOTCONN is generated"
--
Why is it that
Processing control commands:
> tags -1 moreinfo
Bug #879603 [systemd] systemd: network service enters failed state when client
goes away too fast
Added tag(s) moreinfo.
--
879603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879603
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On 10/23/2017 01:31 PM, Michael Biebl wrote:
> Am 23.10.2017 um 12:21 schrieb Julien Cristau:
>> Package: systemd
>> Version: 232-25+deb9u1
>> User: debian-ad...@lists.debian.org
>> Usertag: needed-by-DSA-Team
>>
>> It looks like systemd has a race condition where instead of giving up
>>
Am 23.10.2017 um 12:21 schrieb Julien Cristau:
> Package: systemd
> Version: 232-25+deb9u1
> User: debian-ad...@lists.debian.org
> Usertag: needed-by-DSA-Team
>
> It looks like systemd has a race condition where instead of giving up
> gracefully when a client goes away, it enters a bogus failure
Package: systemd
Version: 232-25+deb9u1
User: debian-ad...@lists.debian.org
Usertag: needed-by-DSA-Team
It looks like systemd has a race condition where instead of giving up
gracefully when a client goes away, it enters a bogus failure mode.
●
