Not connecting to peers

[KaloyanDDimitrov]

Hello, I have installed auroracoin-cli on Ubuntu 18.04 LTS x64. It has been online for hours and it is not connecting to peers and not downloading the block chain.

This is form my debug.log 2022-05-05T15:18:03Z Auroracoin version v2021.01.2.0-a1425f14 (release build) 2022-05-05T15:18:03Z Assuming ancestors of block 6495a84f8f83981a435a6cbf9e6dd4bf0f38618c8325213ca6ef6add40c0ddd8 have valid signatures. 2022-05-05T15:18:03Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000000000000000000000000 2022-05-05T15:18:03Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation 2022-05-05T15:18:03Z Using RdRand as an additional entropy source 2022-05-05T15:18:03Z Default data directory /root/.auroracoin 2022-05-05T15:18:03Z Using data directory /root/.auroracoin 2022-05-05T15:18:03Z Config file: /root/.auroracoin/auroracoin.conf 2022-05-05T15:18:03Z Using at most 64 automatic connections (1024 file descriptors available) 2022-05-05T15:18:03Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2022-05-05T15:18:03Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2022-05-05T15:18:03Z Using 4 threads for script verification 2022-05-05T15:18:03Z scheduler thread start 2022-05-05T15:18:03Z HTTP: creating work queue of depth 16 2022-05-05T15:18:03Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2022-05-05T15:18:03Z HTTP: starting 4 worker threads 2022-05-05T15:18:03Z Using wallet directory /root/.auroracoin 2022-05-05T15:18:03Z init message: Verifying wallet(s)... 2022-05-05T15:18:03Z Using BerkeleyDB version Berkeley DB 5.3.28: (September 9, 2013) 2022-05-05T15:18:03Z Using wallet /root/.auroracoin 2022-05-05T15:18:03Z BerkeleyEnvironment::Open: LogDir=/root/.auroracoin/database ErrorFile=/root/.auroracoin/db.log 2022-05-05T15:18:03Z init message: Loading banlist... 2022-05-05T15:18:03Z ERROR: DeserializeFileDB: Failed to open file /root/.auroracoin/banlist.dat 2022-05-05T15:18:03Z Invalid or missing banlist.dat; recreating 2022-05-05T15:18:03Z Selected Algo: scrypt 2022-05-05T15:18:03Z Cache configuration: 2022-05-05T15:18:03Z Using 2.0 MiB for block index database 2022-05-05T15:18:03Z Using 56.0 MiB for transaction index database 2022-05-05T15:18:03Z Using 8.0 MiB for chain state database 2022-05-05T15:18:03Z Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2022-05-05T15:18:03Z init message: Loading block index... 2022-05-05T15:18:03Z Opening LevelDB in /root/.auroracoin/blocks/index 2022-05-05T15:18:03Z Opened LevelDB successfully 2022-05-05T15:18:03Z Using obfuscation key for /root/.auroracoin/blocks/index: 0000000000000000 2022-05-05T15:18:03Z LoadBlockIndexDB: last block file = 0 2022-05-05T15:18:03Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01) 2022-05-05T15:18:03Z Checking all blk files are present... 2022-05-05T15:18:03Z LoadBlockIndexDB: address index disabled 2022-05-05T15:18:03Z LoadBlockIndexDB: timestamp index disabled 2022-05-05T15:18:03Z LoadBlockIndexDB: spent index disabled 2022-05-05T15:18:03Z Initializing databases... 2022-05-05T15:18:03Z Pre-allocating up to position 0x1000000 in blk00000.dat 2022-05-05T15:18:03Z Opening LevelDB in /root/.auroracoin/chainstate 2022-05-05T15:18:03Z Opened LevelDB successfully 2022-05-05T15:18:03Z Wrote new obfuscate key for /root/.auroracoin/chainstate: a72bc04df5303d78 2022-05-05T15:18:03Z Using obfuscation key for /root/.auroracoin/chainstate: a72bc04df5303d78 2022-05-05T15:18:03Z init message: Rewinding blocks... 2022-05-05T15:18:03Z block index 7ms 2022-05-05T15:18:03Z Opening LevelDB in /root/.auroracoin/indexes/txindex 2022-05-05T15:18:03Z Opened LevelDB successfully 2022-05-05T15:18:03Z Using obfuscation key for /root/.auroracoin/indexes/txindex: 0000000000000000 2022-05-05T15:18:03Z init message: Loading wallet... 2022-05-05T15:18:03Z txindex thread start 2022-05-05T15:18:03Z txindex is enabled 2022-05-05T15:18:03Z txindex thread exit 2022-05-05T15:18:03Z BerkeleyEnvironment::Open: LogDir=/root/.auroracoin/database ErrorFile=/root/.auroracoin/db.log 2022-05-05T15:18:03Z [default wallet] Wallet File Version = 10500 2022-05-05T15:18:03Z [default wallet] Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total. Unknown wallet records: 0 2022-05-05T15:18:03Z [default wallet] Performing wallet upgrade to 169900 2022-05-05T15:18:04Z [default wallet] keypool added 2000 keys (1000 internal), size=2000 (1000 internal) 2022-05-05T15:18:04Z [default wallet] Wallet completed loading in 973ms 2022-05-05T15:18:04Z [default wallet] setKeyPool.size() = 2000 2022-05-05T15:18:04Z [default wallet] mapWallet.size() = 0 2022-05-05T15:18:04Z [default wallet] mapAddressBook.size() = 0 2022-05-05T15:18:04Z UpdateTip: new best=2a8e100939494904af825b488596ddd536b3a96226ad02e0f7ab7ae472b27a8e height=0 version=0x00000001 algo=1 (scrypt) log2_work=20.000001 tx=1 date='2014-01-24T21:26:46Z' progress=0.000000 cache=0.0MiB(0txo) 2022-05-05T15:18:04Z block tree size = 1 2022-05-05T15:18:04Z nBestHeight = 0 2022-05-05T15:18:04Z Failed to open mempool file from disk. Continuing anyway. 2022-05-05T15:18:04Z torcontrol thread start 2022-05-05T15:18:04Z AddLocal(192.248.147.241:12340,1) 2022-05-05T15:18:04Z Discover: IPv4 enp1s0: 192.248.147.241 2022-05-05T15:18:04Z AddLocal([2001:19f0:7402:bdc:5400:3ff:fef4:6ef0]:12340,1) 2022-05-05T15:18:04Z Discover: IPv6 enp1s0: 2001:19f0:7402:bdc:5400:3ff:fef4:6ef0 2022-05-05T15:18:04Z Bound to 127.0.0.1:12340 2022-05-05T15:18:04Z init message: Loading P2P addresses... 2022-05-05T15:18:04Z ERROR: DeserializeFileDB: Failed to open file /root/.auroracoin/peers.dat 2022-05-05T15:18:04Z Invalid or missing peers.dat; recreating 2022-05-05T15:18:04Z init message: Starting network threads... 2022-05-05T15:18:04Z net thread start 2022-05-05T15:18:04Z dnsseed thread start 2022-05-05T15:18:04Z Loading addresses from DNS seed electrum4.auroracoin.is 2022-05-05T15:18:04Z addcon thread start 2022-05-05T15:18:04Z init message: Done loading 2022-05-05T15:18:04Z opencon thread start 2022-05-05T15:18:04Z msghand thread start 2022-05-05T15:18:04Z Loading addresses from DNS seed electrum1.auroracoin.is 2022-05-05T15:18:04Z Loading addresses from DNS seed electrum2.auroracoin.is 2022-05-05T15:18:04Z Loading addresses from DNS seed electrum3.auroracoin.is 2022-05-05T15:18:04Z 0 addresses found from DNS seeds 2022-05-05T15:18:04Z dnsseed thread exit 2022-05-05T15:19:05Z Adding fixed seed nodes as DNS doesn't seem to be available. 2022-05-05T15:26:46Z [default wallet] keypool reserve 1 2022-05-05T15:26:46Z [default wallet] keypool keep 1 2022-05-05T15:29:18Z Potential stale tip detected, will try using extra outbound peer (last tip update: 674 seconds ago) 2022-05-05T15:39:48Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1304 seconds ago) 2022-05-05T15:50:18Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1934 seconds ago)

[BioMike]

Seed nodes were shutdown, not sure how that happened. I've restarted them. Problem should be fixed now.

[KaloyanDDimitrov]

Seed nodes were shutdown, not sure how that happened. I've restarted them. Problem should be fixed now.

Thanks. It is fixed now.

[KaloyanDDimitrov]

Hello, I have again the same problem with peers. @BioMike Can you restart them again?

[BioMike]

It seems that the cloud provider for the seed nodes suspended the account, that the Auroracoin foundation/IBF paid for, due to missed payments. I mailed them yesterday, but no resonse from them yet.

[BioMike]

I've added my ip address to the wiki, people can connect to that to get a peer list. Do note that this node is not always online. I'll see if I can update this list with more ip addresses within the next few days.

It's far from perfect, but should work for now.

[auroracoin101]

In regards to the existing/previous servers paid for by the IBF (Icelandic Blockchain Foundation) there was a conflict or confusion in relation to use of IBF funds and Auroracoin servers. I am working with both the previous team members and IBF to resolve payment situations for the future.

For now though I will be funding necessary infrastructure servers for Auroracoin ( in partnership with other stakeholders, such as CommunityCoins.org and a South African blockchain coalition that supports Auroracoin growth)

Anyone may email me at m.hannes@auroracoin.is for further information. With kind regards, Mikael Hannes

[auroracoin101]

Process for adding peernodes from within the QT-wallet:

NODE LIST> ( You can find live network nodes at https://chainz.cryptoid.info/aur/#!network

• Click the top Node list with most connections.
  /rni Magnsson:2021.01.2.0/ | node list | 3020191 | 34 )

1) Open the Auroracoin Qt-wallet 2) Wait for the splash screen to close after initial loading process. 3) You will see a synchronization screen indicating the number of blocks "behind" that need to load. 4) If there is no progress or activity after 30 seconds or so ( depending on internet connection, give it a couple minutes)... a) If there is no activity it could indicate the wallet cannot locate a peer to begin synchronizing. b) From top system menu, Select Window | Peers - if the list is empty than this is the issue. c) ( I suppose if there are peers listed but the blockchain is not synchronizing you should continue these instructions ) 5) From the top system menu, select Window | Console 6) You will see a command line input at the bottom of the screen, this is where you will add peer nodes. 7) I am providing here a list of known peer nodes, good as of June 18 2022. See NODE LIST section above for more

in the command line box at bottom of screen type the following and press :
addnode 84.28.5.90 add

You will see this command reflected in the console history, with a response of "null". This indicates success.

8) If you click on the Peers tab, after a few moments, you should see the peer show up and then more over time.

More valid peers:

again, go to Window | Console and type the following addnode 157.161.128.56 add addnode 62.171.189.219 add

Notes: In the Console window you can type in addnode by itself to see instructions on the command.

You will see that technically the command addnode expects quotations around the ipaddress and command, addnode "node" "command"

However atleast in the Windows client the quotations are not needed.

Respectfully, Mikael Hannes Auroracoin Project Team

ps. We are working on setting up more Seed servers which will be provided in the default installation with the next version of the core wallet in development.

Again, if you have any questions feel free to email me at m.hannes@auroracoin.is

[BioMike]

I've updated the seed node list with the list suggested by Mikael, will try to provide new release/binaries soon.

[BioMike]

I've just published a new release that contains an updates seed node list. Please check it out.

[dbkeys]

As a work-around, if anybody is looking for current, active, real-time Auroracoin nodes: https://chainetics.com/AUR-nodes.php

[auroracoin101]

I was testing building and syncing the auroracoin node using the latest aurarad/master.

Not sure if it was able to use the DNS seed dnsseed.auroracoin.cc based on the messages that followed.

However once i did use dnsseed.auroracoin.cc using "addnode dnsseed.auroracoin.cc add" and after a while it did start bringing in transactions.

Just wanted to document this. ~/michael

2024-09-22T17:24:46Z Loading addresses from DNS seed dnsseed.auroracoin.cc 2024-09-22T17:24:46Z init message: Done loading 2024-09-22T17:24:46Z msghand thread start 2024-09-22T17:24:46Z Loading addresses from DNS seed electrum1.auroracoin.is 2024-09-22T17:24:47Z Loading addresses from DNS seed electrum3.auroracoin.is 2024-09-22T17:24:47Z Loading addresses from DNS seed electrum4.auroracoin.is 2024-09-22T17:24:47Z Loading addresses from DNS seed electrum2.auroracoin.is 2024-09-22T17:24:47Z 0 addresses found from DNS seeds 2024-09-22T17:24:47Z dnsseed thread exit 2024-09-22T17:25:47Z Adding fixed seed nodes as DNS doesn't seem to be available. 2024-09-22T17:25:58Z New outbound peer connected: version: 3020191, blocks=4825841, peer=0 (full-relay) 2024-09-22T17:25:59Z nActualTimespan = 1867 before bounds