Comment 49 for bug 1752411

@Erich - infinite hangs are usually due to the kernel somewhere, while suggesting dig was a good idea just to try I wonder if we would have to find what "host" actually hangs on to be sure that "dig" in turn will not some day block on just the same.

Can one of you affected when the "host" command hangs check if it is spinning in userspace or if it is a kernel wchan?
$ cat /proc/<pid of host>/wchan
and
$ perf top -p <pid of host>
$ strace -rtf -p <pid of host>
should help to get an idea what it is blocking on.

@Trent - you said you started on strace already, maybe you can provide the full logs here?
Also was it spinning in strace (on the same things) or just waiting?