Solo?
-
the closest thing I can get is this error:
[22:28:37] Setting GPU 0 engine clock to 1025
[22:28:37] Setting GPU 0 memory clock to 1250
[22:28:37] WARNING: GPU_MAX_ALLOC_PERCENT is not specified!
[22:28:37] WARNING: GPU_USE_SYNC_OBJECTS is not specified!
[22:28:37] Probing for an alive pool
[22:28:37] Testing 127.0.0.1
[22:28:37] Probing for GBT support
[22:28:44] No GBT coinbase + append support found, using getwork
[22:28:44] Successfully retrieved but FAILED to decipher work fro
[22:28:44] No suitable long-poll found for http://127.0.0.1:9337 -
I’m out of ideas here :(
The only thind I can add is, that longpoll is not possible with solomining, so you should start with --no-longpoll.
But that will not solve the problem you have.
Stupid question: is your wallet fully synchronized? I asume yes…
-
I’m wondering if something has change in a Windows update?
-
Have you tried using a proxy between the miner and local wallet?
-
Try CPUminer first.
-
I have not tried a proxy, the mining system and the system with the feathercoin client are the same system so is this needed?
I tried CPUminer and its working fine.
-
I guess I have to make a GPU miner of my own which just works at least.
-
Thats the odd part. I can mine on a pool just fine, like p2pool. But if I change the config to point to my own wallet it fails.
Ive also got some old ASICs solo mining bitcoin so I am confident that its possible and that Im capable of doing it… I just dont know what went wrong here. I guess my next try will be with a different computer setup as the miner.
-
They don’t support Getwork properly (with or without long polling). Solo mining doesn’t use Stratum.
-
I have had a little experience in solo and got the same result (it was error: “no servers were found to get work from, please check url or credentials.”). Then I tried to take another wallet from this https://forum.feathercoin.com/index.php?/topic/8018-dev-feathercoin-core-093-alpha-release/. The error message is gone.
May be something wrong with the oficial wallet?
-
I am having the exact same problem. I can pool mine without any issues but solo mining does not work and I have tried every .conf suggestion in these forums.
-
I am new to feathercoin so forgive my persistence. Has anyone come up with an answer as to why solo mining does not seem to work for some people? I can solo mine other coins but not feathercoin.
feathercoin.conf:
server=1
daemon=1
rpcuser=featherrpc
rpcpassword=x
rpcport=9337
rpcallowip=192.168.1.*
sgminer conf:
{
“pools” : [
{
“url” : "http://192.168.1.15:9337",
“user” : “featherrpc”,
“pass” : “x”
}
]
,
“intensity” : “13”,
“kernel” : “neoscrypt”,
“worksize” : “64”,
blah, blah, blah…
when I start sgminer (I have tried 5.0, 5.1 and 5.1.1) I get a message:
192.168.1.15 slow/down or URL or credentials invalid
…and all the rest.
I start the wallet (versions 0.8.7.1 and 0.9.3) with the -server option but its as if the wallet is not listening or allowing connections from miners.
I can pool mine, but I like to have solo as a backup in case the pool fails.
What am I - and apparently others - missing?
Thanks.
-
I have only ideas, but:
-
I’m not sure if the 192.168.1.* works. can you try to specify the miner host only?
-
If you are using any firewall, check, that connections to port 9337 are allowed in the rule set
-
check if your wallet is listening to port 9337
-
linux: ‘netstat -lnp |grep feather’
-
windows: you need to find the parameters for : show listeing ports, no name resolution and show program information
-
Also I don’t use the port parameter in the feathercoin.conf, but use the default parameter, which should be 9337 anyway.
-
-
Thanks for the response.
It was the firewall. After configuring the firewall for feathercoin-qt.exe solo mining works. I could not recall if the prompt to open the firewall came up when I started the program but I guess not.
btw, 192.168.1.* does work in the .conf file. * is a wildcard for any IP address.
Thanks again. This was an oversight on my part.
