Monero Support

[explorer]

how are you starting mining.

If you are starting it in simplewallet, you can add a thread count after the command. For example:

start_mining 2

If you start it on the bitmonerod command line with "--start-mining address" then you can add "--mining-threads thread-count"

I will play with that. thanks.

tried various formations of that.  Success with running bitmonerod, then:

start_mining address 2


couldn't make it happen from simplewallet, probably just me, but figured to document it here in case there's any other noobs that can learn from it.

thanks

[equipoise]

how are you starting mining.

If you are starting it in simplewallet, you can add a thread count after the command. For example:

start_mining 2

If you start it on the bitmonerod command line with "--start-mining address" then you can add "--mining-threads thread-count"

I will play with that. thanks.

tried various formations of that.  Success with running bitmonerod, then:

start_mining address 2


couldn't make it happen from simplewallet, probably just me, but figured to document it here in case there's any other noobs that can learn from it.

thanks

You should run simplewallet with the "--trusted-daemon" switch in order to use "start_mining N" command.

[birr]

I'm running 32 bit Ubuntu 14 on a netbook with an SSD over public library wifi.
I need to download about another 155,000 blocks and not getting anywhere.  Just running bitmonerod without any flags is much too slow, so I tried some of the suggestions from this thread.  I tried a command that molecular posted for connecting to a single node and that didn't help.  I tried the --p2p-bind-ip 127.0.0.1 flag and that didn't help.  Just now I tried bitomonerod without any flags again:

Code:

a@a-1000H:~/monero.v0-9-1-1$ ./bitmonerod
Creating the logger system
2016-Mar-12 11:17:09.148477 Initializing cryptonote protocol...
2016-Mar-12 11:17:09.148892 Cryptonote protocol initialized OK
2016-Mar-12 11:17:09.150153 Initializing p2p server...
[1457799429] libunbound[4345:0] info: warning: unsupported algorithm for trust anchor . DS IN
[1457799429] libunbound[4345:0] warning: trust anchor . has no supported algorithms, the anchor is ignored (check if you need to upgrade unbound and openssl)
2016-Mar-12 11:17:12.960113 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.960951 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.961488 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.962204 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.968187 Binding on 0.0.0.0:18080
2016-Mar-12 11:17:12.968881 Net service bound to 0.0.0.0:18080
2016-Mar-12 11:17:12.969164 Attempting to add IGD port mapping.
2016-Mar-12 11:17:16.975016 No IGD was found.
2016-Mar-12 11:17:16.975391 P2p server initialized OK
2016-Mar-12 11:17:16.976533 Initializing core rpc server...
2016-Mar-12 11:17:16.977173 Binding on 127.0.0.1:18081
2016-Mar-12 11:17:16.977918 Core rpc server initialized OK on port: 18081
2016-Mar-12 11:17:16.978314 Initializing core...
2016-Mar-12 11:17:16.979770 Loading blockchain from folder /home/a/.bitmonero/lmdb ...
2016-Mar-12 11:17:16.980165 option: fastest
2016-Mar-12 11:17:16.980526 option: async
2016-Mar-12 11:17:16.980873 option: 1000
2016-Mar-12 11:17:17.447525 Blockchain initialized. last block: 839143, d109.h15.m4.s7 time ago, current difficulty: 785463195
2016-Mar-12 11:17:34.462371 WARNING: no two valid MoneroPulse DNS checkpoint records were received
2016-Mar-12 11:17:34.466477 Core initialized OK
2016-Mar-12 11:17:34.466986 Starting core rpc server...
2016-Mar-12 11:17:34.467432 Run net_service loop( 2 threads)...
2016-Mar-12 11:17:34.469203 [SRV_MAIN]Core rpc server started ok
2016-Mar-12 11:17:34.470473 [SRV_MAIN]Starting p2p net loop...
2016-Mar-12 11:17:34.471363 [SRV_MAIN]Run net_service loop( 10 threads)...
2016-Mar-12 11:17:35.471512 [P2P9]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).

Use "help" command to see the list of available commands.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2016-Mar-12 11:17:35.634786 [P2P7][108.28.24.179:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:36.091791 [P2P5][104.159.188.157:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.198821 [P2P4][104.233.75.221:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.780959 [P2P4][31.128.159.34:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:42.205319 [P2P9][76.173.170.133:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
exit
2016-Mar-12 11:18:32.217862 [node] Stop signal sent
Stop signal sent
exit
2016-Mar-12 11:20:18.539281 [node] Stop signal sent
Stop signal sent
2016-Mar-12 11:20:46.574322 [P2P7][108.28.24.179:18080 OUT]Synced 839344/994350
2016-Mar-12 11:20:46.574356 [P2P8][104.159.188.157:18080 OUT]Synced 839344/994350
save
Blockchain saved
exit
2016-Mar-12 11:21:12.569851 [node] Stop signal sent
Stop signal sent

Now it won't even exit.  I gave the command ten minutes ago.  So just for the hell of it I checked status:

Code:

status
Height: 839344/994350 (84.4%) on mainnet, mining at 604849015.99 GH/s, net hash 11.75 MH/s, v1, up to date, 6+0 connections

What to do, what to do...

[GingerAle]

I'm running 32 bit Ubuntu 14 on a netbook with an SSD over public library wifi.
I need to download about another 155,000 blocks and not getting anywhere.  Just running bitmonerod without any flags is much too slow, so I tried some of the suggestions from this thread.  I tried a command that molecular posted for connecting to a single node and that didn't help.  I tried the --p2p-bind-ip 127.0.0.1 flag and that didn't help.  Just now I tried bitomonerod without any flags again:

Code:

a@a-1000H:~/monero.v0-9-1-1$ ./bitmonerod
Creating the logger system
2016-Mar-12 11:17:09.148477 Initializing cryptonote protocol...
2016-Mar-12 11:17:09.148892 Cryptonote protocol initialized OK
2016-Mar-12 11:17:09.150153 Initializing p2p server...
[1457799429] libunbound[4345:0] info: warning: unsupported algorithm for trust anchor . DS IN
[1457799429] libunbound[4345:0] warning: trust anchor . has no supported algorithms, the anchor is ignored (check if you need to upgrade unbound and openssl)
2016-Mar-12 11:17:12.960113 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.960951 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.961488 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.962204 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.968187 Binding on 0.0.0.0:18080
2016-Mar-12 11:17:12.968881 Net service bound to 0.0.0.0:18080
2016-Mar-12 11:17:12.969164 Attempting to add IGD port mapping.
2016-Mar-12 11:17:16.975016 No IGD was found.
2016-Mar-12 11:17:16.975391 P2p server initialized OK
2016-Mar-12 11:17:16.976533 Initializing core rpc server...
2016-Mar-12 11:17:16.977173 Binding on 127.0.0.1:18081
2016-Mar-12 11:17:16.977918 Core rpc server initialized OK on port: 18081
2016-Mar-12 11:17:16.978314 Initializing core...
2016-Mar-12 11:17:16.979770 Loading blockchain from folder /home/a/.bitmonero/lmdb ...
2016-Mar-12 11:17:16.980165 option: fastest
2016-Mar-12 11:17:16.980526 option: async
2016-Mar-12 11:17:16.980873 option: 1000
2016-Mar-12 11:17:17.447525 Blockchain initialized. last block: 839143, d109.h15.m4.s7 time ago, current difficulty: 785463195
2016-Mar-12 11:17:34.462371 WARNING: no two valid MoneroPulse DNS checkpoint records were received
2016-Mar-12 11:17:34.466477 Core initialized OK
2016-Mar-12 11:17:34.466986 Starting core rpc server...
2016-Mar-12 11:17:34.467432 Run net_service loop( 2 threads)...
2016-Mar-12 11:17:34.469203 [SRV_MAIN]Core rpc server started ok
2016-Mar-12 11:17:34.470473 [SRV_MAIN]Starting p2p net loop...
2016-Mar-12 11:17:34.471363 [SRV_MAIN]Run net_service loop( 10 threads)...
2016-Mar-12 11:17:35.471512 [P2P9]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).

Use "help" command to see the list of available commands.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2016-Mar-12 11:17:35.634786 [P2P7][108.28.24.179:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:36.091791 [P2P5][104.159.188.157:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.198821 [P2P4][104.233.75.221:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.780959 [P2P4][31.128.159.34:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:42.205319 [P2P9][76.173.170.133:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
exit
2016-Mar-12 11:18:32.217862 [node] Stop signal sent
Stop signal sent
exit
2016-Mar-12 11:20:18.539281 [node] Stop signal sent
Stop signal sent
2016-Mar-12 11:20:46.574322 [P2P7][108.28.24.179:18080 OUT]Synced 839344/994350
2016-Mar-12 11:20:46.574356 [P2P8][104.159.188.157:18080 OUT]Synced 839344/994350
save
Blockchain saved
exit
2016-Mar-12 11:21:12.569851 [node] Stop signal sent
Stop signal sent

Now it won't even exit.  I gave the command ten minutes ago.  So just for the hell of it I checked status:

Code:

status
Height: 839344/994350 (84.4%) on mainnet, mining at 604849015.99 GH/s, net hash 11.75 MH/s, v1, up to date, 6+0 connections

What to do, what to do...

sometimes it needs a second exit command. i thought this was resolved. 32 bit? you compile yourself?

edited to add - i see you tried more than 1 exit command.

u can always kill 9 it. if the blockchain was saved (as indicated) then your progress was saved afaik.

edited to add again - sometimes the exit process can take a while if you just started the daemon. I don't know why, but when I run for hours, and use the exit, it exits cleanly and very quickly. When I start it up, let it run for a couple of minutes and then go "oh crap I forgot this flag" and then hit exit, its hit or miss if it does it quickly.

[dEBRUYNE]

Using "exit" twice usually helps in exiting the daemon. I'll let someone else answer your other question, since I don't know that for sure.

[birr]

Slow exiting is the least of my problems.

[explorer]

status
Height: 839344/994350 (84.4%) on mainnet, mining at 604849015.99 GH/s, net hash 11.75 MH/s, v1, up to date, 6+0 connections
What to do, what to do...

That is so much higher than my 16 H/s   

[birr]

Forget about the exiting thing.  If anybody read my post, it should be evident the blockchain isn't downloading

[explorer]

Forget about the exiting thing.  If anybody read my post, it should be evident the blockchain isn't downloading

looks like it ran for less than a minute before exiting?  or was that just a sample, and no change after that?

[birr]

Forget about the exiting thing.  If anybody read my post, it should be evident the blockchain isn't downloading

looks like it ran for less than a minute before exiting?  or was that just a sample, and no change after that?

That was a sample.  I had it running for hours, before.

[dEBRUYNE]

Forget about the exiting thing.  If anybody read my post, it should be evident the blockchain isn't downloading

looks like it ran for less than a minute before exiting?  or was that just a sample, and no change after that?

That was a sample.  I had it running for hours, before.

I'll forward your error to hyc, who does most of the 32bit stuff currently.

[hyc]

I'm running 32 bit Ubuntu 14 on a netbook with an SSD over public library wifi.
I need to download about another 155,000 blocks and not getting anywhere.  Just running bitmonerod without any flags is much too slow, so I tried some of the suggestions from this thread.  I tried a command that molecular posted for connecting to a single node and that didn't help.  I tried the --p2p-bind-ip 127.0.0.1 flag and that didn't help.  Just now I tried bitomonerod without any flags again:

Code:

a@a-1000H:~/monero.v0-9-1-1$ ./bitmonerod
Creating the logger system
2016-Mar-12 11:17:09.148477 Initializing cryptonote protocol...
2016-Mar-12 11:17:09.148892 Cryptonote protocol initialized OK
2016-Mar-12 11:17:09.150153 Initializing p2p server...
[1457799429] libunbound[4345:0] info: warning: unsupported algorithm for trust anchor . DS IN
[1457799429] libunbound[4345:0] warning: trust anchor . has no supported algorithms, the anchor is ignored (check if you need to upgrade unbound and openssl)
2016-Mar-12 11:17:12.960113 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.960951 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.961488 Set limit-up to 2048 kB/s
2016-Mar-12 11:17:12.962204 Set limit-down to 8192 kB/s
2016-Mar-12 11:17:12.968187 Binding on 0.0.0.0:18080
2016-Mar-12 11:17:12.968881 Net service bound to 0.0.0.0:18080
2016-Mar-12 11:17:12.969164 Attempting to add IGD port mapping.
2016-Mar-12 11:17:16.975016 No IGD was found.
2016-Mar-12 11:17:16.975391 P2p server initialized OK
2016-Mar-12 11:17:16.976533 Initializing core rpc server...
2016-Mar-12 11:17:16.977173 Binding on 127.0.0.1:18081
2016-Mar-12 11:17:16.977918 Core rpc server initialized OK on port: 18081
2016-Mar-12 11:17:16.978314 Initializing core...
2016-Mar-12 11:17:16.979770 Loading blockchain from folder /home/a/.bitmonero/lmdb ...
2016-Mar-12 11:17:16.980165 option: fastest
2016-Mar-12 11:17:16.980526 option: async
2016-Mar-12 11:17:16.980873 option: 1000
2016-Mar-12 11:17:17.447525 Blockchain initialized. last block: 839143, d109.h15.m4.s7 time ago, current difficulty: 785463195
2016-Mar-12 11:17:34.462371 WARNING: no two valid MoneroPulse DNS checkpoint records were received
2016-Mar-12 11:17:34.466477 Core initialized OK
2016-Mar-12 11:17:34.466986 Starting core rpc server...
2016-Mar-12 11:17:34.467432 Run net_service loop( 2 threads)...
2016-Mar-12 11:17:34.469203 [SRV_MAIN]Core rpc server started ok
2016-Mar-12 11:17:34.470473 [SRV_MAIN]Starting p2p net loop...
2016-Mar-12 11:17:34.471363 [SRV_MAIN]Run net_service loop( 10 threads)...
2016-Mar-12 11:17:35.471512 [P2P9]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).

Use "help" command to see the list of available commands.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2016-Mar-12 11:17:35.634786 [P2P7][108.28.24.179:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:36.091791 [P2P5][104.159.188.157:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.198821 [P2P4][104.233.75.221:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:41.780959 [P2P4][31.128.159.34:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
2016-Mar-12 11:17:42.205319 [P2P9][76.173.170.133:18080 OUT]Sync data returned unknown top block: 839144 -> 994350 [155206 blocks (215 days) behind] 
SYNCHRONIZATION started
exit
2016-Mar-12 11:18:32.217862 [node] Stop signal sent
Stop signal sent
exit
2016-Mar-12 11:20:18.539281 [node] Stop signal sent
Stop signal sent
2016-Mar-12 11:20:46.574322 [P2P7][108.28.24.179:18080 OUT]Synced 839344/994350
2016-Mar-12 11:20:46.574356 [P2P8][104.159.188.157:18080 OUT]Synced 839344/994350
save
Blockchain saved
exit
2016-Mar-12 11:21:12.569851 [node] Stop signal sent
Stop signal sent

Now it won't even exit.  I gave the command ten minutes ago.  So just for the hell of it I checked status:

Code:

status
Height: 839344/994350 (84.4%) on mainnet, mining at 604849015.99 GH/s, net hash 11.75 MH/s, v1, up to date, 6+0 connections

What to do, what to do...

OK, ignoring the exit issue - there's no evidence of any problem here. Your log clearly shows that it sync'd 200 blocks between 11:17:42 and 11:20:46.

The main reason the current code seems to ignore exits is because the worker threads are busy syncing, and generally tied up waiting for disk I/O. When they finish syncing they ought to honor the exit command. Looks to me like you just have a very slow disk or very tight on RAM at that point, to cause so much I/O wait.

[birr]

There's something I don't understand.  Monero says I'm synced

Code:

2016-Mar-17 10:58:11.272307 [P2P6][178.22.65.158:18080 OUT]Synced 840144/1001392
2016-Mar-17 10:58:14.210958 [P2P6]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

but I'm still at block 843390 and 219 days behind

Code:

2016-Mar-17 11:49:20.305410 [P2P2][68.168.221.116:18080 OUT]Sync data returned unknown top block: 843390 -> 1001450 [158060 blocks (219 days) behind] 

I thought "synced and you may now start simplewallet" would mean you've finished downloading the blockchain?

[hyc]

There's something I don't understand.  Monero says I'm synced
but I'm still at block 843390 and 219 days behind

I thought "synced and you may now start simplewallet" would mean you've finished downloading the blockchain?

Ignore that. It just means that at one point you connected with a peer that was in the same state as you (843390 blocks) and it told you it had nothing new to give you. The daemon will of course keep on syncing with the rest of the connected peers.

[LucyLovesCrypto]

There's something I don't understand.  Monero says I'm synced
but I'm still at block 843390 and 219 days behind

I thought "synced and you may now start simplewallet" would mean you've finished downloading the blockchain?

Ignore that. It just means that at one point you connected with a peer that was in the same state as you (843390 blocks) and it told you it had nothing new to give you. The daemon will of course keep on syncing with the rest of the connected peers.

The first time I saw that I was confused too but ultimately assumed what you wrote:)

[mmortal03]

After upgrading from 0.9.1 to 0.9.2 on Windows 10 64-bit, at some point I received the following message "LMDB Mapsize increased. Old 10240MiB, New: 11264MiB", and then bitmonerod crashed. I haven't seen this on subsequent runs, so it could be a one-off bug.

[hyc]

Haven't seen anything like that. It's odd too, a fully sync'd blockchain would have been around 15GB mapsize already. If you were running 0.9.1, was it fully sync'd before you upgraded?

[mmortal03]

Haven't seen anything like that. It's odd too, a fully sync'd blockchain would have been around 15GB mapsize already. If you were running 0.9.1, was it fully sync'd before you upgraded?

Yes, it was within the last day, soon after 0.9.2 was released.

[hyc]

Haven't seen anything like that. It's odd too, a fully sync'd blockchain would have been around 15GB mapsize already. If you were running 0.9.1, was it fully sync'd before you upgraded?

Yes, it was within the last day, soon after 0.9.2 was released.

We had a critical bug in 0.9.2, which is now fixed in git master. I think you ran into it. A new point release will be coming out tomorrow.

[explorer]

Running .9.2 on windows 64, 100% synced, status says:

 ...v1, up to date, 8+0 connections

can someone give me explicit instructions to get connected?

thanks