Jump to content
News Ticker
Sign in to follow this  
dukemc

Error with Pool

Recommended Posts

Have talked to Andy in Telegram he advised me to start a topic here that Daniel can look over:

I have a error creating a pool for CHI Mining. Its all setup and working but if it found a block there are block rejected errors:

stratum log

10:30:18: ERROR: rpc_do_call: 127.0.0.1:8939 500
10:30:18: ERROR Xaya Invalid mode
10:30:18: *** REJECTED :( Xaya block 10790 1 txs
2018-07-17 10:30:18: REJECTED CHI block 10790

 

debug.log of coindaemon

2018-07-17T08:30:17Z CreateNewBlock() packages: 0.01ms (0 packages, 0 updated descendants), validity: 0.63ms (total 0.64ms)
2018-07-17T08:30:18Z received: headers (167 bytes) peer=6
2018-07-17T08:30:18Z received: getdata (37 bytes) peer=2
2018-07-17T08:30:18Z received getdata (1 invsz) peer=2
2018-07-17T08:30:18Z received getdata for: cmpctblock e60c74121045b0ab9eb0664e811b5a5f9a27d9b5132eeb63f8470c3203f0343b peer=2
2018-07-17T08:30:18Z sending cmpctblock (359 bytes) peer=2
2018-07-17T08:30:18Z received: headers (167 bytes) peer=5
2018-07-17T08:30:18Z Received a POST request for / from 127.0.0.1:57380
2018-07-17T08:30:18Z ThreadRPCServer method=getblocktemplate user=xayarpc
2018-07-17T08:30:21Z connection to 37.174.37.130:8394 timeout
2018-07-17T08:30:23Z trying connection [2606:a000:e646:b600:8c9:fc6f:a7ae:8a9e]:8394 lastseen=20.1hrs
2018-07-17T08:30:23Z connect() to [2606:a000:e646:b600:8c9:fc6f:a7ae:8a9e]:8394 failed: Network is unreachable (101)
2018-07-17T08:30:24Z trying connection [2001:0:9d38:953c:2ca4:3036:3f57:ffd6]:8394 lastseen=17.3hrs
2018-07-17T08:30:24Z connect() to [2001:0:9d38:953c:2ca4:3036:3f57:ffd6]:8394 failed: Network is unreachable (101)
2018-07-17T08:30:24Z trying connection 103.85.206.230:8394 lastseen=74.6hrs
2018-07-17T08:30:29Z connection to 103.85.206.230:8394 timeout

Share this post


Link to post
Share on other sites

are you able to run the daemon with -debug=1

or have you?

@domob could this be related to the format change that f2pool were talking about?

Share this post


Link to post
Share on other sites

Yes, this can very well be related to the issue F2Pool mentioned.  @dukemc, please check your debug.log for details of why the block gets rejected.  Or can you perhaps share a full rejected block (e.g. as hex) so I can take a look?

Share this post


Link to post
Share on other sites

The Second Log is from the debug.log at the same time as the block get rejected. I dont know why theres a two hour time difference. I can paste the whole Log If needed.

Share this post


Link to post
Share on other sites
1 hour ago, dukemc said:

The Second Log is from the debug.log at the same time as the block get rejected. I dont know why theres a two hour time difference. I can paste the whole Log If needed.

Yes, please post the full log - or look for some message that specifically says "ERROR" or something like that when validating the block.  (I'm not sure if there is such a message, but I hope there is.  If not, I think I need an example block to debug this properly.)

Share this post


Link to post
Share on other sites

Thanks for the logs by PM - unfortunately they do not contain anything useful it seems.  I do not see any messages regarding the rejected block.  How does your pool submit the block and know it was rejected?  There are no "submitblock" RPC calls in the logs and I thought that would be the way to do it (but I'm not a miner).

Share this post


Link to post
Share on other sites

Thats the same i have seen - if there was a error in the log i think i could sort this error out. But with no response or log it´s quite difficult to get this to work. What should we do?

What does this mean:

10:30:18: ERROR: rpc_do_call: 127.0.0.1:8939 500
10:30:18: ERROR Xaya Invalid mode ????

Invalid mode.. are there any special options to start the xayad? Something special for the xaya.conf?

Share this post


Link to post
Share on other sites

I think that's an error by the miner / your pool script, not xayad, right?  Then I'm afraid I do not know what it means, you would have to check the miner's documentation or source code.

As I said, do you know how the miner actually tried to submit the block and found it rejected?  I do not see any traces of submitted blocks in the Xaya logs.  Perhaps the error is entirely on the miner's side.

Share this post


Link to post
Share on other sites

yes its from the stratum part of the pool script --> it seems it could not talk correctly to the xayad with the given commands.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

Your use of this site is governed by our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.