chia-plot-sink doesn't work with mmx-cpu-plotter

Question

chia-plot-sink doesn't work with mmx-cpu-plotter

Opened this issue 2 years ago · 14 comments

The parameter does not accept '-d @localhost' for WIN10. Will there be support in new versions?
It was also great to add GPU plotter supports multiple -d

madMAx43v3r commented 2 years ago

yes

Answer 1 · 2023-02-06T23:36:45.000Z

Windows doesn't like you using localhost to refer to the local host, you have to use the actual host name like @PC-345345345.

Answer 2 · 2023-02-07T06:38:32.000Z

-d @PC-345345345 not work for mmx-cpu-plotter. There is no new version 2.4 for WIN10
It only works for mmx-cuda-plotter

Answer 3 · 2023-02-07T06:41:43.000Z

Farmer Public Key (48 bytes) needs to be specified via -f, see chia keys show.
This is the error it shows

Answer 4 · 2023-02-07T16:09:16.000Z

ah yeah it only works with GPU plotter yes

Answer 5 · 2023-02-07T18:49:38.000Z

Will copy-sink be supported in the future by mmx-cpu-plotter?

Answer 6 · 2023-02-07T19:54:35.000Z

Thanks for what you do! You are a great person and will remain in history forever.

Answer 7 · 2023-02-08T20:16:10.000Z

Now available here: https://github.com/madMAx43v3r/chia-gigahorse

Answer 8 · 2023-02-08T21:38:36.000Z

Dear friend, -d @hostname does not work again in the new version.
The readme also does not specify the additional parameter -d, as for cuda-plotter
cpu-plotter - (-d, --finaldir arg Final directory to copy plot in parallel (default =tmpdir))
cuda-plotter - ( -d, --finaldir arg Final destinations (default = tmpdir, remote = @host))

Answer 9 · 2023-02-09T00:10:33.000Z

yes need to update readme, -d @HOSTNAME is need to make it work

Answer 10 · 2023-02-09T07:51:13.000Z

The problem was in powershell for windows. Need extra quotes " " "@hostname". Everything works fine for CMD

Answer 11 · 2023-02-09T13:00:06.000Z

After the task is ready, I get error 10093
Copy to *.plot failed with: socket() failed with: 10093
What could be the problem? Tried on different machines
My task
./chia_plot -n -1 -k 32 -C 6 -x 11337 -r 31 -K 1 -u 256 -v 256 -t A:\ -d @hostname -f ... -p ...

Answer 12 · 2023-02-09T14:29:12.000Z

Internet search turned up that this is related to WSAStartup

WSANOTINITIALISED10093	Successful WSAStartup not yet performed.Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.

WSANOTINITIALISED 10093 Successful WSAStartup not yet performed. Either the application has not called [WSAStartup](https://learn.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-wsastartup) or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or [WSACleanup](https://learn.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-wsacleanup) has been called too many times.

https://learn.microsoft.com/en-US/windows/win32/winsock/windows-sockets-error-codes-2

Answer 13 · 2023-02-09T16:21:02.000Z

oh yes, I forgot something...