I'm running a node I have incoming transaction for let say 50 bucks that's in green and show as confirmed.
Will this be added to my balance and when or is it just there because of the node?
I have a few of these transactions there since yesterday with no change on my balance.
Thanks
Topic: 🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵 - page 40. (Read 133306 times)
June 30, 2015, 06:32:19 PM
June 30, 2015, 06:30:18 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.
I have a solution for this temporarily if you want to try it since you have a lot of nodes like I do
Try launching the .bat with port as 36480, but in GorillaBucks.conf, add as many nodes as you can from the staking wallet and add listen=0 at the bottom
Let me know what this returns for you. THIS IS NOT A PERMANENT SOLUTION, I HIGHLY SUGGEST NOT DOING THIS UNLESS SPECIFICALLY INSTRUCTED TO
I am simply trying to run a test that forces this node to accept only specific connections listed as addnodes by doubling up on a port that we know works for sure
rpcport=11839
port=11838
That being said... still running in to the issue where bands don't seem to start / show in the band list where all the bands are showed. Never did get an answer on that last night where I asked if bands will work with a fully locked wallet or have to be unlocked with "staking only" or fully unlocked to work which if fully unlocked doesnt make for a safe environment.
Right now I have band 24.154.55.93:11838 running locally and has been for ~20 minutes and is not showing up in the main band list... It does have 1 active connection so should be running fine like it was last night when I did a start from scratch deal.
If you don't see it on the list, click start all
I have not tested the locking, yet, that's why I'm not answering; don't want to give wrong answer, just try it and see
June 30, 2015, 06:26:34 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.I have a solution for this temporarily if you want to try it since you have a lot of nodes like I do
Try launching the .bat with port as 36480, but in GorillaBucks.conf, add as many nodes as you can from the staking wallet and add listen=0 at the bottom
Let me know what this returns for you. THIS IS NOT A PERMANENT SOLUTION, I HIGHLY SUGGEST NOT DOING THIS UNLESS SPECIFICALLY INSTRUCTED TO
I am simply trying to run a test that forces this node to accept only specific connections listed as addnodes by doubling up on a port that we know works for sure
still same with Network 1 Connection, same with .bat port 36480-36482
and a lot of orphan blocks
June 30, 2015, 06:25:11 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.I have a solution for this temporarily if you want to try it since you have a lot of nodes like I do
Try launching the .bat with port as 36480, but in GorillaBucks.conf, add as many nodes as you can from the staking wallet and add listen=0 at the bottom
Let me know what this returns for you. THIS IS NOT A PERMANENT SOLUTION, I HIGHLY SUGGEST NOT DOING THIS UNLESS SPECIFICALLY INSTRUCTED TO
I am simply trying to run a test that forces this node to accept only specific connections listed as addnodes by doubling up on a port that we know works for sure
rpcport=11839
port=11838
That being said... still running in to the issue where bands don't seem to start / show in the band list where all the bands are showed. Never did get an answer on that last night where I asked if bands will work with a fully locked wallet or have to be unlocked with "staking only" or fully unlocked to work which if fully unlocked doesnt make for a safe environment.
Right now I have band 24.154.55.93:11838 running locally and has been for ~20 minutes and is not showing up in the main band list... It does have 1 active connection so should be running fine like it was last night when I did a start from scratch deal.
June 30, 2015, 06:08:42 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.I have a solution for this temporarily if you want to try it since you have a lot of nodes like I do
Try launching the .bat with port as 36480, but in GorillaBucks.conf, add as many nodes as you can from the staking wallet and add listen=0 at the bottom
Let me know what this returns for you. THIS IS NOT A PERMANENT SOLUTION, I HIGHLY SUGGEST NOT DOING THIS UNLESS SPECIFICALLY INSTRUCTED TO
I am simply trying to run a test that forces this node to accept only specific connections listed as addnodes by doubling up on a port that we know works for sure
June 30, 2015, 05:50:39 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections. June 30, 2015, 05:47:49 PM
Ok, pushing a fix to the network. Please reload clients and report connection progress
Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.Edit: With the VARY client I ALWAYS had 7-8 connections if not more.
Edit2: One active connection now on the staking client but that's it, took 15mins just to get that one.
June 30, 2015, 05:45:59 PM
Better?
now have 8 conns on Gorillaband wallet and 4 on staking wallet, so a bit of an improvement here 
June 30, 2015, 05:44:54 PM
Better?
holding 2-3 connections on 1 machine:

[
{
"addr" : "68.224.6.180:36480",
"addrlocal" : "162.157.8.161:52928",
"services" : "00000001",
"lastsend" : 1435704131,
"lastrecv" : 1435704137,
"bytessent" : 101182,
"bytesrecv" : 195069,
"conntime" : 1435703152,
"pingtime" : 0.17160000,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 2381,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "82.13.20.194:36480",
"addrlocal" : "162.157.8.161:53153",
"services" : "00000001",
"lastsend" : 1435704132,
"lastrecv" : 1435704140,
"bytessent" : 2143,
"bytesrecv" : 38388,
"conntime" : 1435704086,
"pingtime" : 0.37440100,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 2393,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "23.92.61.98:36480",
"services" : "00000000",
"lastsend" : 1435704124,
"lastrecv" : 0,
"bytessent" : 129,
"bytesrecv" : 0,
"conntime" : 1435704124,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0,
"syncnode" : false
}
]
Other machine 0-1 connection to the 23.92 address. not stable
getting closer.....
June 30, 2015, 05:23:26 PM
Better?
June 30, 2015, 04:15:43 PM
Ok..........
Trying something else
Trying something else
June 30, 2015, 04:11:49 PM
Try using the .bat and changing both ports to 36480 - If that does not improve, try 36482
I believe I've narrowed the issue down to ports, I have seeds up on both ports now
I believe I've narrowed the issue down to ports, I have seeds up on both ports now
trying 36480:
Error: Specified data directory "masternodedirectory" does not exist
removed -datadir=masternodedirectory and connected to 1 peer then dropped
trying 36482:
connected to 3 peers:

[
{
"addr" : "68.224.6.180:36480",
"addrlocal" : "162.157.8.161:51661",
"services" : "00000001",
"lastsend" : 1435698468,
"lastrecv" : 1435698468,
"bytessent" : 1315,
"bytesrecv" : 19978,
"conntime" : 1435698450,
"pingtime" : 0.29640000,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 2319,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "23.92.61.98:36480",
"services" : "00000000",
"lastsend" : 1435698451,
"lastrecv" : 0,
"bytessent" : 129,
"bytesrecv" : 0,
"conntime" : 1435698451,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "41.226.110.48:36480",
"services" : "00000000",
"lastsend" : 1435698471,
"lastrecv" : 0,
"bytessent" : 129,
"bytesrecv" : 0,
"conntime" : 1435698471,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0,
"syncnode" : false
}
]
Has now dropped to 1 connection:

[
{
"addr" : "68.224.6.180:36480",
"addrlocal" : "162.157.8.161:51661",
"services" : "00000001",
"lastsend" : 1435698588,
"lastrecv" : 1435698571,
"bytessent" : 9504,
"bytesrecv" : 23210,
"conntime" : 1435698450,
"pingtime" : 0.17160000,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 2319,
"banscore" : 0,
"syncnode" : true
}
]
June 30, 2015, 04:09:37 PM
restarted on port 36482 and have 2 connections at the moment. Not counting the misbehaving seednode which connects intermittently.
its starting to look good
thanks spots.
its starting to look good
thanks spots.
June 30, 2015, 03:57:26 PM
Try using the .bat and changing both ports to 36480 - If that does not improve, try 36482
I believe I've narrowed the issue down to ports, I have seeds up on both ports now
I believe I've narrowed the issue down to ports, I have seeds up on both ports now
June 30, 2015, 03:55:32 PM
qt because I don't have windows. bu i have tried it with port 36842 and had the same issue.
Edit_: Should I try again with that port?
Edit_: Should I try again with that port?
June 30, 2015, 03:53:38 PM
Ok, I believe I figured out why some people are having connection issues
Are you guys loading with the GorillaBand.bat file or with the Qt itself?
I load with QT and I don't have gorillabands at the moment Are you guys loading with the GorillaBand.bat file or with the Qt itself?
June 30, 2015, 03:53:29 PM
Ok, I believe I figured out why some people are having connection issues
Are you guys loading with the GorillaBand.bat file or with the Qt itself?
Are you guys loading with the GorillaBand.bat file or with the Qt itself?
Just the Qt
June 30, 2015, 03:51:09 PM
Ok, I believe I figured out why some people are having connection issues
Are you guys loading with the GorillaBand.bat file or with the Qt itself?
Are you guys loading with the GorillaBand.bat file or with the Qt itself?
June 30, 2015, 03:50:26 PM
If you posted your IP, please close and reopen client, then report results
I am now connecting to 2 peers

[
{
"addr" : "23.92.61.98:36480",
"addrlocal" : "162.157.8.161:51425",
"services" : "00000001",
"lastsend" : 1435697319,
"lastrecv" : 1435697319,
"bytessent" : 10874,
"bytesrecv" : 2856,
"conntime" : 1435697307,
"pingtime" : 0.20001200,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 2301,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "78.214.244.90:36480",
"services" : "00000000",
"lastsend" : 1435697321,
"lastrecv" : 0,
"bytessent" : 129,
"bytesrecv" : 0,
"conntime" : 1435697321,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0,
"syncnode" : false
}
]
Managed to sync then connections dropped
June 30, 2015, 03:46:59 PM
Hi guys
is this a normal behaviour?
is this a normal behaviour?
I get this too and after 2 days my debits put me back to when we started Sunday. All 2 days of compounding credit are gone. When will we get those credits back.
Just an orphan. They happen from time to time, you don't lose anything
Jump to: