• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.17.x Testing

Status
Not open for further replies.
I can't keep any of these wallets up for more then 5 mins. All my test masternodes segfault before I get back to even checking them once. p2pool won't run for more then 5 mins without seg faulting.

Might be time to just wait for 0.10.17.2?
 
Last few blocks were oddly close to each other...

OTMTEzH.png


linux QT crashed when I tried my first InstantX to myself. Here are the last lines.

2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:41 ProcessMessages(dsee, 249 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-11-28 22:09:41 ProcessMessage(dsee, 249 bytes) FAILED
2014-11-28 22:09:43 connection timeout
2014-11-28 22:09:43 trying connection 50.254.73.148:19999 lastseen=0.2days
2014-11-28 22:09:43 connect() failed after select(): Connection refused
2014-11-28 22:09:44 trying connection 24.112.251.161:19999 lastseen=1.2days
2014-11-28 22:09:49 connection timeout
2014-11-28 22:09:49 trying connection 94.23.158.91:19999 lastseen=37.2days
2014-11-28 22:09:50 connect() failed after select(): Connection refused
2014-11-28 22:09:50 trying connection 70.209.73.64:19999 lastseen=0.2days
2014-11-28 22:09:52 1 addresses found from DNS seeds
2014-11-28 22:09:52 dnsseed thread exit
 
I can't keep any of these wallets up for more then 5 mins. All my test masternodes segfault before I get back to even checking them once. p2pool won't run for more then 5 mins without seg faulting.

Might be time to just wait for 0.10.17.2?

I can't keep the masternodes I setup to have darcoind stay running, after awhile they change to 0 and then drop off the list and darkcoind is no longer running. Checking logs on some of them now.
 
Have started 20 testnet masternodes, but they die very quickly. will try again once .2 is released.

Those close blocks are 16M hash I aimed at testnet. Stopping until .2 is released.
 
thoughts about new mixing methode :

it does seem to make pairing with other clients more easy but it also feels like its creating a lot more Darksend Denominate transactions which
gives Masternodes a lot more work to do then with previous mixing methode i think .. i just hope it wont conflict with the InstantX
transactions that the masternodes need to do as well (i'm kinda worried it may slow them down with this new methode)
 
How do you guys find the crash log? My QT just shuts off without a report (ubuntu 14.04)
 
Status
Not open for further replies.
Back
Top