Fighting Steem Daemon #6
I finally had a little success !
The fix suggested by @abit worked alright - It was my fault.
Steemd replayed, started a witness, synced and started mining.


The whole thing is pointless, though.
There is a bug.
So I won't be able to show off a POW.
Nobody is back in the miner queue with his Supercomputing accounts.

It looks like two people can exploit this bug.
I hope it gets fixed quickly and that I can get the miner running quickly after the next fork.
Thanks @abit and @smooth for taking the time to help me.
Can you spot the difference ?
sudo mount -o remount,size=10G /dev/shm
works.
sudo mount -o remount, size=10G /dev/shm
doesn't work.
Maybe I can skip avoidable mistakes like that next time.
Here is a picture of my miner hashing:

I'm waiting for the bugfix now.
Steem on !
blank after comma?
B)
It's a shame they couldn't make mining more practical. It might attract more people to the project
I expect that.
The last fork seemed rushed and a lot of things got changed at the same time.
But all together it's quite some progress, I think.
Equihash is pretty popular through ZCash and after that (new) queue-bug is fixed, I expect more competition.
fixed Steam in the title -.-
@felixxx
it's the space between the comma and size?
so there are still bugs - sighs no wonder it says I still am following less than 200+ people - sadness
thanks for the confirmation
and good luck with your mining and "witness"
It's the space between the comma and size, yes ;)
The displayed number of people following you is a different bug. (not directly related to hardfork 16, I think)
The bug i mentioned above only affects the miner queue.
My "witness" technically was a witness.
I would need some major stakeholders to approve of it as witness though, before it would create/sign any blocks.
It was a witness node none the less B) (turned it off now).
@felixxx I see .. good luck with everything
as for the 'following" it's okay now I suppose