Restarting journald causes Nomad to get stuck in a loop with high CPU usage

[maxvt]

strace output shows:
[pid 30581] write(1, "==> Caught signal: broken pipe", 30 <unfinished ...>

it appears that nomad gets a SIGPIPE, tries to log an entry about it, and this causes another SIGPIPE.

This continues #1798 and is very similar to hashicorp/consul#2842.

Nomad version

0.6.0

Operating system and Environment details

Ubuntu Xenial 16.04

Issue

Restarting journald shouldn't cause Nomad to go crazy

Reproduction steps

Restart journald

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.