Marcel Witte
Marcel Witte
A recreation of the portainer service does not fix anything, interestingly a restart of the portainer service did help for one out of our four instances
I have to correct myself: After restarting the portainer instance, logging in is working exactly once, this is reproducible on all systems
I was using 1.21.0 (Image from 2 months age, ID: da2759008147). Because of the problems of today I pulled the latest tag which is from 3 weeks ago, ID: 2b4ddf654e1c....
We are not using any reverse proxy for the access to portainer, just accessing port 9000 directly. So the rate limiter per IP cannot be the problem here
Yes, I'm using a Swarm stack and after changing the port it seems to be working
Attached are the output and screenshots of lighthouse at about the same time (a few apps there open so there is a small positive RAM value this time :D ...
Second meminfo after a reboot, lighthouse is showing -48% now [meminfo2.txt](https://github.com/almindor/lighthouse/files/2593057/meminfo2.txt)
Second stat, it is showing more cpu cores now, so perhaps really changing dynamically [stat2.txt](https://github.com/almindor/lighthouse/files/2593060/stat2.txt)
[cpuinfo.txt](https://github.com/almindor/lighthouse/files/2593170/cpuinfo.txt)
Any idea when this will be fixed?