Tim Gross

I've found that Windows returns `ERROR_INVALID_PARAMETER` at the drop of a hat, but that's a good catch. The added bit of context is the sometimes-unfortunate decision that Go made to...

Hi @PayStreamArmitsteadJ. What's you're seeing isn't identical, but it sure smells similar. I'm not sure where you're getting this idea from: > The executor failed due to not being able...

> I have only experienced this issue once and it was affecting our production cluster, so I had to remedy the situation right away. Therefore, I do not know if...

I've updated this issue to make sure it gets some attention on our internal tracker. I also have some suspicion that this may be related to https://github.com/hashicorp/nomad/issues/23969

@CullenShane I was hoping your reproduction would be the clue I needed, but I think it's possibly related but not _quite_ the same. It looks like we're simply returning an...

Ok, I tried some more to reproduce this and I want to make sure that I've documented here a specific bug where the proximate cause is the executor process fails...

I've got a fix up here for the executor orphaning the child processes: https://github.com/hashicorp/nomad/pull/24214. I'll open a new issue for improving the UX of the error messages.

Opened #24220 and #24219 as follow-ups from this issue.

The fix for the child process being orphaned will ship in Nomad 1.9.1 (with Enterprise backports). The executor failure itself is _likely_ fixed by #24182, and that's why we're seeing...

I also wanted to leave a note here that this rolls up into a concept we've been talking about internally as Node Identity. See also https://github.com/hashicorp/nomad/issues/16574 for related ideas.