Simon Zou

FYI, this post seems like reporting exactly same issue with mine. https://discuss.hashicorp.com/t/nomad-1-7-3-upgraded-from-1-0-4-cpu-and-memory-allocation-showing-as-zero/62062

Hi, @jrasell , thanks for looking into it. 1) In terms of client side logs, surprisingly, there is not much when I run `nomad alloc status ` under nomad v1.7.6...

in case you need full logs from nomad clients, including the logs from running `nomad job run python-service.hcl` and `nomad alloc status `, below are logs right after startup log....

Now I assure more this is a bug, since it works fine on Windows and MacOs nomad clients, but not Linux, or at least CentOS 7.6. Can you please advise...

@jrasell hey, James, I found the root cause after debugging in code base. Basically [drivers/shared/executor/procstats/getstats.go@scanPIDs()](https://github.com/hashicorp/nomad/blob/363d2370f3cf895b98ea1a568015c9b493765131/drivers/shared/executor/procstats/getstats.go#L55) is supposed to fetch detected live pids that make up the task process tree /...