[AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$

[Fuzzbawls]

...that sounds like it's hitting max connections

I suspected that, too... no signs of rejection or whatever and then, after some time it became responsive again.

Line from .conf
"maxconnections=1024"

Now wallet has ~30 active connections
Yesterday it was 69 at maximum.

Though I have never seen over 70 connections. Never.

Server load 20-30%

you can set maxconnections to whatever you like (over 9000!, for example) but that is just a theoretical hard cap and is limited by system resources and network activity. Basically, by setting it to a high value like you have, you're telling the daemon to just accept as many connections as it can possibly sustain (up to 1024).

[AmberCoinDev]

...that sounds like it's hitting max connections

I suspected that, too... no signs of rejection or whatever and then, after some time it became responsive again.

Line from .conf
"maxconnections=1024"

Now wallet has ~30 active connections
Yesterday it was 69 at maximum.

Though I have never seen over 70 connections. Never.

Server load 20-30%

you can set maxconnections to whatever you like (over 9000!, for example) but that is just a theoretical hard cap and is limited by system resources and network activity. Basically, by setting it to a high value like you have, you're telling the daemon to just accept as many connections as it can possibly sustain (up to 1024).

I have checked once again - server is loaded at 20%. (Memory ~50%)

[inget]

I upgraded my wallet. On 1 PC it is working fine (staking etc.).

On another PC it's still syncing (2 days now).

Are there any nodes?

[verycoinsuchlist]

Last DEBUG info from ambercoin01.mooo.com.
Maybe would be helpful.

getblocks stopping at limit 319039 000000001e9e81e56405
accepted connection 81.88.143.194:58254
getblocks 13920 to 000000002177ca4f7aa4 limit 500
  getblocks stopping at limit 14419 0000000000e17c6c14e5
partner 81.88.143.194:58254 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 81.88.143.194:58254
connection from 113.161.128.181:64841 dropped (banned)
getblocks 318540 to c184b39662b4c2b46b3b limit 500
  getblocks stopping at 318975 c184b39662b4c2b46b3b
connection from 71.187.62.42:56790 dropped (banned)
connection timeout
accepted connection 176.107.192.2:61021
partner 176.107.192.2:61021 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 176.107.192.2:61021
trying connection 108.61.174.143:31982 lastseen=1.2hrs
connection from 85.214.23.49:38378 dropped (banned)
connection from 213.180.26.45:53289 dropped (banned)
connection from 212.83.176.222:50699 dropped (banned)
connection from 213.180.26.34:54001 dropped (banned)
getblocks 598600 to 00000000ec75c4beed3d limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
getblocks 598600 to 00000000059cd7afbae2 limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
received getdata (12 invsz)
connection from 113.161.128.181:64842 dropped (banned)

ah, that probably answers some questions regarding the immediate disconnects ...that happens for sure if trying to resync with a blockchain that already went astray... even if peers.dat and addnode entries have been removed.
had the impression it might take about half an hour to be able to reconnect... does it?

so, safe to say: anyone who is assuming to be on the wrong chain should go and start off with the bootstrap blockchain before trying to sync with amber01.mooo.com!

[verycoinsuchlist]

I upgraded my wallet. On 1 PC it is working fine (staking etc.).

On another PC it's still syncing (2 days now).

Are there any nodes?

in brief:

- until the network is consistent again, ONLY the main node at ambercoin01.mooo.com is save to use.
- if you suspect being already on the next fork or in case of doubt REMOVE the following from your data folder:
  * subfolders 'database' and 'txleveldb',
  * blk0001.dat,
  * peers.dat
  if you don't remove the already forked blockchain data before trying to sync, you risk getting your clients ip
  temporarily banned by said node!
- backup your wallet, always do!
- custom config? you might want to rename/backup it first.
- get the bootstrap data here: https://bitcointalk.org/index.php?topic=944408.msg13087230#msg13087230
- extract the bootstrap archive into your data folder.
- however, in your config file or as startup option, there must be no addnode, just connect=ambercoin01.mooo.com
- as mentioned, listen=0 helps avoiding further connection attempts from outside (should internaly already set to 0 by using connect)
- upnp option should also be turned off, as stated earlier.
- now, start the client

IF YOU ONLY GET 0 CONNECTIONS EVEN AFTER SOME TIME, BE PATIENT!
YOU MIGHT HAVE BECOME TEMPORARILY BANNED DUE TO FORMER CONNECTION ATTEMPTS. IT WILL GO AWAY AFTER SOME TIME.



and some more tips:

...this can be done at anytime anyway without harm, but if you suspect your ballance might show some odd values, this will most likely fix the messed up display:

Just an FYI to all...

if you were caught off chain, and now you're back on... make sure you run checkwallet and repairwallet from debug window.

and keep in mind that all blocks being minted or mined AFTER tripping on a fork will of course stay on that fork... so, rolling back and resyncing to the main blockchain shows, they never existed in the first place. facing that case also means it would be a good time for the 'repairwallet' tip after syncing completed.

[exemplaar]

I upgraded my wallet. On 1 PC it is working fine (staking etc.).

On another PC it's still syncing (2 days now).

Are there any nodes?

If your first wallet is on correct chain (getblockbynumber 599640 "proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d") then just copy file blk0001.dat and (sub)folders database and txleveldb from working wallet and paste it to a nonworking wallet. On that nonworking wallet also remove file peers.dat and start again. It should sync.

make sure that you have your .conf file like that:
listen=0
connect=ambercoin01.mooo.com
addnode=ambercoin01.mooo.com

If you solomine then add server=1, rpc port and rpc commands to your .conf file.

This worked for me. No need for all that long procedure of deleting everything and starting from scratch.

[verycoinsuchlist]

...
make sure that you have your .conf file like that:
listen=0
connect=ambercoin01.mooo.com
addnode=ambercoin01.mooo.com
...

all agreed, but...

for the moment, I'd still avoid the addnode...
it might eventually spill in clients who are still on an improper chain. this might turn into a problem when the main node becomes unavailable for some time and you manage to sync yourself with an improper client. could leave you back in the same situation again.
'connect' is sufficient to stay on track for the time being.

[Fuzzbawls]

AmberCoin.conf file setups (assuming use with Qt GUI Wallet):

No Solo-Mining:

Code:

upnp=0
listen=0
connect=ambercoin01.mooo.com

Solo-Mining:

Code:

rpcuser=<desired_username>
rpcpassword=<desired_password>
rpcallowip=<ip_of_your_miner>
server=1
listen=0
upnp=0
connect=ambercoin01.mooo.com

If you are using the daemon instead of the Qt GUI Wallet, make sure the following is present no matter what above option you choose:

Code:

rpcuser=<desired_username>
rpcpassword=<desired_password>
daemon=1

[exemplaar]

AmberCoin.conf file setups (assuming use with Qt GUI Wallet):

No Solo-Mining:

Code:

upnp=0
listen=0
connect=ambercoin01.mooo.com

Solo-Mining:

Code:

rpcuser=<desired_username>
rpcpassword=<desired_password>
rpcallowip=<ip_of_your_miner>
server=1
listen=0
upnp=0
connect=ambercoin01.mooo.com

If you are using the daemon instead of the Qt GUI Wallet, make sure the following is present no matter what above option you choose:

Code:

rpcuser=<desired_username>
rpcpassword=<desired_password>
daemon=1

Thank you. 
This is very helpful post.

Regarding upnp=0
If you do not want to edit .conf file then in your ambercoin wallet click settings, options, network and make sure that option "map port using UPNP" is unchecked. 
   

[Mig-23]

stuck again

i just closed my wallet too see what happens next

waiting the final solutions of all this

[Slydrule]

Last DEBUG info from ambercoin01.mooo.com.
Maybe would be helpful.

getblocks stopping at limit 319039 000000001e9e81e56405
accepted connection 81.88.143.194:58254
getblocks 13920 to 000000002177ca4f7aa4 limit 500
  getblocks stopping at limit 14419 0000000000e17c6c14e5
partner 81.88.143.194:58254 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 81.88.143.194:58254
connection from 113.161.128.181:64841 dropped (banned)
getblocks 318540 to c184b39662b4c2b46b3b limit 500
  getblocks stopping at 318975 c184b39662b4c2b46b3b
connection from 71.187.62.42:56790 dropped (banned)
connection timeout
accepted connection 176.107.192.2:61021
partner 176.107.192.2:61021 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 176.107.192.2:61021
trying connection 108.61.174.143:31982 lastseen=1.2hrs
connection from 85.214.23.49:38378 dropped (banned)
connection from 213.180.26.45:53289 dropped (banned)
connection from 212.83.176.222:50699 dropped (banned)
connection from 213.180.26.34:54001 dropped (banned)
getblocks 598600 to 00000000ec75c4beed3d limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
getblocks 598600 to 00000000059cd7afbae2 limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
received getdata (12 invsz)
connection from 113.161.128.181:64842 dropped (banned)

I'm in there.  How long is the bantime?  I'll shutdown and wait until I've done my penance before resyncing again.

Thanks.  This was the info I needed.

[Fuzzbawls]

I'm in there.  How long is the bantime?  I'll shutdown and wait until I've done my penance before resyncing again.

Thanks.  This was the info I needed.

looks like the default ban time is 86400 seconds (24 hours).

https://github.com/AmberCoinDev/Amber/blob/master/src/net.cpp#L594
https://github.com/AmberCoinDev/Amber/blob/master/src/init.cpp#L259

[Slydrule]

I'm in there.  How long is the bantime?  I'll shutdown and wait until I've done my penance before resyncing again.

Thanks.  This was the info I needed.

looks like the default ban time is 86400 seconds (24 hours).

https://github.com/AmberCoinDev/Amber/blob/master/src/net.cpp#L594
https://github.com/AmberCoinDev/Amber/blob/master/src/init.cpp#L259

24 hours!?  Ouch!  Was I that bad? 

[verycoinsuchlist]

I'm in there.  How long is the bantime?  I'll shutdown and wait until I've done my penance before resyncing again.

Thanks.  This was the info I needed.

looks like the default ban time is 86400 seconds (24 hours).

https://github.com/AmberCoinDev/Amber/blob/master/src/net.cpp#L594
https://github.com/AmberCoinDev/Amber/blob/master/src/init.cpp#L259

dang! that's some waiting hours and a half... but I suppose a lot of people would get away with just restarting their routers and retrieving  a different ip from their provider...

24 hours!?  Ouch!  Was I that bad?  

even worse! even heard about santa not coming to town this year because of you! 

[Fuzzbawls]

24 hours!?  Ouch!  Was I that bad? 

even worse! even heard about santa not coming to town this year because of you! 

yeah...you killed Christmas!

[Fuzzbawls]

getblockbynumber 600315
"proofhash" : "0000000075bb366a563a67411b42306397c38b0f93bd566d6deda464289a14ba"

[PowerHemp]

getblockbynumber 600367

"proofhash" : "000bcdf2a47db1553cb03c563846a19fa090e38010b4352870d2b500ef1d84fe"

is that correct?

[binmon]

Wow, I think I forked again...and I was locked exclusively on ambercoin01.mooo.com ?

My wallet suddenly started getting all these POS rewards.  Not sure if that's what caused the disconnect, or the disconnect caused all the POS rewards.


trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=600315, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com
trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=600315, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com
trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=600315, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed


Can someone check this proofhash please?  I'm up to block 600,315

getblockbynumber 600315
"proofhash" : "0001d3f8dd5131685b470730a4f42f1a05eec77492f99a654818bfeceb9368c8",

Exactly same thing happened to me...  even just using the one node  (i did have it set to "addnode" versus "connect", so I'm blaming that.... guess I'll see you in 24 hours, lol.

BUT, it begs the question:  How much long is this going to continue?  Is a new wallet indicated, or is that a solution?   This is already old, like me. 

[Fuzzbawls]

getblockbynumber 600367

"proofhash" : "000bcdf2a47db1553cb03c563846a19fa090e38010b4352870d2b500ef1d84fe"

is that correct?

getblockbynumber 600367
"proofhash" : "000000006937c4f1a22ffea48af494e3eefcdc2cf76f439ff7a420981bf9c107"

Thats what I have, and still connected to the main node

[PowerHemp]

getblockbynumber 600367

"proofhash" : "000bcdf2a47db1553cb03c563846a19fa090e38010b4352870d2b500ef1d84fe"

is that correct?

getblockbynumber 600367
"proofhash" : "000000006937c4f1a22ffea48af494e3eefcdc2cf76f439ff7a420981bf9c107"

Thats what I have, and still connected to the main node

i dont understand..


getblockbynumber 600315
"proofhash" : "0000000075bb366a563a67411b42306397c38b0f93bd566d6deda464289a14ba"
there is all fine..