We used 'command: pg_isready -h host.example.nl' on Ubuntu 22.04 and it failed. As it turns out we had to change uid 65535 to 65534 in order to make it work. Uid 65534 is linked to nobody in our /etc/passwd, whereas uid 65535 does not occur.
Was the choice for 65535 deliberate? Is it perhaps better to do a lookup for the uid of the 'nobody' user and the guid for the 'nogroup' group? (https://cs.opensource.google/go/go/+/refs/tags/go1.19.2:src/os/user/lookup.go;l=32)
Reference:
We used 'command: pg_isready -h host.example.nl' on Ubuntu 22.04 and it failed. As it turns out we had to change uid 65535 to 65534 in order to make it work. Uid 65534 is linked to nobody in our /etc/passwd, whereas uid 65535 does not occur.
Was the choice for 65535 deliberate? Is it perhaps better to do a lookup for the uid of the 'nobody' user and the guid for the 'nogroup' group? (https://cs.opensource.google/go/go/+/refs/tags/go1.19.2:src/os/user/lookup.go;l=32)
Reference:
argus5/src/argus/monitor/prog/prog.go
Line 106 in 133696a