Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: Jude Austin on September 08, 2013, 08:19:53 PM



Title: Anyone having issues with P2Pool and Litecoin right now?
Post by: Jude Austin on September 08, 2013, 08:19:53 PM
A couple of days ago I noticed Litecoin was down on P2Pool.org.

So I got on a checked my screen to find this:
Code:
2013-09-06 16:16:46.013864 > Couldn't link returned work's merkle root with its handler. This should only happen if this process was recently restarted!

So I updated the Litecoin client and downloaded an updated version of P2Pool, I reindexed blocks, then started P2Pool back up with the same error.

What did I do?





Title: Re: Anyone having issues with P2Pool and Litecoin right now?
Post by: markm on September 08, 2013, 08:53:00 PM
Maybe wait and see, how recent do they mean by recent?

Seems you are saying you recently restarted it and lo and behold it has the same error despite being updated code...

I use p2pool for litecoin and for merged mining, I have seen that message before but am not seeing it right now. I think I git pulled within last few days. (I tend to from time to time anyway.)

-MarkM-


Title: Re: Anyone having issues with P2Pool and Litecoin right now?
Post by: Jude Austin on September 08, 2013, 09:15:29 PM
Maybe wait and see, how recent do they mean by recent?

Seems you are saying you recently restarted it and lo and behold it has the same error despite being updated code...

I use p2pool for litecoin and for merged mining, I have seen that message before but am not seeing it right now. I think I git pulled within last few days. (I tend to from time to time anyway.)

-MarkM-


Well, I noticed that I couldn't access the stats page, so I logged into my server and checked the screen output and it gave me that error.

So I killed everything, downloaded a new P2Pool from ForrestV github, downloaded the new LTC client, then I re-indexed the blocks, once that was done I started everything back up and I still had the same error.

I am wondering if this is some kind of attack or miner error causing this.