pi-consensus-stub Container error

[MingYanWu]

2024/6/11 docker desktop: 4.31.1 pi node: 0.4.11 Infinite errors, unable to verify, unable to open the correct container, what should I do?

[MingYanWu]

It seems the problem is not with whale version 4.31.1, but with node 0.4.11. Because my original whale version was 4.25.2, I upgraded it to see if there would be any version conflicts. Apparently this is not the case.This problem occurred on June 11, 2024. This problem has not occurred before.

[MingYanWu]

I reset a new container at 2024/6/12 02:00, and the attached node has not exited and cannot be started. If you need to reset and start a new container, the blockchain will need to be resynchronized. It depends on the individual. The host requires network acceleration, so there is no need to use the old one.

[adnanoncevarlik]

Hi, I have the similar issue. In Docker Desktop there is a pi-consensus-stub container but Node can not run properly. Here is the screen shot. Whats happened in last ten days? I don't know but now Pi Node App out of order.

Whats going on in PiNode App? How can I fix it? In last 10 days, sometimes in my Docker Programme pi-node-update named container appeared. It stucks when it was running. It is so confusing.

What must I do? Any sugestions?

Thanks in advance.

[MingYanWu]

You can create a new container according to my diagram, but it must be synchronized according to your computer configuration and network speed.

[adnanoncevarlik]

Thanks so much, it seems to be working now. But what I don't understand is why we set only 3 ports and why the order of the port like that? What about other Ports? Also, in the second picture you sent, while the port numbers we entered are on the left, what do the port numbers on the right do and why did we enter 3 of them? We had forwarded 10 ports in total, but why did we use 3 ports? Are the port numbers we entered sufficient? Why didn't we use the other idle port numbers? We operated this Container manually. The port numbers we entered on the port number entry screen and the numbers on the right do not match. I don't understand. Thank you for your help. I will inform you about the next situation.

[adnanoncevarlik]

@MingYanWu Bro, now it's gone again. It worked couple of hours but now container disappeared. I don't know whats has happened but now container is absent. Node got stucked again same status. Whats going on I do not know. What can I do? Have you got any idea to offer me?

[mcass75]

I had problem a few days ago it suddenly showed stub container and after an hour of it running it stopped and i could not fix it by just deleting and reinstalling pi node and docker it just kept throwing same stub container. I fixed the problem by signing out of my pi node then i reset my P.C on Windows 11 removing all files and apps, i then reinstalled Pi Node and Docker and sgned back into Pi Node it gave me a new passcode, it then gave me a new container and node and has been working good last few days, hope this might help. Kind Regards.

[adnanoncevarlik]

@mcass75 Bro, like my situation. I did it before. I cleaned all the data all programmes all the directories and registry records in the Windows Registry but I did not signed out. I'll try it, thanks for the advice :)

[adnanoncevarlik]

Hi @mcass75 bro, I tried the what you said in the my previous tries but I did not success. But I had have never signed out of the node app. I will try with the signing out of the pi node app process.

Here is the What did I do with your advices, (All steps are included) I signed out from the Pi Node App, I closed the Pie Node App, I quit the Docker Desktop Ver 4.19.0, I Uninstalled firstly PiNode App, I Uninstalled Docker Desktop App, I deleted all the following directories, C:\Users\adnan\AppData\Roaming\PiNetwork C:\Users\adnan\AppData\Roaming\Docker C:\ProgramData\DockerDesktop C:\Users\adnan\ .docker I cleaned unused registry entries with CCleaner Tool, I Manually checked all registry records for Docker Desktop and Pi Node App and deleted all the entry records, I searched for Docker, PiNetwork and Pi Network words in the and deleted but some registry entries did not delete, because of the windows denied to delete all the entries. But almost %100 cleaned. I Shut down the Notebook and waited for 10 seconds than start the notebook again with all the good prayers :) After the starting of the notebook, I installed the Docker Desktop 4.19.0 Version. Because this trouble has appeared/came with the upgrade of to the newest version of Docker Desktop around ten days ago. I started the Docker Desktop (There is no container or image file in the Docker Desktop, I cheked twice :) ) I Installed Pi Network (0.4.11 Version) and Logged in again. I choosed the Node App button on the Pi Network App. Pi Node started the loaded of the first run. Now everything is freshed. I rechecked my ports in the "Visit Tech Setup" button/link on the screen. Port Listener Container downloaded and Checked all the ports are Open Status (there is no obstacle for the properly run) All ports Open, Docker Desktop Installed and ready. I Turned On the Node Switch. And I pressed "Troubleshoot" button/link on the app. I Turned On The "Run the optional blockchain API service" switch also. After downloading process Consensus container has created again. Now it is running. Thank you so much. I will inform about the future status of the application.

[adnanoncevarlik]

Hi @mcass75 & @MingYanWu ,

Bad news, still same. pi-consensus turn to pi-consensus-stub container. In Troubleshoot screen Consensus container: absent, There is a situation like this. In the line written Consensus Container, the situation constantly changes from ABSENT to CREATING and CREATING to ABSENT status. It is continuously like that. It is so interesting. What happened to the pi-consensus container? When did it change to a pi-consensus-stub container? I don't know and it frustrates me. And there is no information about the pi-consensus-stub container (at least I did not find yet). I wish Pi Developer team may correct this BUG.

[MingYanWu]

You delete the extra container of the whale, then rebuild the new container according to the steps in my picture, and then let the node synchronize the blockchain,Otherwise, we will have to help you set up new nodes remotely.

[adnanoncevarlik]

@MingYanWu Thanks for the info, I'm gonna explain what I did, When in the Pi Node App "Turn the Node on" if the switch ON status, I tried to delete "pi-consensus-stub" container, it created immediately again. I deleted again, it created again. Then I turned OFF the Node Switch then deleted the "pi-consensus-stub" container. Everything seemed to be fine. Then I created a new container by the steps like you explained previous answers. The Container Upped and Ran automatically. After that I tried to Turn the NODE SWITCH ON. "pi-consensus" container that I've created automatically deleted and damn "pi-consensus-stub" container created automatically and PiNode App get stucked again. Then I Turn the NODE SWITCH OFF, deleted again "pi-consensus-stub" container, after that I created and ran manually a new "pi-consensus" container again. If the NODE SWITCH is in the OFF position, the CONTAINER I just created named "pi-consensus" stops itself within 3-4 seconds. Here is the Logs,

2024-06-20 01:37:29 <----- (First Manually Starts Here) 2024-06-20 01:37:29 Starting Stellar Quickstart 2024-06-20 01:37:29 2024-06-20 01:37:29 mode: ephemeral 2024-06-20 01:37:29 network: testnet (Pi Testnet) 2024-06-20 01:37:29 postgres user: stellar 2024-06-20 01:37:29 postgres password: 8ylqD0MiykX0sdKl 2024-06-20 01:37:29 finalize-pgpass: ok 2024-06-20 01:37:31 init-postgres: ok 2024-06-20 01:37:31 postgres: up 2024-06-20 01:37:32 create-horizon-db: ok 2024-06-20 01:37:32 create-core-db: ok 2024-06-20 01:37:32 stellar-postgres-user: ok 2024-06-20 01:37:32 chown-core: ok 2024-06-20 01:37:32 finalize-core-config-pgpass: ok 2024-06-20 01:37:32 finalize-core-config-run-standalone: ok 2024-06-20 01:37:32 finalize-core-config-manual-close: ok 2024-06-20 01:37:32 set-private-key: ok 2024-06-20 01:37:33 init-core-db: ok 2024-06-20 01:37:33 chown-horizon: ok 2024-06-20 01:37:33 init-horizon-db: ok 2024-06-20 01:37:34 postgres: down 2024-06-20 01:37:34 starting supervisor 2024-06-20 01:37:34 2024-06-19 22:37:34,294 CRIT Supervisor running as root (no user in config file) 2024-06-20 01:37:34 2024-06-19 22:37:34,299 INFO RPC interface 'supervisor' initialized 2024-06-20 01:37:34 2024-06-19 22:37:34,299 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-20 01:37:34 2024-06-19 22:37:34,299 INFO supervisord started with pid 1 2024-06-20 01:37:35 2024-06-19 22:37:35,302 INFO spawned: 'postgresql' with pid 168 2024-06-20 01:37:35 2024-06-19 22:37:35,303 INFO spawned: 'stellar-core' with pid 169 2024-06-20 01:37:35 2024-06-19 22:37:35,303 INFO reaped unknown pid 165 2024-06-20 01:37:36 2024-06-19 22:37:36,346 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 01:38:33 Unlinking stale socket /var/run/supervisor.sock 2024-06-20 01:37:36 2024-06-19 22:37:36,347 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-20 01:38:33 <----- (Second Manually Starts Here and there is no LOG Record whats happened to First Start) 2024-06-20 01:38:33 Starting Stellar Quickstart 2024-06-20 01:38:33 2024-06-20 01:38:33 mode: ephemeral 2024-06-20 01:38:33 network: testnet (Pi Testnet) 2024-06-20 01:38:33 postgres: config directory exists, skipping copy 2024-06-20 01:38:33 supervisor: config directory exists, skipping copy 2024-06-20 01:38:33 stellar-core: config directory exists, skipping copy 2024-06-20 01:38:33 horizon: config directory exists, skipping copy 2024-06-20 01:38:33 postgres: already initialized 2024-06-20 01:38:33 chown-core: ok 2024-06-20 01:38:33 core: already initialized 2024-06-20 01:38:33 horizon: already initialized 2024-06-20 01:38:33 starting supervisor 2024-06-20 01:38:33 2024-06-19 22:38:33,666 CRIT Supervisor running as root (no user in config file) 2024-06-20 01:38:33 2024-06-19 22:38:33,972 INFO RPC interface 'supervisor' initialized 2024-06-20 01:38:33 2024-06-19 22:38:33,973 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-20 01:38:33 2024-06-19 22:38:33,973 INFO supervisord started with pid 1 2024-06-20 01:38:34 2024-06-19 22:38:34,975 INFO spawned: 'postgresql' with pid 20 2024-06-20 01:38:34 2024-06-19 22:38:34,976 INFO spawned: 'stellar-core' with pid 21 2024-06-20 01:38:34 2024-06-19 22:38:34,976 INFO reaped unknown pid 17 2024-06-20 01:38:36 2024-06-19 22:38:36,040 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 01:38:36 2024-06-19 22:38:36,040 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 01:38:37 2024-06-19 22:38:37,934 WARN received SIGTERM indicating exit request 2024-06-20 01:38:37 2024-06-19 22:38:37,935 INFO waiting for stellar-core, postgresql to die 2024-06-20 01:38:41 2024-06-19 22:38:41,455 INFO waiting for stellar-core, postgresql to die 2024-06-20 01:38:41 2024-06-19 22:38:41,800 INFO stopped: stellar-core (exit status 0) 2024-06-20 01:38:41 2024-06-19 22:38:41,836 INFO stopped: postgresql (exit status 0)

Let me tell you what I observed. The text "Your computer is not running the blockchain" written under the Switch in the PiNode App changes to "Loading" when I run the CONTAINER manually. After 3-4 seconds, the CONTAINER I just created stops and the "Loading" text changes to "Your computer is not running the blockchain" again.

here is the (cleaned) LOG records about last try,

2024-06-20 01:47:59 2024-06-20 01:47:59 Starting Stellar Quickstart 2024-06-20 01:47:59 2024-06-20 01:47:59 mode: ephemeral 2024-06-20 01:47:59 network: testnet (Pi Testnet) 2024-06-20 01:47:59 postgres: config directory exists, skipping copy 2024-06-20 01:47:59 supervisor: config directory exists, skipping copy 2024-06-20 01:47:59 stellar-core: config directory exists, skipping copy 2024-06-20 01:47:59 horizon: config directory exists, skipping copy 2024-06-20 01:47:59 postgres: already initialized 2024-06-20 01:47:59 chown-core: ok 2024-06-20 01:47:59 core: already initialized 2024-06-20 01:47:59 horizon: already initialized 2024-06-20 01:48:00 starting supervisor 2024-06-20 01:48:00 2024-06-19 22:48:00,142 CRIT Supervisor running as root (no user in config file) 2024-06-20 01:48:00 2024-06-19 22:48:00,148 INFO RPC interface 'supervisor' initialized 2024-06-20 01:48:00 2024-06-19 22:48:00,148 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-20 01:48:00 2024-06-19 22:48:00,148 INFO supervisord started with pid 1 2024-06-20 01:48:01 2024-06-19 22:48:01,151 INFO spawned: 'postgresql' with pid 20 2024-06-20 01:48:01 2024-06-19 22:48:01,152 INFO spawned: 'stellar-core' with pid 21 2024-06-20 01:48:01 2024-06-19 22:48:01,152 INFO reaped unknown pid 17 2024-06-20 01:48:02 2024-06-19 22:48:02,201 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 01:48:02 2024-06-19 22:48:02,201 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 01:48:03 2024-06-19 22:48:03,770 WARN received SIGTERM indicating exit request 2024-06-20 01:48:03 2024-06-19 22:48:03,770 INFO waiting for stellar-core, postgresql to die 2024-06-20 01:48:07 2024-06-19 22:48:07,323 INFO waiting for stellar-core, postgresql to die 2024-06-20 01:48:08 2024-06-19 22:48:08,732 INFO stopped: stellar-core (exit status 0) 2024-06-20 01:48:08 2024-06-19 22:48:08,751 INFO stopped: postgresql (exit status 0)

It is so confusing :)

[adnanoncevarlik]

After that, I treid to start container manually again (pressed Start button on Containers screen in the Docker Desktop) and it exited again, then after that I tried to Turn the Node Switch On in the PiNode App it ran and did not exited, now it seemed to be running status. I wonder when it will kill the "pi-consensus" container and delete it and create damn "pi-consensus-stub" container again. I guess after 3-4 hours it will be.

Here is the LOG's latest Runs,

2024-06-20 02:02:43 2024-06-20 02:02:43 Starting Stellar Quickstart 2024-06-20 02:02:43 2024-06-20 02:02:43 mode: ephemeral 2024-06-20 02:02:43 network: testnet (Pi Testnet) 2024-06-20 02:02:43 postgres: config directory exists, skipping copy 2024-06-20 02:02:43 supervisor: config directory exists, skipping copy 2024-06-20 02:02:43 stellar-core: config directory exists, skipping copy 2024-06-20 02:02:43 horizon: config directory exists, skipping copy 2024-06-20 02:02:43 postgres: already initialized 2024-06-20 02:02:43 chown-core: ok 2024-06-20 02:02:43 core: already initialized 2024-06-20 02:02:43 horizon: already initialized 2024-06-20 02:02:44 starting supervisor 2024-06-20 02:02:44 2024-06-19 23:02:44,096 CRIT Supervisor running as root (no user in config file) 2024-06-20 02:02:44 2024-06-19 23:02:44,102 INFO RPC interface 'supervisor' initialized 2024-06-20 02:02:44 2024-06-19 23:02:44,102 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-20 02:02:44 2024-06-19 23:02:44,102 INFO supervisord started with pid 1 2024-06-20 02:02:45 2024-06-19 23:02:45,104 INFO spawned: 'postgresql' with pid 20 2024-06-20 02:02:45 2024-06-19 23:02:45,105 INFO spawned: 'stellar-core' with pid 21 2024-06-20 02:02:45 2024-06-19 23:02:45,106 INFO reaped unknown pid 17 2024-06-20 02:02:45 2024-06-19 23:02:45,106 WARN received SIGTERM indicating exit request 2024-06-20 02:02:45 2024-06-19 23:02:45,106 INFO waiting for stellar-core, postgresql to die 2024-06-20 02:02:45 2024-06-19 23:02:45,133 INFO stopped: stellar-core (terminated by SIGTERM) 2024-06-20 02:02:45 2024-06-19 23:02:45,137 INFO reaped unknown pid 22 2024-06-20 02:02:45 2024-06-19 23:02:45,153 INFO stopped: postgresql (exit status 0) 2024-06-20 02:03:00 2024-06-20 02:03:00 Starting Stellar Quickstart 2024-06-20 02:03:00 2024-06-20 02:03:00 mode: ephemeral 2024-06-20 02:03:00 network: testnet (Pi Testnet) 2024-06-20 02:03:00 postgres: config directory exists, skipping copy 2024-06-20 02:03:00 supervisor: config directory exists, skipping copy 2024-06-20 02:03:00 stellar-core: config directory exists, skipping copy 2024-06-20 02:03:00 horizon: config directory exists, skipping copy 2024-06-20 02:03:00 postgres: already initialized 2024-06-20 02:03:00 chown-core: ok 2024-06-20 02:03:00 core: already initialized 2024-06-20 02:03:00 horizon: already initialized 2024-06-20 02:03:00 starting supervisor 2024-06-20 02:03:00 2024-06-19 23:03:00,790 CRIT Supervisor running as root (no user in config file) 2024-06-20 02:03:00 2024-06-19 23:03:00,795 INFO RPC interface 'supervisor' initialized 2024-06-20 02:03:00 2024-06-19 23:03:00,796 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-20 02:03:00 2024-06-19 23:03:00,796 INFO supervisord started with pid 1 2024-06-20 02:03:01 2024-06-19 23:03:01,798 INFO spawned: 'postgresql' with pid 34 2024-06-20 02:03:01 2024-06-19 23:03:01,799 INFO spawned: 'stellar-core' with pid 35 2024-06-20 02:03:01 2024-06-19 23:03:01,799 INFO reaped unknown pid 17 2024-06-20 02:03:03 2024-06-19 23:03:03,380 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 02:03:03 2024-06-19 23:03:03,380 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-20 02:03:07 2024-06-19 23:03:07,292 INFO spawned: 'horizon' with pid 92 2024-06-20 02:03:08 2024-06-19 23:03:08,636 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[adnanoncevarlik]

@mcass75 Here is the result of the CMD prompt, Microsoft Windows [Version 10.0.22631.3737] (c) Microsoft Corporation. Tüm hakları saklıdır.

C:\Users\adnan>docker exec -it pi-consensus stellar-core http-command info 2024-06-19T23:10:43.433 [default INFO] Config from stellar-core.cfg 2024-06-19T23:10:43.433 [default INFO] Using QUORUM_SET: { "t" : 2, "v" : [ "testnet1", "testnet2", "testnet3" ] }

Content-Length: 1310 Content-Type: application/json

2024-06-19T23:10:43.434 GAFME [default INFO] { "info" : { "build" : "stellar-core 15.2.0 (54b03f755ae5d5aa12a799c8f1ee4d87fc9d1a1d)", "history_failure_rate" : "0.0", "ledger" : { "age" : 1718838643, "baseFee" : 100, "baseReserve" : 100000000, "closeTime" : 0, "hash" : "44e30ce5d01c867867ad6f6c532f0697879ec171ec03739cfebc13e0d9183897", "maxTxSetSize" : 100, "num" : 1, "version" : 0 }, "network" : "Pi Testnet", "peers" : { "authenticated_count" : 8, "pending_count" : 18 }, "protocol_version" : 15, "quorum" : { "node" : "GAFME", "qset" : { "agree" : 3, "cost" : 45396, "delayed" : 0, "disagree" : 0, "fail_at" : 2, "hash" : "c51e25", "lag_ms" : 3, "ledger" : 16525215, "missing" : 0, "phase" : "EXTERNALIZE" }, "transitive" : { "critical" : null, "intersection" : true, "last_check_ledger" : 16525198, "node_count" : 4 } }, "startedOn" : "2024-06-19T23:03:01Z", "state" : "Joining SCP", "status" : [ "Waiting for trigger ledger: 16525216/16525249, ETA: 165s" ] } }

C:\Users\adnan>

I Cleaned all the directories, registry entries, files everything. Then re-installed all the applications and get new Password to LOGIN TO NODE App, but still same.

[adnanoncevarlik]

It is too late for Türkiye, here is the Last Screen shot, tomorrow i will be informed you for the last status,

[MingYanWu]

There are too many problems with the latest version of Whale. Before re-downloading Whale, you must first turn off the little red dot of the node, re-download the low-level Whale version, use an open router port for detection, and then turn on the little red dot to make it run out of error. , and then delete the wrong container. , and then follow the steps in my picture to set it up https://docs.docker.com/desktop/release-notes/ -> Whale web page Synchronization is completed, the computer needs to be restarted

[adnanoncevarlik]

@MingYanWu Thank you for your help,

I already installed Docker Desktop Older version 4.19.0 and I did what you said, now it is trying to sync. I also checked the port status twice and all ports are OPEN there is no problem.

Maybe few hours later it will be fall the same status of "pi-consensus-stub" :) I'm waiting to sync and I am praying.

[adnanoncevarlik]

The problem is that "pi-consensus" Container runs normally for 4-5 hours (trying to catch-up) and then suddenly it deletes itself and spins the "pi-consensus-stub" Container and after that it starts rambling and just gets stuck. I hope I was able to explain the problem.

[adnanoncevarlik]

@kokkalis Have you got any idea to solve that problem? Very interesting things are happening.

[adnanoncevarlik]

News Update, still running and there is no problem yet. I wish it will continue to run properly and sync with the current ledger.

[MingYanWu]

When it runs to the pi-consensus-stub container, stop deleting it first. The little red dot will detect it repeatedly, and then create a new container using the picture I put up.

[adnanoncevarlik]

Hi Guys,

Thank you for your advices, container still running for 2 days without any error. Thank you for your cooperation and help.

[DocTRM]

@MingYanWu Thanks for your comment referring to this thead , i couldnt download whale ver 4.19 but 4.24 as oldest version available , tried all above even disabling completely the firewall, still cant get open ports nor the PI node app to run correctly as stated earlier it starts ok with new boot but after syncing upto current block it disconnects some how and im back to zero, quiet annoying as this came with latest updates of whale and pi node app....

[ideabilisim]

Hi, Is your Internet Connection is Static IP? If not, it is not possible to run node correctly.

[DocTRM]

@ideabilisim Thanks yes my IP is static assigned my my ISP

[adnanoncevarlik]

Hi, Here is the Docker older versions from 4.0.0 to 4.22.1

https://gist.github.com/kupietools/2f9f085228d765da579f0f0702bec33c

I wish useful for you.

[DocTRM]

@adnanoncevarlik thanx bro I´ll try this i believe you had docker ver 4.19 installed right?. Otherwise i am running docker and pi node newest versions but just have to exit the pi-node app delete the damn stub container , restart pi-node and it syncs nicely again but only for max couple of hours as it seems like it stops only after some idle after one is in sync meaning local block i same as remote. I hope dev can soon fix this bug in pi node app

[adnanoncevarlik]

Yes I installed 4.19 and in the previous posts (june 19 posts) I wrote what I did. All cleaning process in my computer.

[DocTRM]

@adnanoncevarlik Hi thanks for your comment , I've done all of what you have mentioned in post 19th and experienced exactly same as you. Now I've even installed whale 4.19 still same consensus- stub /port tester vicious cycle. Only way of escaping is exit node-app then delete running container and restart node-app and it will run for a few hours. If one creates container as @MingYanWu describes that container runs without any other effect than just creating a loop of consensus goin on/off without syncing . It is definitely a glitch in the Node app that needs correction

[MingYanWu]

I agree with your point of view, but since I created a new container, the container damage has not occurred again. How the project side handles it is not something I can handle. I can only provide how I created a new container.node version 0.4.11, whale version I use 4.25.2

[michelferia]

Hi, I reinstall everything and it was fine yesterday but today I got this:

do you know why? thanks in advance!!!

[DocTRM]

I agree with your point of view, but since I created a new container, the container damage has not occurred again. How the project side handles it is not something I can handle. I can only provide how I created a new container.node version 0.4.11, whale version I use 4.25.2

@MingYanWu : well i have made it work finally with latest whale and latest pi node, but problem is you actually gave wrong information on running the pi node with port settings ! one shoud not touch the ports at all, rather delete the consensus stub, turn off the red nob, exit pi node app run the pi-node container in whale without any port assignment , restart th epi-node app then turn on the red button and a new correct container of consensus will start running smoothly. @adnanoncevarlik @michelferia

[MingYanWu]

@DocTRM I also closed the little red dot and resynchronized the blockchain like this before, but it didn't work. An error was displayed and the container couldn't run. It appeared like the title above. When I encounter this situation, should I stop there and not solve it? Or should I find a way that I think can run the container? If you don't agree with me, I accept it because I just successfully used the new container and let it run.

[DocTRM]

@MingYanWu Good for you but when attempting to run as you described actually tries to assign same ports for two containers which does give the error, once the Pi-node container is run without specific port assignment it runs fine and then so does the pi-consensus container one the node app is started both running without problems. At least until so far now through 17 hours without any problem.

[MingYanWu]

@DocTRM I published this article in early June. Maybe the project team didn't handle it well at the time, which caused me to stop after 4 to 8 hours. I couldn't access the computer at all while working until I closed and opened the little red dot again. The container kept going back and forth, so I changed the previous connection. When changing ports, I don't even use the port I originally created with the little red dot, but directly use the port I'm connected to now. Even now it's okay.

[adnanoncevarlik]

Hi Guys, Last night, my Node App went crazy. The Node problem occurs again. I did new fresh install again. Why NODE APP going crazy and why p-consensus-stub container appears?

[MingYanWu]

嗨，夥計們，昨晚，我的 Node 應用程式發瘋了。Node 問題再次出現。我再次進行了新的全新安裝。為什麼 NODE APP 會發瘋，為什麼會出現 p-consensus-stub 容器？

If there is an error container, please refer to the image above to rebuild a new container.

[adnanoncevarlik]

Thank You, I did it. Now it is running but there is no Incoming connections yet. I am waiting. Here is the screenshots.

[ndagijimanapazo]

it seems issue has been identified and fixed, nothing else just remove docker with its temp files and reinstall again, then signout in Pi and remove it, after reinstall with newest version the run pi node, it works perfectly in simple words, thanks