Consensus container: absent / creating

[ironkick75]

Good afternoon everyone. Pi Node 0.4.11 + Docker desktop 4.34.2 + Mac OS Monterey 12.7.6. My node hasn't been working for weeks either. I have the ports open, and in the diagnostics it tells me "Consensus container: absent / creating", but it never creates it. Some solution?.

[cruzerdk]

Did you solve this? I am also experiencing the same problem.

I am using mac os 15 Sequoia. Docker is using version 4.25.2. Before that, I used OS 14 Sonoma and the same problem occurs.

I think this problem has been happening for about 2 weeks, and I tried several Docker versions (4.34.2, 4.34.1, 4.30.0, 4.19.0), but in the end, none of the versions I used were able to create a consensus container. I'm currently using version 4.25.2, and I keep the node switch turned on.

I was using it well before the problem occurred, but I'm embarrassed that it suddenly doesn't work. I did a search and saw a few posts about other Macs experiencing the same symptoms.

Is the problem occurring on Mac?

[ironkick75]

I have not been able to solve the problem. I have also tried using different versions of Docker and reinstalling Pi Node, but it hasn't solved the problem. I don't know if the problem is only on Mac computers, or it also happens on Windows.

[RumoursGR]

I'm experiencing the same problem exactly. I thought it was a problem with my machine. Could someone kindly help us fix this issue?

[marchetb]

Same here, consensus container, keep going from creating to absent. Macos sequoia 15.0 and M2 Max, I use Orbstack for my docker containers.

[wlara]

Same issue here, running a mac node. My node was actually running ok, but I was not getting rewards for ~1 week, so I decided to delete all data and re-start. After that I got into this "absent/creating" status.

[RumoursGR]

If anyone has found a solution to this, please post it here. Thanks!

[Trebuin]

I'm having the same issue...also waiting on solutions. I'm on the Mac side of the house.

[quocduongpy]

I have found the solution to this issue. You will need to install an older version of Pi Node, such as Pi Network 0.4.7.

After adding Pi Network to the Applications folder, do not run it immediately.

First, you need to access: /Applications/Pi\ Network.app/Contents/Resources/app-update.yml and modify it as follows. The purpose is to disable the automatic update feature of Pi Network:

#provider: generic
#url: https://downloads.minepi.com/node-manifests
#updaterCacheDirName: pi-network-desktop-updater

Next, run Pi Network and go through the installation process as usual.

If you encounter a "Stuck loading" error, you can fix it by editing the user-preferences.json file. You can learn how to do this on YouTube or Google.

After the process of creating the pi-consensus container on Docker is successful, wait and see if the block creation process on the Pi Network application screen is running smoothly.

Then, you need to replace the Pi Network in the Applications folder with the latest version, which is 0.4.11, by copying the latest Pi Network version into the Applications folder and replacing the existing one.

Best of luck.

Note: You should only install Pi Network versions that are directly downloaded from the official provider minepi.com.

[cruzerdk]

I have found the solution to this issue. You will need to install an older version of Pi Node, such as Pi Network 0.4.7.

After adding Pi Network to the Applications folder, do not run it immediately.

First, you need to access: /Applications/Pi\ Network.app/Contents/Resources/app-update.yml and modify it as follows. The purpose is to disable the automatic update feature of Pi Network:

#provider: generic
#url: https://downloads.minepi.com/node-manifests
#updaterCacheDirName: pi-network-desktop-updater

Next, run Pi Network and go through the installation process as usual.

If you encounter a "Stuck loading" error, you can fix it by editing the user-preferences.json file. You can learn how to do this on YouTube or Google.

After the process of creating the pi-consensus container on Docker is successful, wait and see if the block creation process on the Pi Network application screen is running smoothly.

Then, you need to replace the Pi Network in the Applications folder with the latest version, which is 0.4.11, by copying the latest Pi Network version into the Applications folder and replacing the existing one.

Best of luck.

Note: You should only install Pi Network versions that are directly downloaded from the official provider minepi.com.

Thank you for providing the solution. But I don't know where to get version 0.4.7. I searched and tried up to version 0.4.9, but it said it was an old version and after a certain period of time, it was automatically updated to 0.4.11 and did not work.

Where can I get Pi Network version 0.4.7?

[quocduongpy]

@cruzerdk If you are using version 0.4.9, you can still apply the above method. First, you need to disable the auto-update feature, then follow the next steps as mentioned above.

[cruzerdk]

@cruzerdk If you are using version 0.4.9, you can still apply the above method. First, you need to disable the auto-update feature, then follow the next steps as mentioned above.

I didn't know where to stop the app from automatically updating, so I just ignored it and proceeded. The pi-consensus container is initially created, but disappears after a while, and the update-pi-node-app container is created, but no progress is made.

It's not easy.

[quocduongpy]

@cruzerdk You need to read my guide carefully. It already includes instructions for disabling the auto-update feature as follows:

You need to edit the file app-update.yml at this location: /Applications/Pi\ Network.app/Contents/Resources/app-update.yml.

Disable all the data inside it by adding a # at the beginning of each line, like this:

#provider: generic
#url: https://downloads.minepi.com/node-manifests
#updaterCacheDirName: pi-network-desktop-updater

Good luck

[cruzerdk]

@cruzerdk You need to read my guide carefully. It already includes instructions for disabling the auto-update feature as follows:

You need to edit the file app-update.yml at this location: /Applications/Pi\ Network.app/Contents/Resources/app-update.yml.

Disable all the data inside it by adding a # at the beginning of each line, like this:

#provider: generic
#url: https://downloads.minepi.com/node-manifests
#updaterCacheDirName: pi-network-desktop-updater

Good luck

I did as you suggested, but it didn't work. I'll keep trying. thank you!!

[RumoursGR]

@cruzerdk please provide a link with the 0.4.9 pi node release. I can't find it.

[cruzerdk]

@cruzerdk please provide a link with the 0.4.9 pi node release. I can't find it.

https://downloads.minepi.com/Pi%20Network-0.4.9-universal.dmg

Here is the link. I'm trying to do the above, but it's not working for me. Please let me know if it goes well.

[RumoursGR]

It doesn't work for me either.

[marchetb]

Its working for me. Steps to follow :

• Quit Pi network app
• Download pi network version 0.4.9 from https://github.com/pi-node/instructions/issues/386#issuecomment-2390557059
• Copy (as usual) Pi network to App folder
• Disable your network
• Launch Pi network (this is for the image verification of macos)
• Quit Pi network
• Launch terminal
• vi /Applications/Pi\ Network.app/Contents/Resources/app-update.yml (or nano)
• Add a # on each line, save and quit (:wq)
• Enable your network
• Launch Pi network
• It works 😊

[Trebuin]

That worked for me... for those who might be confused on how to save (these are Mac instructions for terminal), once you finish editing, you select ":" which puts you down at the bottom, then input w & q live marchetb posted, then hit enter.

[Trebuin]

Now I'm stuck between "joining SCP" & "Catching up"

I figured out in full & finally am syncing correctly. After the above instructions, I had the error above with no updates, but found this: https://github.com/pi-node/instructions/issues/367#issuecomment-2179652773 There's a post in there that has us create a replacement container due to a corrupt container. This process also works for this error. When you're on 4.11 & create the container, it no longer cycles between absent / creating & it won't just stall. I still have the joining SCP & Catching up, but on the main node switch page, it is showing my progress to sync. It also doesn't crash & attempt to force updating after 30-45 mins as I saw when sitting on 4.09.

It got to 95%, stopped, then deleted itself...recreated it again to see if try 2 will work.

[cruzerdk]

@marchetb @Trebuin thank you. By following the order you mentioned, the pi-consensus container was created, and it seems that the container is still maintained and has not disappeared.

It is best to disconnect from the Internet once during the process. I think that's the point.

I can't rest assured until the consensus status changes, so I'll keep watching.

[RumoursGR]

Hi all,

For me it works for a while, then it updates and stops working again.

So, after I put a # to all three lines in the yml file, do I have to do anything more? I'm a newbie - excuse my ignorance - and I'm using the nano command instead of vi; aren't those three lines in the yml file supposed to change colour, or something, to show me that the app won't run the code? 🫠

[wlara]

Its working for me. Steps to follow :

• Quit Pi network app
• Download pi network version 0.4.9 from Consensus container: absent / creating #386 (comment)
• Copy (as usual) Pi network to App folder
• Disable your network
• Launch Pi network (this is for the image verification of macos)
• Quit Pi network
• Launch terminal
• vi /Applications/Pi\ Network.app/Contents/Resources/app-update.yml (or nano)
• Add a # on each line, save and quit (:wq)
• Enable your network
• Launch Pi network
• It works 😊

Worked like a charm!!! Thanks for the steps.

[RumoursGR]

of

It worked for me after much effort, only when I decided to probe ChatGPT that told me to leave the app-update.yml file empty instead. Maybe that's a similar to the original option. Thanks! 😄

[Trebuin]

@marchetb @Trebuin thank you. By following the order you mentioned, the pi-consensus container was created, and it seems that the container is still maintained and has not disappeared.

It is best to disconnect from the Internet once during the process. I think that's the point.

I can't rest assured until the consensus status changes, so I'll keep watching.

which version are you running? I still haven't pulled off 100% before it deletes, no matter what I use.

[cruzerdk]

@Trebuin I used version 0.4.9. At first, it kept getting deleted, so I kept trying and eventually reached the synced state, but it was deleted automatically after a while.

I think it's just a node server issue. I hope them handle it quickly.

I wonder if others are doing well.

[Trebuin]

Ok, finally got fully sync'd...I figured out how to avoid the container being deleted: after you launch Pi on 4.09, you'll have a pinetwork/pi-node-docker when you follow the instructions once you've updated to 4.11, you manually create the pi node per 386 above: Go into Docker Desktop Select Images Select the ellipsis (three dots) Select inspect Select Run Expand Optional Settings Container name: pi-consensus Host port 1: 31402 Host port 2: 31403 Host port 3: 31401 run it at this point, you should see it joining SCL/catching up on the troubleshooting page state section On the main page, you'll see the progress with the buckets going on. I waited until the first bit was done & then closed Pi Network but kept Docker desktop running. After about 3 hours, I launched Pi Network & it showed that it had fully sync'd.

I'll see tomorrow if it will stay online.

[cruzerdk]

Even after 24 hours by using a method similar to the method above, the pi-consensus container is still well maintained in the Synced state. 😮‍💨

PiNode, Docker, and Mac OS have all been updated to the latest. I saw a comment on another post saying that Pi Node is not compatible with the latest version of Docker. But from what I feel, runcat's cat runs slower and seems to be better. (I think it will be fine even if you don't necessarily have to match the version to mine.)

I was a little worried because the node didn't work for almost a month, but it seems like the issue has been resolved well thanks to the kind explanations provided by the people here.

Thank you so much. 🙇‍♂️

I believe that those who are still doing it will do well.

[MelSG-sports0]

Good afternoon everyone. Pi Node 0.4.11 + Docker desktop 4.34.2 + Mac OS Monterey 12.7.6. My node hasn't been working for weeks either. I have the ports open, and in the diagnostics it tells me "Consensus container: absent / creating", but it never creates it. Some solution?.

I've found a solution to my month long issue about this subject.

The following steps which I did just today:

1. Edited the "users-preferences.json" under users/application support/Pi Network.
2. Restarted my Mac mini os 12.7.6
3. See my uploaded files for your reference.

[MelSG-sports0]

I've upgraded Pi node to 0.4.11 just now and used the image, pinetwork/pi-node-docker:latest to create pi-consensus container. Attached are the screenshots for your reference.

[RumoursGR]

I've upgraded Pi node to 0.4.11 just now and used the image, pinetwork/pi-node-docker:latest to create pi-consensus container.

Attached are the screenshots for your reference.

This is the only solution of the aforementioned that worked for me. Thank you, mate!

[marchetb]

Good afternoon everyone. Pi Node 0.4.11 + Docker desktop 4.34.2 + Mac OS Monterey 12.7.6. My node hasn't been working for weeks either. I have the ports open, and in the diagnostics it tells me "Consensus container: absent / creating", but it never creates it. Some solution?.

I've found a solution to my month long issue about this subject.

The following steps which I did just today:

1. Edited the "users-preferences.json" under users/application support/Pi Network.
2. Restarted my Mac mini os 12.7.6
3. See my uploaded files for your reference.

That's strange because your users-preferences.json is not valid at the end of the file stellarSeretSeed:"NODE_PRIVATE_KEY"dockerImage", this should be : stellarSecretSeed:"NODE_PRIVATE_KEY" (Secret with a C 😊 )

[kashk94]

So, the application script searches for the container name "pi-consensus" among the docker containers running - if it can't find it, the creating/absent loop will kick in. To resolve this, turn the red switch off in the Pi Node UI, create a container from the pinetwork/pi-node-docker:latest image named pi-consensus (under optional settings -> container name) and after the container is running, restart the red switch in the Pi Node UI

[wlara]

It's been 3 days since I fixed my node following the instructions here. Everything is sync'd up; however, I'm still getting 0 Node Bonus. Anyone else having the same issue?

[marchetb]

It's been 3 days since I fixed my node following the instructions here. Everything is sync'd up; however, I'm still getting 0 Node Bonus. Anyone else having the same issue?

Yes same issue, don't know if it's normal.

[RumoursGR]

I read that it can take up to 2 weeks for the bonus to appear in the app.

Cheers!

[Trebuin]

Mine has been fixed since this weekend & I’m at 0 bonus & 4% uptime…it updated on Saturday & hasn’t changed since. I don’t know how often it updates On Oct 8, 2024 at 12:17 AM -0500, Walter Lara @.***>, wrote:

It's been 3 days since I fixed my node following the instructions here. Everything is sync'd up. However, no earnings. Anyone else having the same issue? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[ironkick75]

Thank you all very much for your contributions, I have also managed to solve the problem with the instructions you have indicated.

[MelSG-sports0]

It's been 3 days since I fixed my node following the instructions here. Everything is sync'd up; however, I'm still getting 0 Node Bonus. Anyone else having the same issue?

11 hours ago my pi-consensus container has became stable. I hope this will continue for the next 24 hours and will expect node bonus restoration. The same scenario I've experienced for more than a month with unstable Pi node system of course zero bonus. Hence, I've followed the instructions here, then applied my users-preference.json edited file, it works on and off. However now my container was running well, in synced state with latest block, and supporting other nodes. I'm running Mac mini with Monterey os 12.7.6 with 1gb dedicated in 5G network.

[MelSG-sports0]

It's been 3 days since I fixed my node following the instructions here. Everything is sync'd up; however, I'm still getting 0 Node Bonus. Anyone else having the same issue?

11 hours ago my pi-consensus container has became stable. I hope this will continue for the next 24 hours and will expect node bonus restoration. The same scenario I've experienced for more than a month with unstable Pi node system of course zero bonus. Hence, I've followed the instructions here, then applied my users-preference.json edited file, it works on and off. However now my container was running well, in synced state with latest block, and supporting other nodes. I'm running Mac mini with Monterey os 12.7.6 with 1gb dedicated in 5G network.

![Uploading Screenshot 2024-10-12 at 9.45.24 AM.png…]()

[wlara]

Has anyone gotten any bonus yet after getting etge node synced by following the instructions here? No luck for me after 10 days

[RumoursGR]

No bonus for me either after 9-10 days. 😅