Quote from: mrb on November 04, 2016, 08:56:24 AM

Quote from: efficienthash on November 04, 2016, 08:53:26 AM

@mrb

thanks, I got around that problem. I run into

Code:

DEBUG:asyncio:poll 573.300 ms took 0.016 ms: 1 events
DEBUG:asyncio:process 21691 exited with returncode 1
INFO:asyncio:<_UnixSubprocessTransport pid=21691 stdin=<_UnixWritePipeTransport closed fd=17 closed> stdout=<_UnixReadPipeTransport closed fd=18 closed>> exited with return code 1
DEBUG:asyncio:poll 563.276 ms took 0.014 ms: 1 events
DEBUG:asyncio:process 21692 exited with returncode 1
INFO:asyncio:<_UnixSubprocessTransport pid=21692 stdin=<_UnixWritePipeTransport closed fd=19 closed> stdout=<_UnixReadPipeTransport closed fd=20 closed>> exited with return code 1
INFO:asyncio:poll 999.912 ms took 1001.039 ms: timeout

I can run the solver manual and it seems to work. Is there an easy way to see the output/error of the solver so that I can keep debugging?

Weird. Enable verbose or very verbose ("-v" or "-v -v") mode and you'll see the stdout/stderr output of sa-solver.

Thanks, only tried -v. I guess it's then related to bytes.hex throwing an error - and I replaced it with binascii.hexlify - I can't find the documentation to bytes.hex.

Code:

To solvers: b'4f8d976e1283c0caa145b6f3fdd478e9263108ac1c5a643bdf4f8d976e128300' 9732eb5b92ca5bdbb150 b'04000000455f40ac14ec9f6bad6cc8d5de2714ea84be396203d45e710745605e01000000f963ea196bb8cb2260a2825beca315b6d1e6608d8696338e26b75f8b1a4f93da0000000000000000000000000000000000000000000000000000000000000000fc4e1c58940d041d' b'6493d02292'
From solver 0.0: banner "SILENTARMY mining mode ready"
From solver 0.0: strange: more than 1 line was read