I get "-17 days ahead" - and a later message "block verification failed, dropping connection" - ? any tips
This is a customary system message in the sync process. It means that the network had a connected daemon which was mining an alternative chain of lesser lenght. Now the daemon is online and sees that the top block is alternative and began synch. The quantity of days is calculated according to the chain it's missing. |
|
|
|
Failed to process TxI've received several messages that the pools now have the following error:  I've studied the simplewallet & RPC code. Now its clear that wallet2 was developed to be used with one thread only. It seems that the open source pool devs broke wallet state and now all the renewed pools are getting this error. The problem is that transactions are created with inputs which are already spent. You can solve the issue as follows: 1) re-sync your wallet 2) only one thread can address RPC of the wallet at one point, so put the payments in line.I've run that script within testnet by putting the payments in line. Tests have been going for about a day and everything is OK. I recommend the pool devs to make these changes.
|
|
|
|
Failed to process TxI've received several messages that the pools now have the following error: I've studied the simplewallet & RPC code. Now its clear that wallet2 was developed to be used with one thread only. It seems that the open source pool devs broke wallet state and now all the renewed pools are getting this error. The problem is that transactions are created with inputs which are already spent. You can solve the issue as follows: 1) re-sync your wallet 2) only one thread can address RPC of the wallet at one point, so put the payments in line.I've run that script within testnet by putting the payments in line. Tests have been going for about a day and everything is OK. I recommend the pool devs to make these changes.
|
|
|
|
Good news!Difficulty and overall network h/r systematically increased over the last week. See charts:  Diff Network h/rNow diff is about 75 mln and network h/r is about 1,240,000. Also the total transaction volume increased.  This chart doesn't include block rewards Currently about 260,000 quazarcoins was produced. Here're all chartsJoin to QuazarCoin:
|
|
|
|
Good news!Difficulty and overall network h/r systematically increased over the last week. See charts: DiffNetwork h/rNow diff is about 75 mln and network h/r is about 1,240,000. Also the total transaction volume increased. This chart doesn't include block rewards Currently about 260,000 quazarcoins was produced. Here're all chartsJoin to QuazarCoin:
|
|
|
|
Whether I use the windows blockchain that i downloaded today (500+ mb size) or I just launch the daemon, i eventually get this looping error message: 2014-Jun-22 16:25:06.818070 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection 2014-Jun-22 16:25:06.825071 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:638 [27.41.114.162:23080 OUT]Failed to do_send() 2014-Jun-22 16:25:06.831071 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection 2014-Jun-22 16:25:06.838071 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:638 [27.41.114.162:23080 OUT]Failed to do_send() in red text for maximal panic inducement. What am I doing wrong? I use the 64bit files since I'm using w7 x64 with 16gb ram. I can do xmr no problem, in fact mining it now. Thanks in advance for the help  This error doesn't interrupt sync&work and your QCNs remain safe. We are working to resolve this problem, I understand that huge red letters irritate users. |
|
|
|
I changed the pool fee of http://qcnpool.org to 0.75%. Maybe that makes it attractive enough to at least get the 8KH it needs to run smooth... Connect to qcnpool.org! |
|
|
|
Hey all,
I've noticed my Total Paid stats from minin.gs has not increased at all over the past 16 hours even though i've been mining straight. I've even confirmed that I haven't received payment via a wallet refresh.
Anyone else seeing this?
hello today my internet lag i can't connect to my server please wait me next 3 hour i payment all holding. It has been way more than 3 hours, and I still haven't received my payment! It's not scam pool and the pool dev is working with problems. |
|
|
|
+ 1 move hashrate to other pool I changed the pool fee of http://qcnpool.org to 0.75%. Maybe that makes it attractive enough to at least get the 8KH it needs to run smooth... Posted from Bitcointa.lk - #Ob4nqddbbFJYZWnkConnect to qcnpool.org! |
|
|
|
My daemon says im ahead 19 blocks  This is a customary system message in the sync process. |
|
|
|
When I run quazarcoind.exe. At first it's ok,SYNCHRONIZATION started.
But after a few minutes, error happen.The detail is:
2014-Jun-22 14:48:51.704505 [P2P7]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-22 14:48:51.714507 [P2P7]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-22 14:48:51.724508 [P2P7]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-22 14:48:51.734509 [P2P7]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:638 [107.170.193.84:23080 OUT]Failed to do_send()
2014-Jun-22 14:48:51.734509 [P2P7]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
I have down the new blockchain ,the error is still .Please help me
You can ignore these errors, the daemon will continue to synchronize. I am having the same. Well, maybe this isn't danger but it annoys me and could scare off new users. I'd like to know what is this and how to get rid of this. This error doesn't interrupt sync&work and your QCNs remain safe. We are working to resolve this problem, I understand that huge red letters irritate users. |
|
|
|
It appears all pools including mine, Extremepool, are having the same issues with payouts since the last update.
Dev can you assist?
whenever payout tries to go through get an error in daemon. tx to big
**http://qcn.extremepool.org has rolled back to a previous daemon and the payout issue has gone away**
waiting to hear from dev on a fix.
I'm in process, check PM. |
|
|
|
|
Show Posts
