Unable to retrieve and failure

Hi,

A problem suddenly arose, I cannot access the stacks, the services, or the containers under portainer.
Each time we have the message “failure” “unable to retrieve stack” and ditto for containers and services.

on the other hand, secret, volumes., works very well
I stacked rm and raised and it’s the same.

Best regard

Olivier

Can you please give us more information about your setup?

For instance, what version of Portainer are you using?
How was your Portainer instance installed?
Are you on a desktop/server CPU or an ARM processor?
What are the steps you take to produce this error?

Thanks,
David (Staff)

Hi David,

My answers :

For instance, what version of Portainer are you using? → 1.24.1
How was your Portainer instance installed? → on docker swarm
Are you on a desktop/server CPU or an ARM processor? → CPU SERVER
What are the steps you take to produce this error? → connected to portainer, the problem is when we click on Stack, services, containers, etc….

We have a VPN, and I think it’s a very long timeout… it works best on live site….

Analyse firefox :
Unable to retrieve stacks Un objet “vide” provoque une erreur javascript : Error: can’t access property “map”, e is null o.containers/<@https://portainer.sdse.intranet.justice.gouv.fr/main.50213a000e42f5c05bcc.js:1:869946 s/</<@https://portainer.sdse.intranet.justice.gouv.fr/vendor.50213a000e42f5c05bcc.js:47:105701

We have a functioning DEV server. The only difference is the docker version:

DEV server (no problem): docker 18 CE
PROD server (problem unable to retrieve): docker 00

Best regard

Olivier

Hi
as per above information shared, both docker daemon and portainer are running on a older version. Requesting to upgrade docker daemon portainer to latest version in all the dev nodes. please use portainer-ce image for pulling 2.1.1 latest release
maybe you could have a look at this as a reference
https://documentation.portainer.io/v2.0/upgrade/upgrade/

Ok, thanks ! it’s done.

And we found the problem. We placed the following order: “docker volume prune”

Best regard