OK, I tracked it down and I think I'm getting somewhere: I'm able to reproduce it when journald is restarted. I thought about it because it of the stderr error, and because it seems to happen on upgrades mostly.
Ideally, I would track down stdout/stderr usage in Zaqar to remove that issue. It's possible that it doesn't use loggers correctly, so get into that issue more than other services.
OK, I tracked it down and I think I'm getting somewhere: I'm able to reproduce it when journald is restarted. I thought about it because it of the stderr error, and because it seems to happen on upgrades mostly.
https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 84923 ought to be the culprit, though I wasn't able to verify if the environments have the fix or not.
Ideally, I would track down stdout/stderr usage in Zaqar to remove that issue. It's possible that it doesn't use loggers correctly, so get into that issue more than other services.
In the mean time. I proposed https:/ /review. rdoproject. org/r/# /c/4941/ which ought to workaround the issue by restarting zaqar when it fails.