May 26, 20215 yr On 5/19/2021 at 4:17 PM, unririd said: I've found and tested this script and it solves the sync issue on Windows quite well. Can anyone recommend how to run it within docker? ### HELLO THIS IS SCRIPT TO AUTOMATE SYNCHRONIZE WITH NODES IN CHIA ### ### NODES ARE DOWNLOADED FROM https://chia.keva.app/ & chia.powerlayout.com (PUBILC NODES) STOP USING THE ABOVE QUOTED POWERSHELL SCRIPT IMMEDIATELLY! IT HAS A MALICIOUS BACKDOOR! Stop using the one mentioned in this quote and check over any similar powershell scripts you have used. Many have already been affected with stolen XCH and even the wallet mnemonic passphrase. The backdoor could be used to run any commands, so your windows OS could be compromised if you gave the powershell script admin privileges. Again, look over your scripts people if you used anything like this powershell script to fix earlier syncing issues!! source: https://www.reddit.com/r/chia/comments/nl94th/psa_potential_security_breach_for_end_users_who/ Edited May 27, 20215 yr by jonathanm Removed possible malicious code.
May 26, 20215 yr 1 hour ago, zer0ed said: STOP USING THE ABOVE QUOTED POWERSHELL SCRIPT IMMEDIATELLY! IT HAS A MALICIOUS BACKDOOR! Stop using the one mentioned in this quote and check over any similar powershell scripts you have used. Many have already been affected with stolen XCH and even the wallet mnemonic passphrase. The backdoor could be used to run any commands, so your windows OS could be compromised if you gave the powershell script admin privileges. Again, look over your scripts people if you used anything like this powershell script to fix earlier syncing issues!! source: https://www.reddit.com/r/chia/comments/nl94th/psa_potential_security_breach_for_end_users_who/ Perhaps you should remove the bulk of the script from your quote?
May 26, 20215 yr 7 hours ago, HATEME said: I got all the way to step Venv: "..activate" Umm Wut? Pardon my noobness, but what command do I enter? Tried every combination of ../activate, venv:../activate, activate venv, venv../activate. Even tried to google what a venv was... Everything just comes up as not found, not found, not found. The processes are running, but that's about it so far. You tried ALMOST everything ! The rigth command is : ".(dash) (space).(dash)/activate", you can also type "source ./activate", it's the same.
May 26, 20215 yr 28 minutes ago, Gnomuz said: You tried ALMOST everything ! The rigth command is : ".(dash) (space).(dash)/activate", you can also type "source ./activate", it's the same. # source ./activate sh: 2: source: not found # ./ .//activate sh: 3: ./: Permission denied # source./activate sh: 4: source./activate: not found # /activate sh: 5: /activate: not found # chia ./activate sh: 6: chia: not found # chia_harvester ./activate sh: 7: chia_harvester: not found # :./ .//activate sh: 8: :./: not found # qepkvcnmSDLJNKVC sh: 9: qepkvcnmSDLJNKVC: not found I feel like total boomer right now....
May 26, 20215 yr 8 minutes ago, HATEME said: # source ./activate sh: 2: source: not found # ./ .//activate sh: 3: ./: Permission denied # source./activate sh: 4: source./activate: not found # /activate sh: 5: /activate: not found # chia ./activate sh: 6: chia: not found # chia_harvester ./activate sh: 7: chia_harvester: not found # :./ .//activate sh: 8: :./: not found # qepkvcnmSDLJNKVC sh: 9: qepkvcnmSDLJNKVC: not found I feel like total boomer right now.... You have to be in the chia-blockchain directory, which happens to be a root directory in this container, for all that to work : cd /chia-blockchain source ./activate Here's the result in my container ; root@57ad7c0830ad:/chia-blockchain# cd /chia-blockchain root@57ad7c0830ad:/chia-blockchain# source ./activate (venv) root@57ad7c0830ad:/chia-blockchain# chia version 1.1.7.dev0 (venv) root@57ad7c0830ad:/chia-blockchain# Hey, btw, these commands must be entered in the container console, NOT in the unRAID terminal ! Edited May 26, 20215 yr by Gnomuz
May 26, 20215 yr 5 minutes ago, Gnomuz said: You have to be in the chia-blockchain directory, which happens to be a root directory in this container, for all that to work : cd /chia-blockchain source ./activate Here's the result in my container ; root@57ad7c0830ad:/chia-blockchain# cd /chia-blockchain root@57ad7c0830ad:/chia-blockchain# source ./activate (venv) root@57ad7c0830ad:/chia-blockchain# chia version 1.1.7.dev0 (venv) root@57ad7c0830ad:/chia-blockchain# Hey, btw, these commands must be entered in the container console, NOT in the unRAID terminal ! I'm in the container console, I tried to cd to root directory # cd /chia-blockchain # source ./activate sh: 2: source: not found
May 26, 20215 yr I can't see then, but it's strange that your prompt is "#", like in unRAID terminal, where mine is "root@57ad7c0830ad:/chia-blockchain#" in the container console as you can see. Sorry, I can't help further, it must be something obvious, but it's a bit late here !
May 26, 20215 yr Just now, Gnomuz said: I can't see then, but it's strange that your prompt is "#", like in unRAID terminal, where mine is "root@57ad7c0830ad:/chia-blockchain#" in the container console as you can see. Sorry, I can't help further, it must be something obvious, but it's a bit late here ! Thanks for trying, I'll keep poking around to see what my problem is
May 26, 20215 yr Anyone found a way to map a new destination drive while the container / plotter is running? My USB drive is full and I have 6 plots going... I hope I don't have to stop progress 🤓
May 27, 20215 yr 8 hours ago, zer0ed said: STOP USING THE ABOVE QUOTED POWERSHELL SCRIPT IMMEDIATELLY! IT HAS A MALICIOUS BACKDOOR! Stop using the one mentioned in this quote and check over any similar powershell scripts you have used. Many have already been affected with stolen XCH and even the wallet mnemonic passphrase. The backdoor could be used to run any commands, so your windows OS could be compromised if you gave the powershell script admin privileges. Again, look over your scripts people if you used anything like this powershell script to fix earlier syncing issues!! source: https://www.reddit.com/r/chia/comments/nl94th/psa_potential_security_breach_for_end_users_who/ I would also note even if you had no XCH taken, that PS script likely got access to your private keys which means future earning could be stolen.
May 27, 20215 yr 11 hours ago, adminmat said: Anyone found a way to map a new destination drive while the container / plotter is running? My USB drive is full and I have 6 plots going... I hope I don't have to stop progress 🤓 I don't see any solution to change dynamically the final destination directory for a running plotting process. But if the final copy fails, due to destination drive full for instance, the process doesn't delete the final file in your temp directory, so you can just copy it manually to a destination with free space, and delete it from your temp directory once done.
May 27, 20215 yr Many thanks for that nice docker, i am running this one as harvester only. What is the best way to integrate the chia satellite ? https://github.com/felixbrucker/chia-dashboard-satellite
May 27, 20215 yr At this point if I have the RAM available, it would appear that running chia in a VM instead of docker is the better way to go, Yes? Edited May 27, 20215 yr by Ystebad
May 28, 20215 yr On 5/26/2021 at 6:14 PM, zer0ed said: STOP USING THE ABOVE QUOTED POWERSHELL SCRIPT IMMEDIATELLY! IT HAS A MALICIOUS BACKDOOR! Stop using the one mentioned in this quote and check over any similar powershell scripts you have used. Many have already been affected with stolen XCH and even the wallet mnemonic passphrase. The backdoor could be used to run any commands, so your windows OS could be compromised if you gave the powershell script admin privileges. Again, look over your scripts people if you used anything like this powershell script to fix earlier syncing issues!! source: https://www.reddit.com/r/chia/comments/nl94th/psa_potential_security_breach_for_end_users_who/ Thanks for noticing this, I feel bad for (unknowingly) endangering others... Lesson learned.
May 28, 20215 yr On 5/26/2021 at 11:17 PM, HATEME said: Thanks for trying, I'll keep poking around to see what my problem is At least in my case you don't need to use activate at all in this docker, if you want to run chia command try typing in DOCKER TERMINAL (the one which you choose after clicking chia icon in apps): venv/bin/chia <command> venv/bin/chia stop -d all Edited May 28, 20215 yr by unririd
May 28, 20215 yr So nobody answered my VM question - I ended up installing the docker and running now. However I see that folks say you can open another terminal window and run in parallel. If I try to open another terminal window from the "console" at the docker containers menu it says "connection closed." How can I open and run concurrent sessions?
May 28, 20215 yr 2 hours ago, Ystebad said: So nobody answered my VM question - I ended up installing the docker and running now. However I see that folks say you can open another terminal window and run in parallel. If I try to open another terminal window from the "console" at the docker containers menu it says "connection closed." How can I open and run concurrent sessions? Hi! You can use an SSH terminal like MobaXterm to SSH into the Unraid server as root, opening multiple sessions on different tabs. Then just 'docker exec -it chia bash' to get into the Chia container. That said, perhaps you would find a WebUI with plot manager a better fit. If so, check out my project: Machinaris.
May 28, 20215 yr 2 hours ago, Ystebad said: So nobody answered my VM question - I ended up installing the docker and running now. However I see that folks say you can open another terminal window and run in parallel. If I try to open another terminal window from the "console" at the docker containers menu it says "connection closed." How can I open and run concurrent sessions? Something doesn't sound right. Can you post a screenshot of where it says connection closed?
May 29, 20215 yr If I change the config.yaml file and adjust the log_level to INFO, shouldn't it generate that log in chia/mainnet/log/debug.log? I've confirmed the change and restarted the docker, but still nothing I'm trying to use chiaharvestgraph in the docker in order to make sure that it is working properly and the times are good: https://github.com/stolk/chiaharvestgraph Are you guys telling your disks to NEVER spin down that you use to store plots on? I would imagine this would be VERY IMPORTANT as it can take a bit of time to spin up a disk. I created a share and specified which disks I want that share to use in order to store plots. Basically, I want to make sure that everything is functioning efficiently in regards to connections and time to check plots when necessary.
May 29, 20215 yr 4 hours ago, live4soccer7 said: If I change the config.yaml file and adjust the log_level to INFO, shouldn't it generate that log in chia/mainnet/log/debug.log? I've confirmed the change and restarted the docker, but still nothing Make sure in your config file you have STDOUT set to true and check /mnt/user/appdata/chia/logs/plotting I don't use chiaharvestgraph My disks don't spin down. Balls are always green
May 29, 20215 yr Is anyone else having issues plotting from the windows GUI? I've got the Docker running as harvester and my full node on my windows desktop, with a share on the array for completed plots and a separate share on only the cache drive for building plots. Triple checked all the ports and uPNP and logs have no errors or warnings, just a ton of info logs. Everything works as advertised and running smoothly except when plotting from the windows GUI. It's a 50/50 shot if a plot will finish or not, and when it fails it's random, sometimes as early as 10% sometimes as late as 90%. Every time a plot fails it's always "Only read 0 of 262143 error 1" Which typically means no free space or the drive went to sleep, but my 1TB cache drive is never more than 60% full and Unraid doesn't spin down the cache, so I can't figure out what's going on. I can still copy files to and from the share, and immediately start plotting to the same share again after deleting the failed plot temp files. I'm really stumped on this, any incite as to what I could try or info at all would be very appreciated, thanks!
May 29, 20215 yr 5 hours ago, adminmat said: Make sure in your config file you have STDOUT set to true and check /mnt/user/appdata/chia/logs/plotting I don't use chiaharvestgraph My disks don't spin down. Balls are always green No matter what I do the changes always revert back to warning and false. I'll change them, save it, load it and check and it'll stick but after a restart i'll load again and they're back to warning and false. Just curious, have you checked your log file. I get things like this that seem like this may not be a good setup for chia: 2021-05-28T21:03:53.497 harvester chia.harvester.harvester: WARNING Looking up qualities on /plots/plot-k32-2021-05-28-04-31-5bf78696718b97d9e9d0495d3812a4fe81d92b96b68024657e5184e2292dfa42.plot took: 13.229008436203003. This should be below 5 seconds to minimize risk of losing rewards. 2021-05-28T21:03:53.511 harvester chia.harvester.harvester: WARNING Looking up qualities on /plots/plot-k32-2021-05-20-22-21-783e1fb28377e91fc5f40e4786ffc7596af172441794fb06874a632df63f0af0.plot took: 13.243207454681396. This should be below 5 seconds to minimize risk of losing rewards. 2021-05-28T21:23:55.414 harvester chia.harvester.harvester: WARNING Looking up qualities on /plots/plot-k32-2021-05-27-23-08-fdc5d3100c1118ebe90a9d7c4a206679252a7ce45cf5ca56575596a0e737dab4.plot took: 13.600364923477173. This should be below 5 seconds to minimize risk of losing rewards. 2021-05-28T21:23:55.444 harvester chia.harvester.harvester: WARNING Looking up qualities on /plots/plot-k32-2021-05-26-14-07-fcc2295c3f7b9b9c02ec5ef2c3d7f73c630ccd63d1798364c0e9dfd7da2c283e.plot took: 13.630274295806885. This should be below 5 seconds to minimize risk of losing rewards. I also see a lot of these: 2021-05-28T21:43:25.317 full_node full_node_server : WARNING [Errno 104] Connection reset by peer 175.21.61.94 2021-05-28T22:14:18.864 full_node full_node_server : WARNING Banning 188.113.237.38 for 10 seconds 2021-05-28T22:14:18.872 full_node full_node_server : WARNING Invalid handshake with peer. Maybe the peer is running old software. 2021-05-28T23:28:26.751 full_node full_node_server : WARNING [Errno 32] Broken pipe 183.28.6.115 2021-05-28T23:36:53.284 full_node full_node_server : WARNING [Errno 32] Broken pipe 156.216.184.183 2021-05-28T23:48:47.946 full_node full_node_server : WARNING Banning 221.222.58.212 for 10 seconds 2021-05-28T23:48:47.958 full_node full_node_server : WARNING Invalid handshake with peer. Maybe the peer is running old software. 2021-05-29T00:22:31.852 full_node full_node_server : WARNING [Errno 32] Broken pipe 183.28.6.115 2021-05-29T00:22:53.453 full_node full_node_server : WARNING [Errno 32] Broken pipe 156.216.184.183 2021-05-29T00:23:42.418 full_node full_node_server : WARNING [Errno 32] Broken pipe 27.224.184.153 2021-05-29T00:56:57.768 full_node full_node_server : ERROR Exception: Failed to fetch block 352913 from {'host': '46.6.14.27', 'port': 8444}, timed out, {'host': '46.6.14.27', 'port': 8444}. Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 526, in wrapped_coroutine result = await coroutine File "/chia-blockchain/chia/full_node/full_node_api.py", line 104, in new_peak return await self.full_node.new_peak(request, peer) File "/chia-blockchain/chia/full_node/full_node.py", line 372, in new_peak if await self.short_sync_backtrack( File "/chia-blockchain/chia/full_node/full_node.py", line 322, in short_sync_backtrack raise e File "/chia-blockchain/chia/full_node/full_node.py", line 307, in short_sync_backtrack raise ValueError(f"Failed to fetch block {curr_height} from {peer.get_peer_info()}, timed out") ValueError: Failed to fetch block 352913 from {'host': '46.6.14.27', 'port': 8444}, timed out 2021-05-29T00:56:57.771 full_node full_node_server : ERROR Exception: Failed to fetch block 352913 from {'host': '46.6.14.27', 'port': 8444}, timed out <class 'ValueError'>, closing connection {'host': '46.6.14.27', 'port': 8444}. Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 536, in api_call response: Optional[Message] = await asyncio.wait_for(wrapped_coroutine(), timeout=timeout) File "/usr/lib/python3.8/asyncio/tasks.py", line 455, in wait_for return await fut File "/chia-blockchain/chia/server/server.py", line 533, in wrapped_coroutine raise e File "/chia-blockchain/chia/server/server.py", line 526, in wrapped_coroutine result = await coroutine File "/chia-blockchain/chia/full_node/full_node_api.py", line 104, in new_peak return await self.full_node.new_peak(request, peer) File "/chia-blockchain/chia/full_node/full_node.py", line 372, in new_peak if await self.short_sync_backtrack( File "/chia-blockchain/chia/full_node/full_node.py", line 322, in short_sync_backtrack raise e File "/chia-blockchain/chia/full_node/full_node.py", line 307, in short_sync_backtrack raise ValueError(f"Failed to fetch block {curr_height} from {peer.get_peer_info()}, timed out") ValueError: Failed to fetch block 352913 from {'host': '46.6.14.27', 'port': 8444}, timed out 2021-05-29T00:56:57.772 full_node full_node_server : WARNING Banning 46.6.14.27 for 10 seconds 2021-05-29T01:10:33.673 full_node full_node_server : WARNING Cannot write to closing transport 108.168.120.158 2021-05-29T01:37:55.532 full_node full_node_server : ERROR Exception Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6ee38d30> at 49.88.99.59, exception Stack: Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 235, in incoming_connection connection = WSChiaConnection( File "/chia-blockchain/chia/server/ws_connection.py", line 59, in __init__ raise ValueError(f"Was not able to get peername from {self.ws_witer} at {self.peer_host}") ValueError: Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6ee38d30> at 49.88.99.59 2021-05-29T02:20:43.026 full_node full_node_server : ERROR Exception: Failed to fetch block 353171 from {'host': '58.101.159.137', 'port': 8444}, timed out, {'host': '58.101.159.137', 'port': 8444}. Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 526, in wrapped_coroutine result = await coroutine File "/chia-blockchain/chia/full_node/full_node_api.py", line 104, in new_peak return await self.full_node.new_peak(request, peer) File "/chia-blockchain/chia/full_node/full_node.py", line 372, in new_peak if await self.short_sync_backtrack( File "/chia-blockchain/chia/full_node/full_node.py", line 322, in short_sync_backtrack raise e File "/chia-blockchain/chia/full_node/full_node.py", line 307, in short_sync_backtrack raise ValueError(f"Failed to fetch block {curr_height} from {peer.get_peer_info()}, timed out") ValueError: Failed to fetch block 353171 from {'host': '58.101.159.137', 'port': 8444}, timed out 2021-05-29T02:20:43.028 full_node full_node_server : ERROR Exception: Failed to fetch block 353171 from {'host': '58.101.159.137', 'port': 8444}, timed out <class 'ValueError'>, closing connection {'host': '58.101.159.137', 'port': 8444}. Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 536, in api_call response: Optional[Message] = await asyncio.wait_for(wrapped_coroutine(), timeout=timeout) File "/usr/lib/python3.8/asyncio/tasks.py", line 455, in wait_for return await fut File "/chia-blockchain/chia/server/server.py", line 533, in wrapped_coroutine raise e File "/chia-blockchain/chia/server/server.py", line 526, in wrapped_coroutine result = await coroutine File "/chia-blockchain/chia/full_node/full_node_api.py", line 104, in new_peak return await self.full_node.new_peak(request, peer) File "/chia-blockchain/chia/full_node/full_node.py", line 372, in new_peak if await self.short_sync_backtrack( File "/chia-blockchain/chia/full_node/full_node.py", line 322, in short_sync_backtrack raise e File "/chia-blockchain/chia/full_node/full_node.py", line 307, in short_sync_backtrack raise ValueError(f"Failed to fetch block {curr_height} from {peer.get_peer_info()}, timed out") ValueError: Failed to fetch block 353171 from {'host': '58.101.159.137', 'port': 8444}, timed out 2021-05-29T02:59:31.131 full_node full_node_server : ERROR Exception Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6ee388b0> at 139.212.199.45, exception Stack: Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 235, in incoming_connection connection = WSChiaConnection( File "/chia-blockchain/chia/server/ws_connection.py", line 59, in __init__ raise ValueError(f"Was not able to get peername from {self.ws_witer} at {self.peer_host}") ValueError: Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6ee388b0> at 139.212.199.45 2021-05-29T03:41:18.587 full_node full_node_server : WARNING Cannot write to closing transport 71.38.39.180 2021-05-29T03:47:44.340 full_node full_node_server : ERROR Exception: [Errno 110] Connection timed out with 14.116.68.46 2021-05-29T03:47:44.341 full_node full_node_server : ERROR Exception Stack: Traceback (most recent call last): File "/chia-blockchain/chia/server/ws_connection.py", line 208, in outbound_handler await self._send_message(msg) File "/chia-blockchain/chia/server/ws_connection.py", line 368, in _send_message await self.ws.send_bytes(encoded) File "/chia-blockchain/venv/lib/python3.8/site-packages/aiohttp/web_ws.py", line 307, in send_bytes await self._writer.send(data, binary=True, compress=compress) File "/chia-blockchain/venv/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 685, in send await self._send_frame(message, WSMsgType.BINARY, compress) File "/chia-blockchain/venv/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 656, in _send_frame await self.protocol._drain_helper() File "/chia-blockchain/venv/lib/python3.8/site-packages/aiohttp/base_protocol.py", line 87, in _drain_helper await waiter File "/usr/lib/python3.8/asyncio/selector_events.py", line 846, in _read_ready__data_received data = self._sock.recv(self.max_size) TimeoutError: [Errno 110] Connection timed out 2021-05-29T06:23:14.519 full_node full_node_server : WARNING Cannot write to closing transport 212.62.201.4 2021-05-29T07:39:02.379 full_node full_node_server : ERROR Exception Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6fade280> at 175.171.188.207, exception Stack: Traceback (most recent call last): File "/chia-blockchain/chia/server/server.py", line 235, in incoming_connection connection = WSChiaConnection( File "/chia-blockchain/chia/server/ws_connection.py", line 59, in __init__ raise ValueError(f"Was not able to get peername from {self.ws_witer} at {self.peer_host}") ValueError: Was not able to get peername from <function WSChiaConnection.__getattr__.<locals>.invoke at 0x14af6fade280> at 175.171.188.207 I'm only bringing these things up as I don't want to waste my time or money if the configuration isn't optimized for the real chances of "winning xch" and I want others to take this consideration and look into their setups as well. I currently have a node that is syncing on an ubuntu install that I'll move over to once it is finished to see if that makes any difference. Everything is on the same machine, so one would think that times should be pretty fast if the disks are spun up before the lookup happens. All my disks are "green" and spun up all the time now. I just double checked this. Edited May 29, 20215 yr by live4soccer7
May 29, 20215 yr On 5/26/2021 at 9:57 PM, HATEME said: I got all the way to step Venv: "..activate" Umm Wut? Pardon my noobness, but what command do I enter? Tried every combination of ../activate, venv:../activate, activate venv, venv../activate. Even tried to google what a venv was... Everything just comes up as not found, not found, not found. The processes are running, but that's about it so far. Left click the Chia docker, left click "console" then paste this exact command EXCEPT the parentheses (. ./activate). *dot* *space* *dot* /activate I believe you were missing the space between the dots, it's easy to miss as it looks like it's the normal spacing between characters, but it's an actual press of the space bar between dots. If you did it correctly a new line should appear (venv) #
May 30, 20215 yr Any ideas how to prevent prolonged harvester times when mover is moving files from cache to disk? 021-05-30T09:28:50.116 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 053e266e94... Found 0 proofs. Time: 0.29248 s. Total 665 plots 2021-05-30T09:28:58.069 harvester chia.harvester.harvester: INFO 3 plots were eligible for farming 053e266e94... Found 0 proofs. Time: 0.15578 s. Total 665 plots 2021-05-30T09:29:08.202 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 053e266e94... Found 0 proofs. Time: 0.04793 s. Total 665 plots 2021-05-30T09:29:15.550 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 053e266e94... Found 0 proofs. Time: 90.20634 s. Total 665 plots 2021-05-30T09:29:18.927 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 053e266e94... Found 0 proofs. Time: 0.16241 s. Total 665 plots 2021-05-30T09:29:29.871 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.04839 s. Total 665 plots 2021-05-30T09:29:38.867 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.04701 s. Total 665 plots 2021-05-30T09:30:05.513 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.35507 s. Total 665 plots 2021-05-30T09:30:09.331 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 12.16856 s. Total 665 plots 2021-05-30T09:30:13.810 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.34542 s. Total 665 plots 2021-05-30T09:30:22.381 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.16945 s. Total 665 plots 2021-05-30T09:30:31.359 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.07466 s. Total 665 plots 2021-05-30T09:30:41.600 harvester chia.harvester.harvester: INFO 4 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.20139 s. Total 665 plots 2021-05-30T09:30:48.981 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.08108 s. Total 665 plots 2021-05-30T09:30:57.849 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.04439 s. Total 665 plots 2021-05-30T09:31:13.711 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 85.70189 s. Total 665 plots 2021-05-30T09:31:15.570 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.17471 s. Total 665 plots 2021-05-30T09:31:16.358 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 9.44518 s. Total 665 plots 2021-05-30T09:31:25.255 harvester chia.harvester.harvester: INFO 6 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.24972 s. Total 665 plots 2021-05-30T09:31:33.162 harvester chia.harvester.harvester: INFO 4 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.30697 s. Total 665 plots 2021-05-30T09:31:41.313 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.05186 s. Total 665 plots 2021-05-30T09:31:49.945 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.16118 s. Total 665 plots 2021-05-30T09:31:58.408 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.05384 s. Total 665 plots 2021-05-30T09:32:07.331 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.29088 s. Total 665 plots 2021-05-30T09:32:16.234 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.42783 s. Total 665 plots 2021-05-30T09:32:25.447 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.05527 s. Total 665 plots 2021-05-30T09:32:36.149 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4e2a5a6969... Found 0 proofs. Time: 0.15837 s. Total 665 plots What I tried/noticed so far: mover settings "Priority for mover process: very low" and "Priority for disk I/O: idle" don't seem to improve the situation it is not a thermal issue (all disks and processor way below 50 degrees) it is not processor (avg. 60% during running mover) or memory overload (30%) it is probably a I/O issue. I am using only 18 TB drives and I noticed that: write speed decreases from 280 MB/s to 130 MB/s when drives are 90% full (is it normal?) frequency of harvester times above 5s increases a lot when plots are copied to nearly full drives Any suggestions how to improve this? Maybe there is an option to give chia_harvester highest priority for I/O?
May 30, 20215 yr 9 hours ago, unririd said: Any ideas how to prevent prolonged harvester times when mover is moving files from cache to disk? Any suggestions how to improve this? Maybe there is an option to give chia_harvester highest priority for I/O? Yes, this is a good question as you don't want those long seek times when responding to a blockchain challenges. Have you tried out using Unassigned Disks to hold some/all plots, rather than your main Array? I started on the array too, but am now using a bunch of externals that appear as Unassigned Devices. I'm getting sub-second responses from them. It's possible to extract a disk from the Array and make it Unassigned I believe. The drawback is that copies to these Unassigned shares can be slow from other plotting systems (~15 minutes) as there is no fast cache to speed the write. Definitely a trade-off there. Hope this helps! Edit: It occurs to me that setting your particular Plots share on the Array to "Use cache pool" = No, might be a middle-ground to try first before removing drives from the array. Same trade-off as above though. Edited May 30, 20215 yr by guy.davis
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.