Chia full node status

Run a Chia node

Recently, Chia network become popular because of its new Proof of space consensus.

In this article, we will just show you, the steps to take to run a Chia node on your computer.

Home — Chia Network

We believe that cryptocurrency should be easier to use than cash, harder to lose, and nearly impossible to steal…

Before start, if you have time you can read more about plotting (mining) basics.

Chia plotting basics

First it is important to know that there are two very different parts of being a Chia farmer. There is creating the…

If you want more information about how to use your free space to earn money you can check below article:

Mining using your disks free space

This article lists and compares some method to monetize your computer disk free space.

Installation

The installation is very simple, you just have to follow the installation instructions of the project. However, remember you will need more than 3 00Gb of free space to run the simplest node ( you will certainly not earn a lot of money with it).

Chia-Network/chia-blockchain

To install the chia-blockchain, follow the instructions according to your operating system. After installing, follow…

Setup

After installation lunch the GUI.

Then, add a plot and setup it.

To run one node of 101.4GIB, you will need, more than 300GB of free space. If your disk is full, the plotting will stop; you are supposed to be able to continue plotting if you add more free space. But, in my case plotting never progress after the disk was full.

The plotting will take about one day.

When, plotting is finished, you can save the resulting plot to another disk, like a slower hard disk.

Источник

[BUG] full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id #3696

Comments

Djomla003 commented May 4, 2021

beeing spamed in the debug.log file of chia with following output:

Based on the GUI everything is synced and working.

Does this BUG impact the block wins / chia wins?

The text was updated successfully, but these errors were encountered:

temicus commented May 4, 2021

Hey I have similar error:
2021-05-04T09:44:04.055 full_node full_node_server : WARNING Cannot write to closing transport XX 2021-05-04T09:50:40.660 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXXX, status 3 error: Err.DOUBLE_SPEND

hexslav commented May 4, 2021

Hello, next similar one, started popping out for me today

2021-05-04T11:05:21.327 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXX, status 3 error: Err.MEMPOOL_NOT_INITIALIZED

Everything in GUI looks fine.
Cheers, have a good day!

ricki008 commented May 4, 2021

Somebody know the answer yet?? I’m having the same problem 🙁

LamichhaneKamal commented May 4, 2021

temicus commented May 5, 2021

still have it even after updating to 1.1.4

• this one now:
  UNKNOWN_UNSPENT and DOUBLE_SPEND

djdookie commented May 5, 2021 •

Same here, seeing this error in debug.log several times per minute. I think I get this error since v1.1.3 under Ubuntu.

SKYBILLS commented May 5, 2021

In Windows Gui also have same problems . Please Fixed it

iLexGit commented May 5, 2021

This is happening to me now that i have updated to 1.1.4, it didn’t happen before. IT HAPPENS EVERY TIME SOME OF MY BLOCKS PASS THE FILTER. EVERY. SINGLE. TIME.

zewort commented May 5, 2021

full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXXXXXXXXXX, status 3 error: Err.DOUBLE_SPEND

iLexGit commented May 5, 2021 •

Always «status error 3» followed by one of these two:

• UNKNOWN_UNSPENT
• DOUBLE_SPEND
• MEMPOOL_NOT_INITIALIZED

Also, to the dev that answers this, appart from saying this is going to be fixed or if it is a bug at all (maybe the 1.1.4 logging is more verbose). EXPLAIN WHY this happens or WHAT it is. If the community understands better how your network works and what casues the issues we will be here asking recurrent questions MUCH LESS. It is in everyone’s best interest. Just consider it.

Muffexx commented May 5, 2021 •

Sporadic Err.DOUBLE_SPEND might not be an issue.
Check #3773

Edit: I should have been more precise.

iLexGit commented May 5, 2021

Yeah mariano said this happens cause » Transactions are being resubmitted sometimes» but this is not sometimes. this is absolutely everytime I receive an uncompleted block . My log is absolutely full of lines like this. Also, why is this happening, how can this be solved and what has changed in 1.1.4 that makes this happen.

IDK but i feel like we should have a lot more information about how the network works, what it uses, etc

Muffexx commented May 5, 2021

I’m also having the same issue (Err.DOUBLE_SPEND) multiple times per minute.

hobbit6 commented May 5, 2021

I’m having this issue too, every few minutes I get Err.DOUBLE_SPEND

meaverick commented May 6, 2021 •

full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id ### status 3 error: Err.DOUBLE_SPEND
version 1.1.4
windows 10

Cheshyr commented May 6, 2021 •

Ubuntu 20.04. Same issue. Was not present on 1.1.2, but took over my logs in 1.1.4. I assume the 1.1.2 errors were a misconfigured timelord, but not sure what the new stuff is.

Источник

full_node chia.full_node.full_node: ERROR #2488

Comments

liya558 commented Apr 23, 2021

systemOS:CentOS Linux release 7.9.2009 (Core)
CPU:Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz
memory:128G

full_node chia.full_node.full_node has a lot of error logs, and The drawing task always stops automatically.

The error log is as follows
21:10:16.505 full_node full_node_server : WARNING Banning 116.207.17.221 for 600 seconds
21:10:16.506 full_node chia.full_node.full_node: ERROR Error with syncing: Traceback (most recent call last):
File «/home/chia/chia-blockchain/chia/full_node/full_node.py», line 604, in _sync
raise RuntimeError(f»Weight proof did not arrive in time from peer: «)
RuntimeError: Weight proof did not arrive in time from peer: 116.207.17.221

21:21:58.361 full_node chia.full_node.full_node: ERROR Error with syncing: Traceback (most recent call last):
File «/home/chia/chia-blockchain/chia/full_node/full_node.py», line 604, in _sync
raise RuntimeError(f»Weight proof did not arrive in time from peer: «)
RuntimeError: Weight proof did not arrive in time from peer: 74.135.4.11

22:30:30.135 full_node full_node_server : WARNING Cannot write to closing transport 93.74.42.123
22:37:36.780 full_node full_node_server : WARNING Cannot write to closing transport 207.189.245.240

The text was updated successfully, but these errors were encountered:

Источник

[BUG] Node status Not synced #705

Comments

krispipeleers commented Jan 18, 2021

Having this issue where note status remains Not synced. Height keeps going up, but node status is still saying Not synced.
Connection status = connected
Farm status = wait for synchronization

OS: Win10
node 12.13.0
Chia 0.1.20

Tried to uninstall, deleted the 2 folders, re-installed without success.

The text was updated successfully, but these errors were encountered:

krispipeleers commented Jan 18, 2021

In the meantime upgraded to Chia 0.1.21

krispipeleers commented Jan 18, 2021

Still the same problem after following the instructions on Reddit https://www.reddit.com/r/chia/comments/kz5lwp/chia_network_beta_21/

krispipeleers commented Jan 18, 2021

After another hour or 2 it is fully synced.

dorkmo commented Jan 18, 2021

It just slowly synced finally? im still having the same issue. on windows 21 and ubunutu 21 also

hoffmang9 commented Jan 18, 2021

Node has performance issues related to the handful of transactions stuck in the mempool plus the wallet being mostly broken. You can try chia stop wallet-only to help. We know what’s wrong, but it’s a long weekend. Beta 22 will be soon.

krispipeleers commented Jan 18, 2021

It just slowly synced finally? im still having the same issue. on windows 21 and ubunutu 21 also

Indeed after 2 hours (after downloading the database), it caught up and timestamp of block and status look good now.

dorkmo commented Jan 19, 2021

its funny, my node keeps adding blocks, but its doing it slower that they are being created. slowly become further and further out of sync.

krispipeleers commented Jan 19, 2021

its funny, my node keeps adding blocks, but its doing it slower that they are being created. slowly become further and further out of sync.

It worked fine yesterday, but indeed started to slow down this morning. I’m on block 31021 now. I saw Gene’s note that with beta 22 this should be resolved. So waiting.

dorkmo commented Jan 20, 2021

today i updated to beta 22 on ubunutu, sorta had the same issue. The node connected, then successfully synced with the network. It was synced for a few blocks, then the machine won a farming award. Then it slowly began falling behind from the network again. After a few hours of losing sync, the peak time is about 40 minutes behind the network.

krispipeleers commented Jan 20, 2021 •

Syncing is again stuck around height 32343 with beta 22. Reopening this bug.

dorkmo commented Jan 20, 2021

i restarted my system and am back in sync. seeing some unfinished blocks again. won a block again, still in sync. ill keep an eye on it.

dorkmo commented Jan 20, 2021

it ran a little longer that time, but im out of sync again.

krispipeleers commented Jan 21, 2021

I’m plotting so cannot restart 🙂

dorkmo commented Jan 21, 2021

i feel ya! i got a rasberrypi 400 desktop a few weeks ago. running ubuntu gui on there just for farming and node. running windows 10 on my gaming pc where ive been plotting on external drives. I just shut down the node .exe after the gui boots.

i restarted my node system again and im staying synced once again. seems to be running much longer now.

krispipeleers commented Jan 21, 2021

Got it synced again by restarting the app.

krispipeleers commented Jan 21, 2021

Sorry but stuck again after syncing for an hour. Let me know if you need anything to further analyze.

GBourb commented Jan 26, 2021 •

Same here. My system stop syncing at random time. Did reboot now i’m syncing again (131222/134705)
Connection status still connected.

mariano54 commented Jan 27, 2021

Can you try on beta23? There were some large improvements regarding syncing.

krispipeleers commented Jan 28, 2021

Beta 23 is got stuck multiple times today. Restarting the app solved the problem each time. Let me know if I can send you additional information to analyze if needed!

Erni commented Feb 16, 2021

Same here. I am with version 0.1.26:

And the Status shows as Not Synced :

I have tries to reload and restart the application but it remains like that. I will leave the application open for a few hours and check.

hoffmang9 commented Feb 16, 2021

The Beta 26 chain died a couple of days ago. Upgrade to beta 27 and things will be much better.

Erni commented Feb 16, 2021

thanks @hoffmang9 . I just upgraded to 0.1.27 and started Syncing from the beginning. Let´s see how it goes.

beykovskyb commented Feb 19, 2021

@Erni how did you restart syncing from the begining? is there a way to do it manually?

hoffmang9 commented Feb 19, 2021

You can delete your wallet database in

The Beta 27 chain is likely to be dead very shortly and everyone should upgrade to RC-2

coding-horror commented Mar 14, 2021

Per comments above, I

• closed the client
• downloaded latest client
• installed it

Now it is syncing, so that solution (basically, close, upgrade to latest, re-launch) seems to work!

hesen2006cn commented Apr 27, 2021

]$ chia show -s
Current Blockchain Status: Full Node syncing to block 194826
Currently synced to block: 12242
Current Blockchain Status: Not Synced. Peak height: 12242
Time: Sun Mar 21 2021 19:52:35 EDT Height: 12242

Estimated network space: 124.196 PiB
Current difficulty: 8
Current VDF sub_slot_iters: 112197632
Total iterations since the start of the blockchain: 39003237584

Height: | Hash:
12242 | e4f9b8859d1cd9cc530b864c5e70c6f3edcd2d99c85a8a8ad51cab22f9a633c6
12241 | 5a436455a8d14d978f3b2e98a8a442f6e394c997a16a51c6671a8394f79f8c5b
12240 | e78575fa4a373bb857d0b45717cefe60e43148900308e7137358acbe2b554118
12239 | fb0b779ff70a42d9e7f948ad49b7e622fa0eb24f470ea434031a2e1784af6ebc
12238 | 24f04f1ae90851302e1a4071c071eefe4a0f842988d71998dc4f5c6482517491
12237 | 4c196d69a954d90821cf1948b2bd72126d751c66126362bab76129ca1aaa6936
12236 | 65aa7dcd09fd5a047ee8add2b65a3a6e464960f2fc11c2e6b149f37ae1389774
12235 | edf0f478014c4629e30ac3e3418943baa6118fa6faffde8b4aa3b26a3e4b7f3a
12234 | 9f3cf54ab39dfaa04745754bde88c8308a0f4ca71fa470cc4c3a5ace0f4e2df0
12233 | beea424ee291f03270ce6e186da7e9557d9de3e41d2c41f459d5029ac1bc0017
(venv) [uchia@localhost

]$ chia farm summary

my system: centos7.9 chia-v1.1.2

totaldev commented Apr 28, 2021

$ chia version
1.1.2.dev41

$ chia show -s
Current Blockchain Status: Not Synced. Peak height: 199075
Time: Wed Apr 28 2021 18:45:35 MSK Height: 199075

Estimated network space: 968.155 PiB
Current difficulty: 56
Current VDF sub_slot_iters: 99614720
Total iterations since the start of the blockchain: 653378065998

Height: | Hash:
199075 | d5bb6d79cc2043acf77f81813fcde1008f437801728ad605ce05df0d883f043b
199074 | 968aa4c66b2a85c10605922d937be6da34c21d0eb6891e795646d07d8b44c231
199073 | 6e26a81e13c6ff54817f4850ec9bcd089938a293048cffe25224189a256f8a2b
199072 | 05566dddc784acdb7e51b20c2a4687dbc60384c6c80117bb9666031679413b98
199071 | 1f28630c139b4bcafc48576a9f862377d15a41b25ecb1bb27f850ef98b1a95c4
199070 | e7208563d5d95f88580bb830f317f853e7aed8132b9f1220e6329d1680442405
199069 | b2fdc683698723b6df73836c05dcf319c6ce37ce2442587182f7bbb4886a667b
199068 | 2faf73b6226d6294e28a68208a0851dd209c2555eaa0ea501a66c3474a8867f9
199067 | 835efc336f79a24b8f94829eb634c4cdbe44441ae1c39d9aa908fca7a6a39913
199066 | 3f9258d99b563022e2fec594a079698c18352196f5c5e2046020c1df06e6b065

Источник