+6
Answered

anyone else getting socket errors?

kipo 6 years ago updated 6 years ago 17

getting socket errors every couple of minutes, i'm in the uk and my line speed seems fine. 50 ms ping to etn.coinfoundry.org

Same here, in Bulgaria, rock solid internet connection, but Socket errors every couple of minutes.

+1

same here in america, it started for me 20 mins ago (~1:20 EST)

+1

cant even connect anymore, just continuous timing out

Same here. Just a page full of timeout errors

is anyone able to contact Oliver?

+1

Last ETN block found after 2 hours shows 0% status and empty Effort column. Guess it is broken now.

Same here. And last block found is now 7 hours old and still at 0% status. I'm guessing one of the ETN daemons has stopped.

+2

Just in case no one else has, I've logged a ticket for Oliver to have a look.

+1
Under review

The electroneum daemon is not responding to RPC commands from the pool anymore. Trying to fix it.

+1
Answered

Fixed.

Hi , hat uns diese Geschichte etwa den ETN Block gekostet ?  Schade ....

Nein. In dem Zustand in dem der Node war hätte er den Block nicht entgegen genommen.

What happens with shares and orphan blocks? ie, do the shares used to generate the block that was orphan get carried over to the next block (assuming the next block is short and taking into account PPLNS etc)?

Thanks

+2

Yes of course. From the pool's perspective an orphaned block is one that never happened.

+1

In PPLNS, some shares get carried over to the next block even if a real block is found. Basically your window of eligible shares constantly "travels" across an imaginary stack of shares. A new share always pushes out an older share that falls beyond the window.

+1

Oliver, thanks for sorting this out. I'll be back once i've mined the minimum with another pool.