When running pgbench-tools in remote container getting pid kill errors

[sstubbs]

Traceback (most recent call last):
  File "../../kill_pg", line 29, in <module>
    kill_pg(int(sys.argv[1]))
  File "../../kill_pg", line 12, in kill_pg
    pgid = os.getpgid(pid)
OSError: [Errno 3] No such process
Traceback (most recent call last):
  File "../../kill_pg", line 29, in <module>
    kill_pg(int(sys.argv[1]))
  File "../../kill_pg", line 12, in kill_pg
    pgid = os.getpgid(pid)
OSError: [Errno 3] No such process
./benchwarmer: line 254:   604 Killed                  ./timed-os-stats meminfo > results/$TEST/meminfo.log  (wd: /usr/local/lib/pgbench-tools)

Getting this error when running the benchmarks from a container thats accessing the postgres database container remotely

[sstubbs]

Is there any setting to stop this running via a config option?

[gregs1104]

There is not an option to avoid the monitoring scripts so far. Instead I've spent the last three months adding more monitoring. Since that's done now and the container case is important to many people, I'll add a config option for that before the soon upcoming release.

[gregs1104]

Did this work but forgot to update the ticket. There's a parameter named OSDATA that defaults to 1, change it to 0 and the collectors don't run.