Solo mining batch file no longer works after wallet update...

jimmy24651

Any ideas…?

AcidD

you have to atleast post the error dude ;-)

jimmy24651

Wellenreiter

Looks like your daemon isn’t accepting the rpc call.
Please check your debug.log for configuration errors.
There is something wrong with the rpc part of your configuration.
The syntax has slightly changed.
It also would be interesting to see your rpc allow ip lines of your config

jimmy24651

@AcidD
@Wellenreiter

Bear in mind, this worked flawlessly before the upgrade. I actually have other machines currently using it, which I haven’t upgraded.

I dont know exactly what I’m looking at on the debug file. I copied the last few lines. Maybe this will help…

2018-02-25 19:55:31 Peer 159.100.246.11:9336 unknown, sending version using dual magic
2018-02-25 19:55:31 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:31 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:39830, peer=2
2018-02-25 19:55:31 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:55:39 No valid UPnP IGDs found
2018-02-25 19:55:39 upnp thread exit
2018-02-25 19:55:41 Loading addresses from DNS seeds (could take a while)
2018-02-25 19:55:42 27 addresses found from DNS seeds
2018-02-25 19:55:42 dnsseed thread exit
2018-02-25 19:55:43 Peer 94.130.69.120:9336 unknown, sending version using dual magic
2018-02-25 19:55:43 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:43 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:44545, peer=3
2018-02-25 19:55:43 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:46 upnp thread start
2018-02-25 19:55:56 No valid UPnP IGDs found
2018-02-25 19:55:56 upnp thread exit
2018-02-25 19:56:00 Peer 173.212.192.212:9336 unknown, sending version using dual magic
2018-02-25 19:56:00 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:00 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:36714, peer=4
2018-02-25 19:56:00 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:56:06 Peer 176.9.50.227:9336 unknown, sending version using dual magic
2018-02-25 19:56:06 ProcessMessages(version, 103 bytes) FAILED peer=5
2018-02-25 19:56:07 Peer 24.57.129.35:9336 unknown, sending version using dual magic
2018-02-25 19:56:07 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:07 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:48793, peer=6
2018-02-25 19:56:07 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:13 Peer 188.165.254.191:9336 unknown, sending version using dual magic
2018-02-25 19:56:13 ProcessMessages(version, 105 bytes) FAILED peer=7
2018-02-25 19:56:52 Peer 207.134.44.31:9336 unknown, sending version using dual magic
2018-02-25 19:56:52 ProcessMessages(version, 107 bytes) FAILED peer=8
2018-02-25 19:57:09 Peer 104.225.220.19:9336 unknown, sending version using dual magic
2018-02-25 19:57:09 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:57:09 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:42940, peer=9
2018-02-25 19:57:09 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:57:32 Peer 192.77.188.104:9336 unknown, sending version using dual magic
2018-02-25 19:57:32 ProcessMessages(version, 107 bytes) FAILED peer=10
2018-02-25 19:57:33 Peer [2a01:4f8:130:11a6::4]:9336 unknown, sending version using dual magic
2018-02-25 19:57:33 ProcessMessages: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:57:33 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=[2601:cd:c100:535c:1d5c:57dd:7466:27ae]:63680, peer=11
2018-02-25 19:57:33 AdvertiseLocal: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:57:39 Peer 78.129.241.145:9336 unknown, sending version using dual magic
2018-02-25 19:57:40 ProcessMessages(version, 107 bytes) FAILED peer=12
2018-02-25 19:57:40 Peer 86.5.228.85:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 Peer [2001:41d0:2:c9bf::]:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 ProcessMessages(version, 105 bytes) FAILED peer=14
2018-02-25 19:57:47 Peer 37.187.106.98:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 ProcessMessages(version, 107 bytes) FAILED peer=15
2018-02-25 19:57:58 UpdateTip: new best=149143892ddd5b133184ae5b223c0126f95b7ef8e127bd36d91824168f5202d8 height=2103946 version=0x00000002 log2_work=58.344688 tx=4199690 date=‘2018-02-25 19:57:17’ progress=0.999998 cache=0.0MiB(23tx)
2018-02-25 19:57:58 ProcessMessages(version, 107 bytes) FAILED peer=13
2018-02-25 19:57:59 Peer 84.153.220.102:9336 unknown, sending version using dual magic
2018-02-25 19:58:17 Peer 46.4.0.101:9336 unknown, sending version using dual magic
2018-02-25 19:58:17 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:58:17 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103946, us=73.7.68.100:43255, peer=17
2018-02-25 19:58:17 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:58:23 Peer [2a02:c207:2008:7125::1]:9336 unknown, sending version using dual magic
2018-02-25 19:58:23 ProcessMessages: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:58:23 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103946, us=[2601:cd:c100:535c:1d5c:57dd:7466:27ae]:63858, peer=18
2018-02-25 19:58:23 AdvertiseLocal: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 20:01:51 tor: Thread interrupt
2018-02-25 20:01:51 torcontrol thread exit
2018-02-25 20:01:51 msghand thread interrupt
2018-02-25 20:01:51 scheduler thread interrupt
2018-02-25 20:01:51 addcon thread interrupt
2018-02-25 20:01:51 opencon thread interrupt
2018-02-25 20:01:51 net thread interrupt
2018-02-25 20:01:51 Shutdown: In progress…
2018-02-25 20:01:51 StopNode()
2018-02-25 20:01:52 Shutdown: done

AcidD

to me it looks like your Feathercoind node is starting and then stopping.

Can you confirm it’s running 100% before trying your batch file ?

Wellenreiter

@jimmy24651 said in Solo mining batch file no longer works after wallet update...:

2018-02-25 20:01:51 tor: Thread interrupt
2018-02-25 20:01:51 torcontrol thread exit

Are you using tor as the only network?
Can you try to use IPv4/IPv6 if the answer is yes to the above?

Based on the log output there is a chance, that tor fails and causes the shutdown.

jimmy24651

you guys are talking about things which i dont understand.

i dont know how my wallet would be using the tor network. i dont even know what that means.

all i did was download a copy of the latest wallet from the website.

Wellenreiter

Just add a line

onlynet=ipv4

to your feathercoin.conf and try again. This will force the wallet to use normal IP connections only and not try to use the tor network.

Just guessing here, but we need to eliminate all unnecessary protocols to reduce complexity and isolate your problem.

Bushstar

There were changes to RPC access, try changing the rpcallowip to the localhost IP you are connecting on.

rpcallowip=127.0.0.1

Also make sure that your password is somewhat strong, alphanumeric with upper and lower case and 8+ chars long.

jimmy24651

Thanks for the replies, guys!.. I’ll give this a shot this evening and see what happens!

jimmy24651

@Bushstar @Wellenreiter @AcidD

I first added "onlynet=ipv4 to the feathercoin.conf file, closed out the wallet, restarted it, and the problem was still there. Same error when I tried to start the miner.

Next, I updated the rpcallowip command to “rpcallowip=127.0.0.1” as instructed, and I went ahead and made the user and password something more secure. I restarted the wallet again, and am still getting the same error.

Is there anything more that I can do which would help any of you isolate what may be causing the problem? Go slow for me, as I know very little about the tech-side of things, aside from mining, and this little hiccup has shown me that I don’t know as much about mining as I thought I did!

Bushstar

Paying a bit more attention now, the CCminer command does not appear to have a coinbase address, so I’m guessing you are mining using getwork instead of getblocktemplate. getwork is not present in 0.13 as it was removed in the 0.10 Bitcoin codebase.

To be honest you will need to pool mine, the difficulty goes from 50 to 150, you will not get any blocks for a long time with that difficulty.

For pool mining there is NSGminer for AMD cards that has been updated for getblocktemplate, for CCminer I’ve seen that someone created HSRminer with NeoScrypt getblocktemplate support. If you want to solo mine then please get HSRminer and provide a coinbase address for the newly minted coins to be sent to.

jimmy24651

@bushstar

Thanks for the info!