Re: POLLHUP detected on devd socket

From: Warner Losh <imp_at_bsdimp.com>
Date: Sun, 23 Jan 2022 23:58:27 UTC 
On Sun, Jan 23, 2022 at 1:07 PM Dima Panov <fluffy@freebsd.org> wrote:

> Moin!
>
>
> I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT.
> Both hosts have zfsd enabled, and after devd die by signal 15 all other
> daemons such as sshd, crond, syslogd (almost all runned daemons) stopeed by
> signal 15 too. At least, as it shows by system logs.
>

Signal 15 is SIGTERM, which is the software signal from kill(1)....

Warner


> Will try to play with zfsd disabled, as suggested.
>
> --
> Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team
> (fluffy@FreeBSD.org, https://t.me/dima_panov)
>
> On Sunday, Jan 23, 2022 at 12:03 PM, tech-lists <tech-lists@zyxst.net>
> wrote:
> On Sun, Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote:
>
> Is it reproducible? ie can you trigger it post boot?
>
> It is very strange that devd dying would kill anything else running -
> I have stopped and started it a lot while testing devd scripts and
> I haven't seen anything else break.
>
> One idea would be to hack up devd's rc.d script and run it under
> ktrace and try and get some clues.
>
>
> I can try that, thanks for the suggestion.
>
> Right now I'm thinking it's tied to zfsd, since disabling that
> service I've not seen the issue.
> --
> J.
>
>