Cannot see stats for any running containers

[warneford]

I cannot see stats for any containers in the portainer UI,

I'm running Portainer 2.13.1 via docker on a QNAP TS-453BE (firmware QTS 5.0.0.2055)

Docker version 20.10.14-qnap2, build be617d7

deployed as follows:
sudo docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

see this error: Unexpected pid '311801admin': strconv.Atoi: parsing "311801admin": invalid syntax

x

Originally posted by @warneford in #4818 (comment)

[Val-istar-Guo]

Maybe this can be used as a reference #3898

[MikeWang000000]

I encountered the same problem. After some investigation, I found moby/moby#34282 (comment).

As a workaround, you can run the command below at startup to limit pid digits less than 6.

sysctl -w kernel.pid_max=32768

[titus91360]

I'm not really sure where to use the sysctl -w kernel.pid_max=32768
You use it on nas or on docker ?
Because I try to use it via SSH on Nas, but still havee PID with too much digits :(

[MikeWang000000]

I'm not really sure where to use the sysctl -w kernel.pid_max=32768 You use it on nas or on docker ? Because I try to use it via SSH on Nas, but still havee PID with too much digits :(

You should run it at NAS startup on host machine (not in docker container).
This limit only applies to new created processes. PIDs of running processes will not change.

If you are using QNAP NAS, try this:
https://www.qnap.com/en/how-to/faq/article/running-your-own-application-at-startup

Then put sysctl -w kernel.pid_max=32768 into autorun.sh.
Finally chmod +x autorun.sh.

[titus91360]

Super, thanks a lot !
It works like a charm :)

[titus91360]

I spoke too quickly...
After an hour, my PIDs are too high again and I no longer have any stats :(

[MikeWang000000]

you can run sysctl kernel.pid_max to verify if your script really takes effect.

Here is my startup.sh

#!/bin/sh
export PATH="/bin:/sbin:/usr/bin:/usr/sbin"

sysctl -w kernel.pid_max=32768

exit 0

And don't forget to check this config:

[titus91360]

Ok, really strange things. I'm manage to use autorun.sh
But, after a wild, the kernel.pid_max change automatically and return to default value. Really frustrating ...

[titus91360]

ok, What I see is that my autorun.sh isn't running properly. I managed to correct the error and it's seem to be fine know 😉