Monero Support

[TaurusBit]

I'm just checking all options here.... you have the port open, right? if this is ubuntu, sudo ufw allow 8082

UFW is disabled, I'm using CSF but simplewallet won't listen on the port even with CSF disabled.

hrm. I'm trying to find some log files for my simplewallet that I've used like this, but I think its on another device that is off right now. I'm not 100% sure, but what you might be experiencing is the fact that simplewallet might have to refresh your wallet. A wallet refresh, even on a brand new wallet, can take a while.

as with all things Monero, patience is your best resource.

So, my advice - set it to port 8082, and keep an eye on the log file or on the screen session and see when the status changes. Indeed, I think i recall seeing the final log entry being something like "listening on port blah blah blah". so if the above was the extent of your log for simplewallet, that means the wallet didn't finish refreshing.

Thanks for the suggestion. This should be mentioned in the Developer docs..

Code:

monero@server:~$ netstat -nat | grep 8082
tcp        0      0 0.0.0.0:8082            0.0.0.0:*               LISTEN

Apparently it took around 1h30m for simplewallet to sync..

Code:

2016-Feb-29 15:25:53.836768 Loaded wallet keys file, with public address: [....]
2016-Feb-29 17:08:00.210981 Loaded ok

It's listening now!  

[birr]

I started up bitmonerod.  Thanks to all who helped.
It's doing something but I have no idea what, so I am going to describe it.
Maybe you can tell me if it's working right.
Many lines are scrolling by.  Each line has the date and time, followed by
[P2P_][92.222.201.247:18080 OUT]Synced _____/______
where the underscores represent numbers that change on each line.
Just now, the contents of the second set of brackets changed to
[37.59.53.25:18080 OUT]
Every so often the LMDB memory map size gets increased.

Late breaking news:  I got a line that reads
2016-Feb-29 20:50:04.767999 [P2P7]WARNING: No two valid MoneroPulse DNS checkpoint records were received

[nioc]

I started up bitmonerod.  Thanks to all who helped.
It's doing something but I have no idea what, so I am going to describe it.
Maybe you can tell me if it's working right.
Many lines are scrolling by.  Each line has the date and time, followed by
[P2P_][92.222.201.247:18080 OUT]Synced _____/______
where the underscores represent numbers that change on each line.
Just now, the contents of the second set of brackets changed to
[37.59.53.25:18080 OUT]
Every so often the LMDB memory map size gets increased.

Late breaking news:  I got a line that reads
2016-Feb-29 20:50:04.767999 [P2P7]WARNING: No two valid MoneroPulse DNS checkpoint records were received

When syncing from scratch and you will get what you described.  How long it takes is dependent on your hardware with AFAIK the biggest factor being whether you have a HD or SSD.

I am unsure of the warning but I don't believe it is anything to be concerned about.

Disclaimer: Even though I am clueless compared to anybody else helping you here, I figured you needed a timely response .  Hopefully somebody else can chime in.

[birr]

I have two and a half hours left before the University library closes for the night.  I am using the Uni wifi because that's the fastest connection available to me.
If bitmonerod is still syncing when the library closes, how do I shut it down without losing what I've downloaded so far?

[smooth]

I have two and a half hours left before the University library closes for the night.  I am using the Uni wifi because that's the fastest connection available to me.
If bitmonerod is still syncing when the library closes, how do I shut it down without losing what I've downloaded so far?

Cross post:

Just type exit in the bitmonerod window and it will close the database cleanly so you don't lose anything. You can restart from there and it will continue where it left off.

[GingerAle]

I'm just checking all options here.... you have the port open, right? if this is ubuntu, sudo ufw allow 8082

UFW is disabled, I'm using CSF but simplewallet won't listen on the port even with CSF disabled.

hrm. I'm trying to find some log files for my simplewallet that I've used like this, but I think its on another device that is off right now. I'm not 100% sure, but what you might be experiencing is the fact that simplewallet might have to refresh your wallet. A wallet refresh, even on a brand new wallet, can take a while.

as with all things Monero, patience is your best resource.

So, my advice - set it to port 8082, and keep an eye on the log file or on the screen session and see when the status changes. Indeed, I think i recall seeing the final log entry being something like "listening on port blah blah blah". so if the above was the extent of your log for simplewallet, that means the wallet didn't finish refreshing.

Thanks for the suggestion. This should be mentioned in the Developer docs..

Code:

monero@server:~$ netstat -nat | grep 8082
tcp        0      0 0.0.0.0:8082            0.0.0.0:*               LISTEN

Apparently it took around 1h30m for simplewallet to sync..

Code:

2016-Feb-29 15:25:53.836768 Loaded wallet keys file, with public address: [....]
2016-Feb-29 17:08:00.210981 Loaded ok

It's listening now!  

Would you mind pointing me to these "developer docs" so they may be updated? I don't know what is considered the goto for developers.

[birr]

I am new, have been running bitmonerod for just a couple of days.
I have to use wifi, and it took eleven hours downloading time, even though I have an ssd.
I am getting a new computer, and would like to save time by transferring the Monero blockchain directly from my old computer to the new one, or onto a flash drive first and then to the new computer.
How would you go about doing this?
My present computer is 32bit, running ubuntu 14.04.
I am going to buy a new 64bit chromebook and install linux on it, and run a monero node.

[smooth]

I am new, have been running bitmonerod for just a couple of days.
I have to use wifi, and it took eleven hours downloading time, even though I have an ssd.
I am getting a new computer, and would like to save time by transferring the Monero blockchain directly from my old computer to the new one, or onto a flash drive first and then to the new computer.
How would you go about doing this?
My present computer is 32bit, running ubuntu 14.04.
I am going to buy a new 64bit chromebook and install linux on it, and run a monero node.

The best way is to use the blockchain_export utility to create a .raw file, copy that to the new computer, then use the blockchain_import utility on the new computer.

It might be possible copy the database files (I don't remember if they are portable between 32 bit and 64 bit) but the above will double check everything and make sure everything is properly validated on the new computer. It will take some processing time (let it run overnight), but not bandwidth.

[birr]

I typed ./blockchain_export and got this

can't load blockchain storage from file, generating genesis block.
Segmentation fault (core dumped).

No .raw file.  The export was supposed to go to home/a/.bitmonero/export/blockchain.raw
The .bitmonero directory contains
bitmonero.log dump lmdb p2pstate.bin poolstate.bin

I now have a 7.3 Meg executable file named blockchain_dump in my main monero directory, not sure if it was there before.

[smooth]

I typed ./blockchain_export and got this

can't load blockchain storage from file, generating genesis block.
Segmentation fault (core dumped).

No .raw file.  The export was supposed to go to home/a/.bitmonero/export/blockchain.raw
The .bitmonero directory contains
bitmonero.log dump lmdb p2pstate.bin poolstate.bin

I now have a 7.3 Meg executable file named blockchain_dump in my main monero directory, not sure if it was there before.

Sorry, it turns out that the blockchain utilities are currently hard coded to use the old memory format as an input. If you want to create a .raw file from a database you will have to change this line:

#define SOURCE_DB DB_MEMORY

to this:

#define SOURCE_DB DB_LMDB

And then recompile.

If you aren't prepared to recompile, you will have to wait until this gets addressed in a new release.

You can also sync the new computer exclusively from the old one (won't use any external bandwidth if they are both on the same network) by launching it with:

bitmonerod --add-exclusive-node ip-address-of-old-computer:18080 --p2p-bind-port 127.0.0.1

Once it syncs you can exit and relaunch normally.

[persiancat]

I started bitmonerod a while ago and my computer had a hard crash (blue screen).

After restarting my computer, initializing bitmonerod again, and it showed the below error message

http://postimg.org/image/82k0rxkeh/

Can I know what went wrong and how can I resolve this issue?

Thanks very much in advance.


EDIT : Ok I redownloaded the latest snapshot of blockchain.raw.

1. Can someone provide guidance on how to use blockchain_import.exe to convert the blockchain.raw file?

2. Can I confirm that the converted blockchain is "data.mdb" and that its supposed to be placed inside C:\ProgramData\bitmonero\lmdb?

[GingerAle]

I started bitmonerod a while ago and my computer had a hard crash (blue screen).

After restarting my computer, initializing bitmonerod again, and it showed the below error message



Can I know what went wrong and how can I resolve this issue?

Thanks very much in advance.


EDIT : Ok I redownloaded the latest snapshot of blockchain.raw.

1. Can someone provide guidance on how to use blockchain_import.exe to convert the blockchain.raw file?

2. Can I confirm that the converted blockchain is "data.mdb" and that its supposed to be placed inside C:\ProgramData\bitmonero\lmdb?

Ultimately its better and faster to sync from the network.

[equipoise]

I started bitmonerod a while ago and my computer had a hard crash (blue screen).

After restarting my computer, initializing bitmonerod again, and it showed the below error message



Can I know what went wrong and how can I resolve this issue?

Thanks very much in advance.


EDIT : Ok I redownloaded the latest snapshot of blockchain.raw.

1. Can someone provide guidance on how to use blockchain_import.exe to convert the blockchain.raw file?

2. Can I confirm that the converted blockchain is "data.mdb" and that its supposed to be placed inside C:\ProgramData\bitmonero\lmdb?

Delete the blockchain folder and try again. If you have more then one hdd it's better/faster to use different hdd for the blockchain folder - start bitmoneod with the --data-dir option. I also use --db-sync-mode option for faster sync:

Code:

bitmonerod --data-dir O:\MONERO_blockchain --db-sync-mode fastest:async:12000

As GingerAle said it's faster to sync from the network, not from the raw file. Also since there were some changes in the database format recently the raw import may not work in the current version (I'm not sure about that).

[molecular]

I'm having problems with slow sync:

2016-Mar-05 09:39:56.820168 [P2P8][104.156.227.151:18080 OUT]Sync data returned unknown top block: 77001 -> 983848 [906847 blocks (629 days) behind]
[...]
2016-Mar-05 10:22:10.066426 [P2P3][90.161.84.133:34954 INC]Sync data returned unknown top block: 83401 -> 983899 [900498 blocks (625 days) behind]

So it takes 40 minutes to sync 6,500 blocks? Is that normal?

There's only negligible IO happening (.bitmonero folder in on SSD drive)

My 8 Mbit/s network downstream is completely saturated. This seems to be an awful lot of data: in 40 minutes that'd amount to 2.4 GB, while .bitmonerod folder only grew by roughly 0.5 GB (from 2.8 to 3.3 GB).

So what's up with that? Is monero downloading the blocks in parallel from multiple sources or something? Looks like that in the logfile:

2016-Mar-05 10:26:44.428558 [P2P0][62.210.245.87:54353 INC]Synced 84001/983911
2016-Mar-05 10:26:48.009175 [P2P6][104.152.213.138:56072 INC]Sync data returned unknown top block: 84001 -> 983911 [899910 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:09.699536 [P2P6][101.109.248.25:56177 INC]Sync data returned unknown top block: 84001 -> 983911 [899910 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:13.870784 [P2P4][188.134.79.203:60708 INC]Sync data returned unknown top block: 84001 -> 983911 [899910 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:15.405013 [P2P9][222.177.26.238:55204 INC]Sync data returned unknown top block: 84001 -> 983911 [899910 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:17.439811 [P2P2][128.199.179.100:41131 INC]Sync data returned unknown top block: 84001 -> 983911 [899910 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:19.690642 [P2P3][198.27.81.114:64382 INC]Sync data returned unknown top block: 84001 -> 983912 [899911 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:22.665916 [P2P2][85.72.182.211:55128 INC]Sync data returned unknown top block: 84001 -> 983912 [899911 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:35.236801 [P2P4][142.161.50.93:40308 INC]Sync data returned unknown top block: 84001 -> 983912 [899911 blocks (624 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:27:36.904338 [P2P9][104.42.131.205:1322 INC]Sync data returned unknown top block: 84001 -> 983912 [899911 blocks (624 days) behind]

Can I reduce the bandwidth demand of the sync process somehow?

EDIT: I'm lost... I tried:

build/release/bin/bitmonerod --out-peers 1 --add-exclusive-node 216.130.237.88:45686 --limit-rate-down 6000 --db-sync-mode fast:sync:10000

but it seems to ignore my cmdline options:

• still saturates 8MBit downstream (should be limited to 6, no?)
• still connects to different nodes, getting multiple "data returned" message with different IP and same block height)
• does not seem to connect to the given IP
• sync still slow as f..k

what am I doing wrong?

[smooth]

Can I reduce the bandwidth demand of the sync process somehow?

Yes:

1. Download the blockchain.raw bootstrap and import it using blockchain_import

or

2. Pick one peer and use --add-exclusive-node peer --p2p-bind-ip 127.0.0.1 for initial sync, then restart normally.

There is a certain amount of redundant downloading from multiple peers (specific depend on network conditions, your node performance, etc.). Either of the above will eliminate it.

So it takes 40 minutes to sync 6,500 blocks? Is that normal?

That is absolutely not normal, especially with an SSD. Are you sure you don't have something else using up CPU/RAM. I can sync almost the whole chain in 40 minutes on a mobile i7.

[molecular]

Can I reduce the bandwidth demand of the sync process somehow?

Yes:

1. Download the blockchain.raw bootstrap and import it using blockchain_import

or

2. Pick one peer and use --add-exclusive-node peer --p2p-bind-ip 127.0.0.1 for initial sync, then restart normally.

There is a certain amount of redundant downloading from multiple peers (specific depend on network conditions, your node performance, etc.). Either of the above will eliminate it.

So it takes 40 minutes to sync 6,500 blocks? Is that normal?

That is absolutely not normal, especially with an SSD. Are you sure you don't have something else using up CPU/RAM. I can sync almost the whole chain in 40 minutes on a mobile i7.

Thanks for your tips.

RAM: 10 GB free, CPU: 4 cpus at 10% load on avg.

I just started using

bitmonerod --out-peers 1 --add-exclusive-node 219.159.104.219:59704 --limit-rate-down 6000 --db-sync-mode fast:sync:10000

It still syncs from different peers (using "--p2p-bind-ip 127.0.0.1" resulted in no network activity, I had hope for that one helping to limit connections to 1 peer), but now the log looks different. I think using snychronous db-sync-mode did the trick:

2016-Mar-05 10:45:06.376823 [P2P8][62.210.245.87:33885 INC]Synced 93601/983931
2016-Mar-05 10:45:10.431624 [P2P6][62.210.245.87:33885 INC]Synced 93801/983931
2016-Mar-05 10:45:15.197708 [P2P1][62.210.245.87:33885 INC]Synced 94001/983930
2016-Mar-05 10:45:22.764763 [P2P7][62.210.245.87:33885 INC]Synced 94201/983930
2016-Mar-05 10:45:29.579743 [P2P6][62.210.245.87:33885 INC]Synced 94401/983930
2016-Mar-05 10:45:35.793358 [P2P9][62.210.245.87:33885 INC]Synced 94601/983931
2016-Mar-05 10:45:43.844316 [P2P9][62.210.245.87:33885 INC]Synced 94801/983931
2016-Mar-05 10:45:52.093073 [P2P2][62.210.245.87:33885 INC]Synced 95001/983930
2016-Mar-05 10:45:53.243136 [P2P3][73.8.137.244:55437 INC]Sync data returned unknown top block: 95001 -> 981505 [886504 blocks (615 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:45:58.458835 [P2P5][173.255.220.42:4587 INC]Sync data returned unknown top block: 95001 -> 449346 [354345 blocks (246 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:45:58.520588 [P2P8][123.3.223.110:37287 INC]Sync data returned unknown top block: 95001 -> 983933 [888932 blocks (617 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:46:03.703374 [P2P8][62.210.245.87:33885 INC]Synced 95201/983933
2016-Mar-05 10:46:17.463863 [P2P3][62.210.245.87:33885 INC]Synced 95401/983933
2016-Mar-05 10:46:18.889231 [P2P7][41.164.163.114:52465 INC]Sync data returned unknown top block: 95401 -> 983933 [888532 blocks (617 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:46:30.264306 [P2P4][62.210.245.87:33885 INC]Synced 95601/983933
2016-Mar-05 10:46:47.128749 [P2P8][62.210.245.87:33885 INC]Synced 95801/983933

Looks like the network was my bottleneck and how this is solved (no more parallel download)?

I can see 3 bitmonerod processes in iotop netting about 8 MB/s disk writes (averaged over 20s interval).

Seems to be looking much better now.

Not sure, though. Any info/hints are still appreciated.

(I will benchmark sync speed now and if it's still slow, I might resort to downloading a blockchain.raw)

[molecular]

ok, now it's looking great:

#> bitmonerod --add-exclusive-node 73.8.137.244:49995 --limit-rate-down 6000 --db-sync-mode fastest:async:10000

[...]

SYNCHRONIZATION started
2016-Mar-05 11:03:09.898896 [P2P7][77.50.236.95:12878 INC]Synced 115801/455288
2016-Mar-05 11:03:12.124378 [P2P8][77.50.236.95:12878 INC]Synced 116001/455288
2016-Mar-05 11:03:14.992277 [P2P7][77.50.236.95:12878 INC]Synced 116201/266664
2016-Mar-05 11:03:17.050969 [P2P2][77.50.236.95:12878 INC]Synced 116401/266664
2016-Mar-05 11:03:19.381323 [P2P6][77.50.236.95:12878 INC]Synced 116601/266664
2016-Mar-05 11:03:21.414904 [P2P2][77.50.236.95:12878 INC]Synced 116801/266664
2016-Mar-05 11:03:24.279571 [P2P8][77.50.236.95:12878 INC]Synced 117001/266664
2016-Mar-05 11:03:26.835850 [P2P8][77.50.236.95:12878 INC]Synced 117201/266664
2016-Mar-05 11:03:29.308303 [P2P7][77.50.236.95:12878 INC]Synced 117401/672219
2016-Mar-05 11:03:32.102482 [P2P0][77.50.236.95:12878 INC]Synced 117601/983954
2016-Mar-05 11:03:34.469062 [P2P3][77.50.236.95:12878 INC]Synced 117801/983954
2016-Mar-05 11:03:37.015512 [P2P3][77.50.236.95:12878 INC]Synced 118001/983954
2016-Mar-05 11:03:38.697902 [P2P7][77.50.236.95:12878 INC]Synced 118201/983954
[...]
2016-Mar-05 11:06:28.340904 [P2P6][212.119.171.2:55573 INC]Synced 130000/983956

(it seems to be switching that peer from time to time)

downstream isn't saturated any more, either. around 4-5 MBit/s.

That's about 70 blocks/s. Should take ~3 hours to sync at that speed. Much better than the week I was looking at before. Still not sure why it was THAT slow before. Suspecting network clog (700 kbit/s upstream wasn't ever saturated, though)

io disk write is around 10 MB/s on 2-3 threads.

[smooth]

using "--p2p-bind-ip 127.0.0.1" resulted in no network activity

That means your outgoing connection to the exclusive node did not work. Either the node you chose isn't working any more or your node is having trouble with outgoing connections (firewall issue, etc.)

Your syncing appears to be happening on multiple incoming connections, which aren't so easily limited, but are easily blocked (using the above option):

2016-Mar-05 10:45:06.376823 [P2P8][62.210.245.87:33885 INC]Synced 93601/983931
2016-Mar-05 10:45:53.243136 [P2P3][73.8.137.244:55437 INC]Sync data returned unknown top block: 95001 -> 981505 [886504 blocks (615 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:45:58.458835 [P2P5][173.255.220.42:4587 INC]Sync data returned unknown top block: 95001 -> 449346 [354345 blocks (246 days) behind]
2016-Mar-05 10:46:18.889231 [P2P7][41.164.163.114:52465 INC]Sync data returned unknown top block: 95401 -> 983933 [888532 blocks (617 days) behind]

[molecular]

using "--p2p-bind-ip 127.0.0.1" resulted in no network activity

That means your outgoing connection to the exclusive node did not work. Either the node you chose isn't working any more or your node is having trouble with outgoing connections (firewall issue, etc.)

yes, I noticed that connecting to that node didn't work using "log_level 2" command (I also noticed that using "log_level 3" is rather ill-advised ;-))

Your syncing appears to be happening on multiple incoming connections, which aren't so easily limited, but are easily blocked (using the above option):

2016-Mar-05 10:45:06.376823 [P2P8][62.210.245.87:33885 INC]Synced 93601/983931
2016-Mar-05 10:45:53.243136 [P2P3][73.8.137.244:55437 INC]Sync data returned unknown top block: 95001 -> 981505 [886504 blocks (615 days) behind]
SYNCHRONIZATION started
2016-Mar-05 10:45:58.458835 [P2P5][173.255.220.42:4587 INC]Sync data returned unknown top block: 95001 -> 449346 [354345 blocks (246 days) behind]
2016-Mar-05 10:46:18.889231 [P2P7][41.164.163.114:52465 INC]Sync data returned unknown top block: 95401 -> 983933 [888532 blocks (617 days) behind]

I couldn't find a seednode list, so I ran without giving an exclusive node, but with "--out-peers 1 --p2p-bind-ip 127.0.0.1" with good success.

I was seeing different peer IPs in the log and "Sync data returned unknown top block" messages at first.
But then things settled down...

2016-Mar-05 12:26:59.188420 [P2P9][178.149.145.72:18080 OUT]Synced 204796/984054
2016-Mar-05 12:27:01.998728 [P2P1][178.149.145.72:18080 OUT]Synced 204996/984054
2016-Mar-05 12:27:03.205146 [P2P4][178.149.145.72:18080 OUT]Synced 205196/984054
2016-Mar-05 12:27:04.531189 [P2P5][178.149.145.72:18080 OUT]Synced 205396/984054
2016-Mar-05 12:27:05.854204 [P2P0][178.149.145.72:18080 OUT]Synced 205596/984054
2016-Mar-05 12:27:07.063295 [P2P9][178.149.145.72:18080 OUT]Synced 205796/984054
2016-Mar-05 12:27:08.891061 [P2P4][178.149.145.72:18080 OUT]Synced 205996/984054
2016-Mar-05 12:27:11.054276 [P2P6][178.149.145.72:18080 OUT]Synced 206196/984054
2016-Mar-05 12:27:14.411026 [P2P8][178.149.145.72:18080 OUT]Synced 206396/984054
2016-Mar-05 12:27:16.000495 [P2P2][178.149.145.72:18080 OUT]Synced 206596/984054
2016-Mar-05 12:27:17.489989 [P2P3][178.149.145.72:18080 OUT]Synced 206796/984054
2016-Mar-05 12:27:18.926391 [P2P0][178.149.145.72:18080 OUT]Synced 206996/984054
2016-Mar-05 12:27:20.878400 [P2P8][178.149.145.72:18080 OUT]Synced 207196/984054
2016-Mar-05 12:27:22.693849 [P2P2][178.149.145.72:18080 OUT]Synced 207396/984054
2016-Mar-05 12:27:24.343272 [P2P6][178.149.145.72:18080 OUT]Synced 207596/984054
2016-Mar-05 12:27:27.255623 [P2P2][178.149.145.72:18080 OUT]Synced 207796/984054
2016-Mar-05 12:27:29.877210 [P2P6][178.149.145.72:18080 OUT]Synced 207996/984054

sometimes it switches to a different peer like this:

2016-Mar-05 12:14:13.372133 [P2P9][95.91.125.54:18080 OUT]Synced 181798/984029
2016-Mar-05 12:14:48.709904 [P2P4][95.91.125.54:18080 OUT]Synced 181998/984029
2016-Mar-05 12:15:00.820519 [P2P3][95.91.125.54:18080 OUT]Synced 182198/984029
2016-Mar-05 12:15:13.241033 [P2P0][95.91.125.54:18080 OUT]Synced 182398/984029
2016-Mar-05 12:15:28.043966 [P2P5][95.91.125.54:18080 OUT]Synced 182598/984029
2016-Mar-05 12:15:35.608570 [P2P2][95.91.125.54:18080 OUT]Synced 182798/984029
2016-Mar-05 12:15:46.548866 [P2P0][95.91.125.54:18080 OUT]Synced 182998/984029
2016-Mar-05 12:15:52.262579 [P2P2][95.91.125.54:18080 OUT]Synced 183198/984029
2016-Mar-05 12:15:57.924032 [P2P3][95.91.125.54:18080 OUT]Synced 183398/984029
2016-Mar-05 12:16:08.627850 [P2P1][95.91.125.54:18080 OUT]Synced 183598/984029
2016-Mar-05 12:18:50.743105 [P2P6][178.149.145.72:18080 OUT]Sync data returned unknown top block: 183598 -> 984054 [800456 blocks (555 days) behind]
SYNCHRONIZATION started
2016-Mar-05 12:18:55.829213 [P2P9][178.149.145.72:18080 OUT]Synced 183798/984054
2016-Mar-05 12:18:58.220509 [P2P6][178.149.145.72:18080 OUT]Synced 183998/984054
2016-Mar-05 12:19:00.959168 [P2P4][178.149.145.72:18080 OUT]Synced 184198/984054
2016-Mar-05 12:19:03.836088 [P2P5][178.149.145.72:18080 OUT]Synced 184398/984054
2016-Mar-05 12:19:07.495440 [P2P9][178.149.145.72:18080 OUT]Synced 184598/984054
2016-Mar-05 12:19:11.584073 [P2P6][178.149.145.72:18080 OUT]Synced 184798/984054

anyway... I'm 50% synced and it's running like a charm at this point, so I'm happy.

thanks a lot for your help, smooth.

[GingerAle]

So whats the current best suggesting for syncing new node?

Code:

bitmonerod --add-exclusive-node 23.227.190.223:18080 --limit-rate-down 6000 --p2p-bind-ip 127.0.0.1 --db-sync-mode fastest:async:10000

This is a node hosted at a datacenter, funded by either the Monero community or one Monero community member, I forget which. The status of the node can be checked here:

https://bitnodes.net/node/23-227-190-223/

That port should work, right?