Topic: 🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵 - page 33. (Read 133306 times)

So I have two bands that have been connected for ~7hrs... 24.154.55.93:11839/11840 but only one seems to be getting paid. Anyone else have ne thin similar ?

Edit: Just got another payment to band 2...

okay ill delet abave okay

Then the conflicted is just your wallet not right

-salvagewallet will clean it up

Oh yes I should make them smaller will do thanks again

The reason you see them in a row like that is because they are really all one deposit trying to stake and orphaning a few times in a row, then being accepted and they stop 

It's really all one transaction trying to stake, then finally being accepted

Okay then all set thanks

Just orphans. The network is super packed right now, they are bound to happen for a little while until it smooths out

The bottom one is not a valid transaction

I have some time now for issues like this, please copy paste an example and I'll take a look

Yes no config works better.  Any time to see why I loose my stakinging credits? If Gorrillabands get 50% of them I see  full debits of credits.

All caught up on swaps again. Everyone should have all their coins now

The debug.log suggests the masternode needs to be unlocked (for staking) to register as a masternode, but I am unsure about the need to keep it unlocked thereafter.
Ive kept mine in an unlocked for staking state just to be sure.

One thing I am trying to figure out is the queue order of masternode payments, they dont seem sequential to me.

I'll give this a shot and get back to you by tomorrow at the latest.

Also, does anyone else find they need to "unlock for staking only to keep the bands running ?

Had one band unlocked the other locked and the locked one strangely enough seemed to be the bread winner. So not sure what all still does or doesn't need to be done to get the most out of my bands. IGS said he doesnt use confs but I don't believe has started his type of setup like r his wallet excrypted, has he tried a system reboot or two with wallet launch on startup etc.

Ty.

10 connections now, more than I ever had for MMXIV.  Thanks - something obviously worked.

If anyone still struggling you can try this, most people know all these basics but not so long ago I didn't. So if you know how do do this just ignore & sorry to be basic...

I'm on Windows - actually on a Windows virtual machine on a mac (downloaded VMware fusion and a 64-bit Windows 8 image from a famous file-hosting site)

First make sure you can see hidden folders - go to control panel, type "folders" in the search box and select "show hidden files and folders".

Close down GorillaBucks client.

Then go to C:/Users/your name/AppData/Roaming/GorillaBucks (you won't see the AppData folder unless you have shown hidden folders)

Be very careful here, don't delete anything permanently until you are sure you have done this right - but basically delete or move out of the folder, everything apart from the wallet.dat

Now make a new Text Document in there and rename it:
 GorillaBucks.conf
(to open it again you may need to say "open as text document")

That's a conf file.  As iGotSpots says many people are running fine without one, or with the only contents being:

maxconnections=999

My conf file is as follows, using the addnodes iGS gave us earlier:

maxconnections=999
addnode=195.23.251.183
addnode=171.96.245.177
addnode=68.224.26.233
addnode=83.131.214.162
addnode=99.7.21.54
addnode=98.193.42.19
addnode=173.81.239.170
addnode=137.224.252.10
addnode=86.121.63.75
addnode=80.136.69.94
addnode=39.55.166.152
addnode=70.92.184.203
addnode=217.217.234.127
addnode=192.99.184.36
addnode=197.2.161.89
addnode=131.188.203.228
addnode=75.130.163.51
addnode=82.13.20.194
addnode=192.226.139.105
addnode=98.144.3.64
addnode=220.244.154.64
addnode=192.99.184.36
addnode=79.37.237.149
addnode=93.86.200.129
addnode=32.214.108.194
addnode=75.130.163.51
addnode=101.51.49.130
addnode=75.130.163.51
addnode=49.228.141.168
addnode=73.12.7.191
addnode=71.228.74.170
addnode=1.20.244.211
addnode=60.240.164.100
addnode=69.196.133.53
addnode=100.3.192.41
addnode=94.52.19.22
addnode=60.240.164.100
addnode=5.157.107.66
addnode=24.35.140.35
addnode=60.240.164.100
addnode=174.17.128.72
addnode=68.224.6.180
addnode=31.217.43.152
addnode=78.214.244.90
addnode=76.90.105.71
addnode=23.127.64.254
addnode=83.145.242.175
addnode=178.33.64.235
addnode=104.236.183.29
addnode=69.165.47.72
addnode=84.91.18.158
addnode=23.115.188.142
addnode=83.157.62.179
addnode=39.55.166.152

Hope that helps someone, good luck to all

Most of those commands you posted are for mining or servers, which are not needed here, either, so it would just be forcing your client to run less lightweight and be more of a resource hog than it needs to be

Remember, some people are running a bunch of masternodes on one machine, so usage is important to keep low

Sorry, I'm stressed. Glad it's working. There really is no need for a conf file, though, other than that one line if you want it

Fair enough.
I don't see anything i have written that implies that, but OK I will ask no more questions.

By the way the latest fixes have worked great, I now have 10 connections. Thanks for your hard work.

You act like I've not been helping people. I've written two in-depth guides and been working on connections issues for the past 48 hours straight, which are now resolved

If I don't give a conf example it's because you don't need one unless you want to add maxconnections=999

Spots, i only used that as a quick example from a google search.
None of the other coins I have run like shit they are all stable at 8 or more connection all the time without any problems.
I am not at all trying to be a dick here just noticed that alot of people were asking and were not getting any responses.

Why the attitude toward me? I have been nothing but nice to you through this transition.

That's because that coin runs like shit. I included a .bat if you want to edit folders