revaen
Newbie
Offline
Activity: 9
Merit: 0
|
|
May 14, 2017, 10:21:08 AM |
|
Thanks for your explanation. It is working. The new wallet is synchronizing and shows the balance with XMR. New wallet looks much better.
|
|
|
|
Gemniet
Newbie
Offline
Activity: 24
Merit: 0
|
|
May 14, 2017, 05:24:55 PM |
|
Good run by Monero this past week . I am glad that I mine this coin. It is quite profitable nowadays so I will stick with my mining.
I do not see the good run. The price is quite stable, which is ideal.
|
|
|
|
Chicken76
Newbie
Offline
Activity: 58
Merit: 0
|
|
May 14, 2017, 07:17:40 PM |
|
Could you try as follows: [1] Exit monerod [2] Delete p2pstate.bin (on Windows it's in C:\ProgramData\bitmonero | Linux & Mac OS X it's in $HOME/bitmonero) [3] Restart monerod with the following command: monerod --block-sync-size 20 If you could give your operating system I could give some more detailed instructions (if aforementioned aren't sufficient). I've restarted the machine, fsck-ed the filesystem with no errors found and it looks like it's still stuck. I'll try your suggestion now.
|
|
|
|
start the art
|
|
May 14, 2017, 09:09:56 PM |
|
New original and unique MONERO abstract paintings-click to zoom,please use PM for any details Original price 400 USD Price now 180 USD click to ZOOM
|
|
|
|
monerostruggles1111
Newbie
Offline
Activity: 13
Merit: 0
|
|
May 16, 2017, 06:37:05 AM |
|
I'm having the same problem as Chiken76, daemon that is stuck on block 1200001 on my VPS that I'm setting up for the first time. I'd like to follow dEBRUYNE's advice but I can't find the p2pstate.bin file. I'm quite new to this so I could be doing something dumb. root@scw-c6201dNode:~# ls -LR .: bitmonero linuxarm7
./bitmonero: monero-v0.10.3.1
./bitmonero/monero-v0.10.3.1: monero-blockchain-export monero-blockchain-import monerod monero-utils-deserialize monero-wallet-cli monero-wallet-rpc
Here's the stuck daemon root@scw-c6213dNode:~/bitmonero/monero-v0.10.3.1# screen ./monerod 2017-05-16 06:22:56.104 b6ff43b0 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO 2017-05-16 06:22:56.105 b6ff43b0 INFO global src/daemon/main.cpp:282 Monero 'Wolfram Warptangent' (v0.10.3.1-release) 2017-05-16 06:22:56.106 b6ff43b0 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2017-05-16 06:22:56.106 b6ff43b0 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2017-05-16 06:22:56.107 b6ff43b0 INFO global src/daemon/p2p.h:63 Initializing p2p server... 2017-05-16 06:23:00.505 b6ff43b0 INFO global src/daemon/p2p.h:68 P2p server initialized OK 2017-05-16 06:23:00.505 b6ff43b0 INFO global src/daemon/rpc.h:58 Initializing core rpc server... 2017-05-16 06:23:00.506 b6ff43b0 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:18081 2017-05-16 06:23:00.506 b6ff43b0 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 18081 2017-05-16 06:23:00.506 b6ff43b0 INFO global src/daemon/core.h:73 Initializing core... 2017-05-16 06:23:00.518 b6ff43b0 INFO global src/cryptonote_core/cryptonote_core.cpp:326 Loading blockchain from folder /root/.bitmonero/lmdb ... 2017-05-16 06:23:01.326 b6ff43b0 INFO global src/blockchain_db/lmdb/db_lmdb.cpp:571 [batch] DB resize needed 2017-05-16 06:23:01.326 b6ff43b0 INFO global src/blockchain_db/lmdb/db_lmdb.cpp:487 LMDB Mapsize increased. Old: 12608MiB, New: 13632MiB 2017-05-16 06:23:02.595 b6ff43b0 INFO global src/daemon/core.h:78 Core initialized OK 2017-05-16 06:23:02.596 b6ff43b0 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2017-05-16 06:23:02.598 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2017-05-16 06:23:02.598 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2017-05-16 06:23:03.600 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1098 ********************************************************************** 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|categories>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. **********************************************************************
2017-05-16 06:23:04.110 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [73.110.98.19:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311217 [Your node is 111216 blocks (154 days) behind] SYNCHRONIZATION started 2017-05-16 06:28:40.896 [P2P1] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [5.9.2.145:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311218 [Your node is 111217 blocks (154 days) behind] SYNCHRONIZATION started 2017-05-16 06:31:06.531 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [217.182.73.97:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311220 [Your node is 111219 blocks (154 days) behind] SYNCHRONIZATION started
Thanks for any help.
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
|
May 16, 2017, 10:45:44 AM |
|
I'm having the same problem as Chiken76, daemon that is stuck on block 1200001 on my VPS that I'm setting up for the first time. I'd like to follow dEBRUYNE's advice but I can't find the p2pstate.bin file. I'm quite new to this so I could be doing something dumb. root@scw-c6201dNode:~# ls -LR .: bitmonero linuxarm7
./bitmonero: monero-v0.10.3.1
./bitmonero/monero-v0.10.3.1: monero-blockchain-export monero-blockchain-import monerod monero-utils-deserialize monero-wallet-cli monero-wallet-rpc
Here's the stuck daemon root@scw-c6213dNode:~/bitmonero/monero-v0.10.3.1# screen ./monerod 2017-05-16 06:22:56.104 b6ff43b0 INFO global contrib/epee/src/mlog.cpp:145 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO 2017-05-16 06:22:56.105 b6ff43b0 INFO global src/daemon/main.cpp:282 Monero 'Wolfram Warptangent' (v0.10.3.1-release) 2017-05-16 06:22:56.106 b6ff43b0 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2017-05-16 06:22:56.106 b6ff43b0 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2017-05-16 06:22:56.107 b6ff43b0 INFO global src/daemon/p2p.h:63 Initializing p2p server... 2017-05-16 06:23:00.505 b6ff43b0 INFO global src/daemon/p2p.h:68 P2p server initialized OK 2017-05-16 06:23:00.505 b6ff43b0 INFO global src/daemon/rpc.h:58 Initializing core rpc server... 2017-05-16 06:23:00.506 b6ff43b0 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:18081 2017-05-16 06:23:00.506 b6ff43b0 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 18081 2017-05-16 06:23:00.506 b6ff43b0 INFO global src/daemon/core.h:73 Initializing core... 2017-05-16 06:23:00.518 b6ff43b0 INFO global src/cryptonote_core/cryptonote_core.cpp:326 Loading blockchain from folder /root/.bitmonero/lmdb ... 2017-05-16 06:23:01.326 b6ff43b0 INFO global src/blockchain_db/lmdb/db_lmdb.cpp:571 [batch] DB resize needed 2017-05-16 06:23:01.326 b6ff43b0 INFO global src/blockchain_db/lmdb/db_lmdb.cpp:487 LMDB Mapsize increased. Old: 12608MiB, New: 13632MiB 2017-05-16 06:23:02.595 b6ff43b0 INFO global src/daemon/core.h:78 Core initialized OK 2017-05-16 06:23:02.596 b6ff43b0 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2017-05-16 06:23:02.598 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2017-05-16 06:23:02.598 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2017-05-16 06:23:03.600 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1098 ********************************************************************** 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|categories>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. **********************************************************************
2017-05-16 06:23:04.110 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [73.110.98.19:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311217 [Your node is 111216 blocks (154 days) behind] SYNCHRONIZATION started 2017-05-16 06:28:40.896 [P2P1] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [5.9.2.145:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311218 [Your node is 111217 blocks (154 days) behind] SYNCHRONIZATION started 2017-05-16 06:31:06.531 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [217.182.73.97:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311220 [Your node is 111219 blocks (154 days) behind] SYNCHRONIZATION started
Thanks for any help. Which OS? I presume Linux / Mac OS X, but I'd like to know for sure. Anyway, it should be in $HOME/bitmonero. The directory itself may be hidden, so you have to manually browse to it. Alternatively, on Linux you can unhide directories by using CTRL + H.
|
|
|
|
Chicken76
Newbie
Offline
Activity: 58
Merit: 0
|
|
May 16, 2017, 12:34:17 PM Last edit: May 16, 2017, 04:01:58 PM by Chicken76 |
|
Which OS? I presume Linux / Mac OS X, but I'd like to know for sure. Anyway, it should be in $HOME/bitmonero. The directory itself may be hidden, so you have to manually browse to it. Alternatively, on Linux you can unhide directories by using CTRL + H.
I've tried your suggestion with "--block-sync-size" (even a value of 1) and it doesn't get it past 1200001. I'll delete the blockchain and let it resync from scratch. I'm running the same linuxarm7 build as monerostruggles1111 EDIT: Stopped the daemon and tried to run it on the testnet, to see if it syncs. I got the same behavior, only this time it's stuck on block 3, hehe. EDIT 2: I've restarted it with "--log-level 4" in hope the details might shed some light on the problem. Right now it's dumping a 100MB log file every 2 minutes mostly with messages like: 2017-05-16 18:47:27.212 [P2P0] TRACE blockchain src/cryptonote_core/blockchain.cpp:2105 Blockchain::have_block 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1434 BlockchainLMDB::block_exists 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2445 BlockchainLMDB::block_rtxn_start 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1445 Block with hash 170fd80f88150c79fb52776d5088f253c8cbf9cc7257ba467cada590586a827f not found in db 2017-05-16 18:47:27.213 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:305 mdb_txn_safe: destructor
|
|
|
|
kattycris
Newbie
Offline
Activity: 23
Merit: 0
|
|
May 16, 2017, 03:57:11 PM |
|
Does anyone know how I put the difficulty to the mine in a different value? my pool monero.crypto-pool.fr/
|
|
|
|
crypt0bitz
Newbie
Offline
Activity: 5
Merit: 0
|
|
May 16, 2017, 04:01:31 PM |
|
How does this differ in terms of being untraceable ? is it a scrambler or mixer or whatever ?
|
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
|
May 16, 2017, 05:22:56 PM |
|
Which OS? I presume Linux / Mac OS X, but I'd like to know for sure. Anyway, it should be in $HOME/bitmonero. The directory itself may be hidden, so you have to manually browse to it. Alternatively, on Linux you can unhide directories by using CTRL + H.
I've tried your suggestion with "--block-sync-size" (even a value of 1) and it doesn't get it past 1200001. I'll delete the blockchain and let it resync from scratch. I'm running the same linuxarm7 build as monerostruggles1111 EDIT: Stopped the daemon and tried to run it on the testnet, to see if it syncs. I got the same behavior, only this time it's stuck on block 3, hehe. EDIT 2: I've restarted it with "--log-level 4" in hope the details might shed some light on the problem. Right now it's dumping a 100MB log file every 2 minutes mostly with messages like: 2017-05-16 18:47:27.212 [P2P0] TRACE blockchain src/cryptonote_core/blockchain.cpp:2105 Blockchain::have_block 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1434 BlockchainLMDB::block_exists 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:2445 BlockchainLMDB::block_rtxn_start 2017-05-16 18:47:27.212 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:1445 Block with hash 170fd80f88150c79fb52776d5088f253c8cbf9cc7257ba467cada590586a827f not found in db 2017-05-16 18:47:27.213 [P2P7] TRACE blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:305 mdb_txn_safe: destructor Could you check in the logs whether there are any "Block fails to get added" messages? It's probably easier to spot if you restart monerod with --log-level 1.
|
|
|
|
Chicken76
Newbie
Offline
Activity: 58
Merit: 0
|
|
May 16, 2017, 05:53:46 PM |
|
Could you check in the logs whether there are any "Block fails to get added" messages? It's probably easier to spot if you restart monerod with --log-level 1.
I've tried --log-level 3 as well, but it's the same deluge. However, with --log-level 2 it's easier to spot the important things. What intrigues me is this message: 2017-05-16 20:44:22.197 [P2P8] INFO net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:981 [IP:50350 INC] Block verification failed, dropping connection "IP" is different every time. (over a couple of minutes worth of logs this is present dozens of times) I don't see any messages like "Block fails to get added". EDIT: Actually, this is even more relevant: 2017-05-16 20:41:19.797 [P2P9] ERROR verify src/cryptonote_core/blockchain.cpp:3185 Block with id: <82e8a00ebb396dcafc9ba5b44e9aad367bbc8f886736b0a49dd506c114b621fa> does not have enough proof of work: <2e55a37fb07a0813b6fa36e541e677d538c9d6b8105f6d60e07682af4239abfb> unexpected difficulty: 60 And this repeats for every peer.
|
|
|
|
monerostruggles1111
Newbie
Offline
Activity: 13
Merit: 0
|
|
May 17, 2017, 11:46:29 AM |
|
Well I ditched the armv7 for an armv8 machine and after importing the blockchain from the old box and firing up the daemon it seems to be syncing again. 2017-05-17 11:37:08.045 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [118.92.17.92:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1312076 [Your node is 112075 blocks (155 days) behind] SYNCHRONIZATION started 2017-05-17 11:37:51.965 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [24.20.159.188:18080 OUT] Synced 1200201/1312076 2017-05-17 11:38:33.269 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [74.222.20.106:18080 OUT] Synced 1200401/1312077 2017-05-17 11:39:04.353 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [104.244.73.123:18080 OUT] Synced 1200601/1312077
Maybe there's something wrong with armv7?
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
|
May 17, 2017, 12:21:01 PM |
|
Well I ditched the armv7 for an armv8 machine and after importing the blockchain from the old box and firing up the daemon it seems to be syncing again. 2017-05-17 11:37:08.045 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [118.92.17.92:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1312076 [Your node is 112075 blocks (155 days) behind] SYNCHRONIZATION started 2017-05-17 11:37:51.965 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [24.20.159.188:18080 OUT] Synced 1200201/1312076 2017-05-17 11:38:33.269 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [74.222.20.106:18080 OUT] Synced 1200401/1312077 2017-05-17 11:39:04.353 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004 [104.244.73.123:18080 OUT] Synced 1200601/1312077
Maybe there's something wrong with armv7? Apparently the issue is known and is being investigated by the devs: https://github.com/monero-project/monero/issues/1991&Chicken76.
|
|
|
|
Chicken76
Newbie
Offline
Activity: 58
Merit: 0
|
|
May 17, 2017, 12:51:09 PM |
|
Thanks for letting us know. If the devs need any info from me, or to beta-test a future fix, I'll be happy to help.
|
|
|
|
Juiceboxx
Newbie
Offline
Activity: 53
Merit: 0
|
|
May 17, 2017, 11:25:01 PM |
|
|
|
|
|
NeuroticFish
Legendary
Offline
Activity: 3822
Merit: 6547
Looking for campaign manager? Contact icopress!
|
|
May 18, 2017, 09:40:35 AM |
|
Interesting read. However, since the claimed virus started mining XMR, while the hackers are dumping XMR to the market, the price increases instead of decrease? Really? Although such scenarios are possible, even bedtime stories don't have such big inconsistencies...
|
|
|
|
|
LawBC
Full Member
Offline
Activity: 221
Merit: 100
www.francs.paris
|
|
May 18, 2017, 06:27:45 PM |
|
Some modest advice
- New website. You guys should be now able to hire the best web designer out there.
- Refine further the GUI ergonomy All the uneccessary settings for transactions should be hidden. It needs maximum simplification so the non-techy users don't feel confused. Even the tax ID field. Show them on click. The design as well coud be greatly refined as it's still looking a bit gross and heavy.
Take a look at LTC website and wallet design. These guys had quite terrible design before. If Litecoin have been able to successfully redesign everybody should be able to do it.
- The paper against Monero published by Zcash devs is showing up on Google search. I'm afraid it's bringing confusion for people searching about Monero. I don't know If you made a blog entry about this in order to clarify. But if not you should.
For all the rest I think you guys are doing genuine work.
|
|
|
|
|
|