Open njmdk opened 5 years ago
I'm still dealing with that issue, in my case, account was unlocked but payment wasn't automatically sending because of insufficient funds. Remember that constantinople hard fork reduced reward from 3eth to 2eth. I manually added the lines other user posted to unlocker.go but didn't worked for me. i am waiting for next block, this time i commented all previous rewards and just left last fork. I'll let you know later if it worked.
i modify eth_sign and eth_sendTransaction to personal_sign and personal_sendTransaction can work And it's safe.my test pool ropsten http://122.114.14.153
@njmdk are you still running your pool? i am not able to build the frontend anymore, i don't know if something changed... when pool is down i have the "Stats API Temporarily Down" which is correct, but when i start the pool the home page goes blank, no stats at all, just background and footer is showing. this is in another fresh installed server, my first server is running well but now i don't want to touch it because of this
@njmdk are you still running your pool? i am not able to build the frontend anymore, i don't know if something changed... when pool is down i have the "Stats API Temporarily Down" which is correct, but when i start the pool the home page goes blank, no stats at all, just background and footer is showing. this is in another fresh installed server, my first server is running well but now i don't want to touch it because of this
intl-format-cache.zip copy that into ../node-modules/intl-format-cache/ in zip archive you have 2 folders: lib & src Enjoy!
ubuntu16.04
Parity version: 2.4.6
Redis version:
redis-server --version
OS & Version: Linux
Commit branch and hash: (
master
,ba60e1c
)Running Payment No Response Parity config. [rpc] apis = ["personal","web3", "eth", "pubsub", "net", "parity", "parity_pubsub", "traces", "rpc", "shh", "shh_pubsub"]
rpc call personal_unlockAccount can success,but rpc call eth_sendTransaction Payment No Response payout fail, why???