Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.83k stars 2.02k forks source link

[BUG]1.1.5 WIN GUI crashes and other issues #4688

Closed russ-tolman closed 3 years ago

russ-tolman commented 3 years ago

Set out six plots last night at 10:15 pm. Awoke this morning to find Win chia GUI was closed. Must have crashed. Looked into the plotting logs. Looks like it stopped at 11:45.

Bug logs don't reveal much:

2021-05-11T23:54:58.160 harvester chia.harvester.harvester: WARNING Not farming any plots on this harvester. Check your configuration. 2021-05-11T23:55:01.188 harvester chia.plotting.plot_tools: WARNING Directory: I:\ does not exist. 2021-05-11T23:55:01.188 harvester chia.harvester.harvester: WARNING Not farming any plots on this harvester. Check your configuration. 2021-05-12T06:45:15.457 farmer chia.rpc.rpc_server : WARNING Cannot connect to daemon at ws://localhost:55400 2021-05-12T06:45:15.675 harvester chia.rpc.rpc_server : WARNING Cannot connect to daemon at ws://localhost:55400 2021-05-12T06:45:17.233 harvester chia.plotting.plot_tools: WARNING Directory: I:\ does not exist. 2021-05-12T06:45:17.235 harvester chia.harvester.harvester: WARNING Not farming any plots on this harvester. Check your configuration. 2021-05-12T06:45:17.450 farmer chia.rpc.rpc_server : WARNING Cannot connect to daemon at ws://localhost:55400

The machine was not online as it is used as a plotter only. Directory I:\ was not plugged in at the time as it was connected to my farmer machine.

Last night before I attempted to plot, I upgraded to 1.1.5. I had big troubles getting the wallet to sync. It does seem to sync at all unless machine is online, which I generally don't do as it is a plotting only machine and I don't know of anyway to turn off harvester, etc. on GUI. So I try to keep it offline.

russ-tolman commented 3 years ago

crashed again while plotting. Nothing in bug log that seems to indicate what the problem is, however there are a bunch of entries that make no sense at all as the machine was offline just plotting, so these don't make much sense to me:

2021-05-12T21:48:51.822 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id c0b4893032a29a184f9cb113892de2b37769f946d823c3bcbe2105242302cd37, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:51.922 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 1d23603dd8bae7cc20c0f4318327950fb5665fbc680d40340137a0adebd9267f, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:51.922 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 78c6909a96d26e93234cac946f5c4fa9b7661141b8036c69bacb4d7bf2da7b13, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:51.973 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id dfe34eacd1ddacc4c83119b4eeaa2665188215ecd70a143575e5404677588f9e, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:52.194 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 41ca72af345ab0abbdb08e95c9871e529219e1476e31a9d84e8d8f61487f35dc, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:52.214 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 64adae462ef473d341bafde8ba5a0c29b19aad24c037f032fadab9870f35d60c, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:52.214 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id fc2eeafed8fa4069955ca3a7dd0d59f29c4305f50e54c6eb393922f219568b26, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:48:52.225 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 410305722e8e8401dfea6c9352d3e6a84c78d2c6caac149cfce23bec08c114b2, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:25.272 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 776696e1df4f810d270b75b8cd0349ffe6dfbb410ce52ab0cb03bbc8e61292dd, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.610 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id ab1b1098edc57bea3bd5dc32fb95af0b5c4391c09d32551b03b76d703b0acada, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.610 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 7925e6e16e898524d4cbe44797f20188c2ac05ed132f716892a1c556a2c4de54, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.610 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 820ba3d6bc3293238b0d26c822e04263b192a1f7591320f998e1649a2185cca3, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.610 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id f53ef185548cbf4100851384208c7c94f1c5be1251d46ff20b2059d2b6cc41a3, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.610 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id fa2fad384f90ba3259593a33499115c36a758f60936d3d0af23bafb4976fc42c, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.626 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id ada3f548dd1e74707d8d5f15b8b30740e293a5c1e854df5e87a214a2abe011ce, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:28.969 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 727cc9c12182c297b2cfdc4d71de9e1d125c786d0520aadc4eeb02bfa150470c, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:29.000 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 65ac7f24000bb9bb5f9192f8d6cdb5269156bd2af69ac4cd55c5047de4b1f1c7, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:29.016 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 75175ac2228f5788363763323fe3a1d4db192e776b6121a8fa4a2a5f75a31104, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:29.016 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id e3b9003b4823474b85eaf4259c295599697be824d410c369e45946f2dded1223, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:29.032 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id c9387222b12b86fda30beb39b30cc7752f6a68f2daf3c63d5c0ee4eeb9374bb3, status 3 error: Err.DOUBLE_SPEND 2021-05-12T21:51:29.047 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id c7c61af24a42949a9a4c9ebf959b875b465d75b26e36c5eff545dbde0d843b9d, status 3 error: Err.DOUBLE_SPEND

vas101 commented 3 years ago

I'm having the same problem with the gui continuously shutting down after having upgraded to 1.1.5.i have reinstalled it about 5-6 tmes and the same issue occurs,i start plotting and next morning the chia app is closed. I upgraded to cure the wallet syncing issue which have now come back but with this issue on top aswell.its very frustrating

russ-tolman commented 3 years ago

For plotting 1.1.4, 1.1.5 are turds. Since I don't do anything but plot offline with my plotters, I am going to do some research in the release notes and go back to the version that plotted fast with no problems.

New EP: Russ Sings Fred: The Songs of Fred Neil

www.russtolmanmusic.com

Catch my radio show My Kinda Country, every Thursday, 2pm Pacific on GimmeCountry.com

On Thursday, May 13, 2021, 02:05:58 AM PDT, vas101 ***@***.***> wrote:  

I'm having the same problem with the gui continuously shutting down after having upgraded to 1.1.5.i have reinstalled it about 5-6 tmes and the same issue occurs,i start plotting and next morning the chia app is closed. I upgraded to cure the wallet syncing issue which have now come back but with this issue on top aswell.its very frustrating

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

vas101 commented 3 years ago

I may backtrack on app versions depending on the losses between v 1.1.5 and say 1.1.2

github-actions[bot] commented 3 years ago

This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.

github-actions[bot] commented 3 years ago

This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.