1.6.1 fee estimator error

Chia Farming & Harvesting
1 
2022-11-05T20:41:51.744 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-05T20:41:51.746 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-05T20:41:51.746 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-05T20:41:51.746 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-05T20:42:08.794 full_node chia.full_node.full_node: WARNING  Time for header validate: 0.050562381744384766
2022-11-05T20:42:09.911 full_node chia.full_node.full_node: WARNING  Time for header validate: 0.05001235008239746
2022-11-05T20:42:19.990 full_node chia.full_node.full_node: WARNING  Time for header validate: 0.04354739189147949
2022-11-05T20:42:31.170 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-05T20:42:31.178 full_node chia.full_node.mempool  : WARNING  Fee estimator error

what about fee?

2

it is a new feature added in 1.6.1. New features are always kind of dangerous and prone to bugs. So I rather would wait at least 15 days before going to a new release or take the stable release one before.

I suggest submitting a bug report on github:

if you are not a tech-savy person, I guess the bug will be recognized by other peeps and resolved in one of the upcoming releases

3

more stuff

2022-11-06T03:38:18.724 full_node chia.full_node.mempool_manager: WARNING  Conflicting pool items: 1
4
1 Like
5

should i rollback to 1.5.1?

6

here is more:

2022-11-06T10:32:12.855 wallet chia.wallet.wallet_state_manager: ERROR    Error adding state... Was not able to obtain solution None
Traceback (most recent call last):
  File "chia\wallet\wallet_state_manager.py", line 1196, in new_coin_state
  File "chia\wallet\wallet_node.py", line 1609, in fetch_puzzle_solution
chia.wallet.util.wallet_sync_utils.PeerRequestException: Was not able to obtain solution None
2022-11-06T10:32:12.871 wallet chia.wallet.wallet_state_manager: ERROR    Error adding state... Was not able to obtain solution None
Traceback (most recent call last):
  File "chia\wallet\wallet_state_manager.py", line 1196, in new_coin_state
  File "chia\wallet\wallet_node.py", line 1609, in fetch_puzzle_solution
chia.wallet.util.wallet_sync_utils.PeerRequestException: Was not able to obtain solution None
2022-11-06T10:32:12.871 wallet chia.wallet.wallet_state_manager: ERROR    Error adding state... Was not able to obtain solution None
Traceback (most recent call last):
  File "chia\wallet\wallet_state_manager.py", line 1196, in new_coin_state
  File "chia\wallet\wallet_node.py", line 1609, in fetch_puzzle_solution
chia.wallet.util.wallet_sync_utils.PeerRequestException: Was not able to obtain solution None
2022-11-06T10:32:13.657 full_node chia.full_node.full_node: WARNING  Time for header validate: 0.031255245208740234
2022-11-06T10:32:23.901 full_node chia.full_node.mempool_manager: WARNING  Conflicting pool items: 1
2022-11-06T10:32:23.901 full_node chia.full_node.mempool  : WARNING  Fee estimator error
2022-11-06T10:32:23.901 full_node chia.full_node.mempool  : WARNING  Fee estimator error
7

According to the 1.6.1 release notes you can safely ignore the fee estimation errors.
Are you having issues of some kind?

1 Like
8

read carefully the rest of warnings AND errors

9

Pls answer

Because if so, what?
If not, no problem.

Alot of them ( your log warnings / errors ) are warnings / errors that just arent important and pretty commonly seen in logs.

10

Yea ,what Bones said :joy: :joy: :joy:

11

Having an issue potentially of course is my concern. Why? By the way i was aware of knowing this Is actually AAA forum, sorry for briging discussion of the new version of blockchain software… DUUH …

12

you know what you are right, nothing to warry about just receiving new coins related part of code.

2022-11-07_19-12-59 - chia error adding state
2022-11-07_19-12-59 - chia error adding state1285×522 32.6 KB

2 Likes
13

Hi Ivan,
Feel free to ask for support on Chia Keybase support channel, if you think you have a potential issue, asking never hurts.
You can try to post an issue on Github, but IMHO they are more responsive on Keybase.

1 Like
14

They were all old errors/warnings that have been about for many releases except the fee one, which you were told to ignore.

15

No this is just not true.

16

Your wrong. Try reading more.

Just because they werent in your logs doesnt mean theyre not commonly mentioned as occurring

17

say no more :laughing: :laughing: :laughing: this is perfect software!

18

Clearly not, those errors have been around ages as ive said.
No one here can fix them.
No point moaning here.

19

where here? how are you to decide who can moan and where?

20

Im saying its pointlless, the devs arent here to listen are they.