Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1715. (Read 4670972 times)

sr. member
Activity: 252
Merit: 250


you need to run the "save command in the daemon and you wont have to redownload it every time. it is either save or save_bc i cant remember off the top of my head.

I'm not that dumb. I type exit, and it auto-save's it.

Yeah, your bitmonerod isnt starting that many blocks behind so looks like it saved the blockchain ok. At least two P2P connections (6 & Cool appear to be trying to sync the blockchain for you, anything show up in the log later for them? Equipoise's suggestion about low disk space/RAM seems most likely, except you say it isnt, so its getting a bit baffling. You could be brave and try the "set_log 4" for maximum log spam....
sr. member
Activity: 252
Merit: 250

In http://monero.cc/getting-started there is a script written by Quanttek:
Code:
cd ~ && rm -f install_monero.sh && wget https://monero.cc/downloads/install_monero.sh && bash install_monero.sh
It will install all the pre-requirements and then it'll compile it for you.
I tried this script twice, it did not work for me.
Please could anyone tell me the meaning of these errors:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
     typedef unsigned __int128 uint128_t;
                      ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
     uint128_t res = (uint128_t) a * (uint128_t) b;
     ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
     low = (uint64_t) res;

I dont think those are the errors to worry about, its the compiler just pointing out a few minor issues, it looked to me like your problem is with the make command trying to create folders, but I dont understand the error msgs.
legendary
Activity: 1092
Merit: 1000
I'm a Firestarter!


you need to run the "save command in the daemon and you wont have to redownload it every time. it is either save or save_bc i cant remember off the top of my head.

I'm not that dumb. I type exit, and it auto-save's it.
sr. member
Activity: 294
Merit: 250
1000 blocks downloaded, 103k to go  Lips sealed
If this does not get the thing to work, I DON'T care if it would be even a golden coin.
Dev team should think about it BEFORE they even started publishing anything.
And if dev team fails - success is equal to zero.

Failure to cross-platform serialize was an internal failure from the ByteCoin code, hence we updated our codebase to include mnemonic seeds to generate keys that function easily across platforms.

Unfortunately, we inherited a lot of bad code, but we're doing our best to fix it now.

Can see that.
I've been downloading a blockchain from 0.
It took me about 12 hours to finish it.
After I did, I started my wallet and all was fine.

BUT, now, again, the same problem is present.
I have backup of blockchain I've downloaded(updated) and I tried to replace the existing one, but nothing change that state.
Can anyone explain what the real problem could be?


If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.

Yes, I tried that, and here are (is) result(s) from the .log file:

Code:
2014-Jun-29 20:59:26.112671 [P2P1][94.244.155.113:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:26.114625 [P2P4][94.244.155.113:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:26.117554 [P2P4]Random connection index=6(x=14, max_index=20)
2014-Jun-29 20:59:26.119507 [P2P4]Selected peer: 18170737938260944790 178.41.54.60:18080[white=0] last_seen: d0.h0.m7.s16
2014-Jun-29 20:59:26.124390 [P2P4]Connecting to 178.41.54.60:18080(white=0, last_seen: d0.h0.m7.s16)...
2014-Jun-29 20:59:26.889039 [P2P6][94.244.155.113:18080 OUT]NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:27.242554 [P2P6][94.244.155.113:18080 OUT]-->>NOTIFY_RESPONSE_CHAIN_ENTRY: m_start_height=100914, m_total_height=106847, m_block_ids.size()=5933
2014-Jun-29 20:59:27.247437 [P2P6][94.244.155.113:18080 OUT] post struct cryptonote::NOTIFY_RESPONSE_CHAIN_ENTRY -->
2014-Jun-29 20:59:31.127320 [P2P4]Failed to connect to 178.41.54.60:18080, because of timeout (5000)
2014-Jun-29 20:59:31.140992 [P2P4][sock 4294967295] Socket destroyed without shutdown.
2014-Jun-29 20:59:31.152710 [P2P4][sock 4294967295] Socket destroyed
2014-Jun-29 20:59:31.162476 [P2P4][0.0.0.0:0 OUT]Connect failed to 178.41.54.60:18080
2014-Jun-29 20:59:31.170289 [P2P4]Random connection index=1(x=8, max_index=20)
2014-Jun-29 20:59:31.176148 [P2P4]Selected peer: 9506295159526218340 46.229.50.42:18080[white=0] last_seen: d0.h0.m0.s21
2014-Jun-29 20:59:31.186890 [P2P4]Connecting to 46.229.50.42:18080(white=0, last_seen: d0.h0.m0.s21)...
2014-Jun-29 20:59:31.294312 [P2P4]Connected success to 46.229.50.42:18080
2014-Jun-29 20:59:31.305054 [P2P4][sock 872] new connection from 46.229.50.42:18080 OUT to 192.168.0.101:51883, total sockets objects 11
2014-Jun-29 20:59:31.323609 [P2P4][46.229.50.42:18080 9d3cf0d6-659e-41d7-aedb-6eaaab3b4324 OUT] NEW CONNECTION
2014-Jun-29 20:59:31.848023 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: TIME_DELTA: 4, remote peerlist size=252
2014-Jun-29 20:59:31.861695 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: 35627ce00922a0aa 97.94.210.82:18080 last_seen: d0.h0.m0.s0

Code:
2014-Jun-29 20:59:32.791382 [P2P2][46.229.50.42:18080 OUT]Sync data returned unknown top block: 106847 -> 107148 [301 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Jun-29 20:59:32.802125 [P2P2]Remote top block height: 107148, id: <7a32a4d3735f0cd3be23cad8a3d80b8669550c2a2f9d9baa1f05292cfc3ca1e2>
2014-Jun-29 20:59:32.810914 [P2P2][46.229.50.42:18080 OUT]requesting callback
2014-Jun-29 20:59:32.816773 [P2P2][46.229.50.42:18080 OUT] request_callback
2014-Jun-29 20:59:32.821656 [P2P2][46.229.50.42:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:32.828492 [P2P4][46.229.50.42:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:32.834351 [P2P4]Random connection index=17(x=19, max_index=20)
2014-Jun-29 20:59:32.839234 [P2P4]Selected peer: 7870288044270691678 188.239.94.255:18080[white=0] last_seen: d0.h0.m30.s43
2014-Jun-29 20:59:32.848023 [P2P4]Connecting to 188.239.94.255:18080(white=0, last_seen: d0.h0.m30.s43)...
2014-Jun-29 20:59:32.828492 [P2P8][46.229.50.42:18080 OUT] fired_callback
2014-Jun-29 20:59:32.860718 [P2P8][46.229.50.42:18080 OUT]callback fired
2014-Jun-29 20:59:32.866578 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:32.874390 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_CHAIN -->
2014-Jun-29 20:59:33.444703 [P2P8][46.229.50.42:18080 OUT]NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=302, m_start_height=106846, m_total_height=107148
2014-Jun-29 20:59:33.468140 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=200, txs.size()=0
2014-Jun-29 20:59:33.479859 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_GET_OBJECTS -->
2014-Jun-29 20:59:34.936890 [P2P9][1.57.95.76:18080 OUT]NOTIFY_RESPONSE_GET_OBJECTS
2014-Jun-29 20:59:34.969117 [P2P9]tx <8eede40872a1885835eb8d87dcead63676462f1fa70f9e579efe1073d7949aec> already have transaction in blockchain
2014-Jun-29 20:59:34.981812 [P2P9]tx already have transaction in tx_pool
2014-Jun-29 20:59:34.991578 [P2P9]tx already have transaction in tx_pool
2014-Jun-29 20:59:35.089234 [P2P9]tx with id: <793bde1b414a7c8b04c696fba8b8b980cc569891a61d86bd36296707654bd73f> in block id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> already in blockchain
2014-Jun-29 20:59:35.100953 [P2P9]Block with id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> failed to add transaction to blockchain storage
2014-Jun-29 20:59:35.110718 [P2P9][1.57.95.76:18080 OUT]Block verification failed, dropping connection
2014-Jun-29 20:59:35.117554 [P2P5][sock 924] Some not success at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.129273 [P2P5][sock 924] Some problems at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.140015 [P2P5][sock 924] Socket destroyed
2014-Jun-29 20:59:35.143921 [P2P5][1.57.95.76:18080 d2fb375f-38b5-4640-8ff0-c31e6e1eead5 OUT] CLOSE CONNECTION



you need to run the "save command in the daemon and you wont have to redownload it every time. it is either save or save_bc i cant remember off the top of my head.
newbie
Activity: 47
Merit: 0
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed.

This are the errors I got:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
     typedef unsigned __int128 uint128_t;
                      ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
     uint128_t res = (uint128_t) a * (uint128_t) b;
     ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
     low = (uint64_t) res;
                      ^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited.


It shouldnt be too hard on Ubuntu 14.04, have you been following the instructions or using the install script from http://monero.cc/getting-started/index.html ?

I havent bothered to put the foreign bits through translator, but at a guess you might just need to try "sudo make"
Iam somewhat of a noob with Linux, but not an idiot:
Of course, I have kept to the instructions and various obstacles - such as the right boost version, for example - already circumnavigated. Also, "sudo" is quite familiar to me, otherwise the make command had not been executed.

But with the error messages shown above, I can not do anything. I do not expect complete solution, a hint in which direction I should look for, would help me.
In http://monero.cc/getting-started there is a script written by Quanttek:
Code:
cd ~ && rm -f install_monero.sh && wget https://monero.cc/downloads/install_monero.sh && bash install_monero.sh
It will install all the pre-requirements and then it'll compile it for you.
I tried this script twice, it did not work for me.
Please could anyone tell me the meaning of these errors:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
     typedef unsigned __int128 uint128_t;
                      ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
     uint128_t res = (uint128_t) a * (uint128_t) b;
     ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
     low = (uint64_t) res;
hero member
Activity: 794
Merit: 1000
Monero (XMR) - secure, private, untraceable
^You are running out of RAM.

But (while running it) I have about 1GB free *0.8-1.1
What about your HDD? Your OS (Windows?) is reporting out of memory (probably RAM not HDD, but I'm not sure). If you have enough RAM and HDD then you should contact Microsoft support about a strange bug in their OS.
newbie
Activity: 50
Merit: 0
Hi,

I just compiled bitmonerod and simplewallet and for warm-up did some small transaction back and forth between my wallet and poloniex. Works a charm :-)

Now, my problem: after a while, bitmonerod throws lots of error msgs like this:

..../bitmonero/contrib/epee/include/net/abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection

I wouldn't care really, but I suspect this has something to do for one of my transactions from poloniex to my wallet not showing up in my wallet for more than an hour.
When I restarted bitmonerod and simplewallet, my missing transaction was there imediately, so it looks like the daemon (bitmonerod) "hang" somehow...

Any hints, maybe I should configure something in a certain way to reduce probability of such hangs?

Thanks!
legendary
Activity: 1092
Merit: 1000
I'm a Firestarter!
^You are running out of RAM.

But (while running it) I have about 1GB free *0.8-1.1
hero member
Activity: 794
Merit: 1000
Monero (XMR) - secure, private, untraceable
^You are running out of RAM.
legendary
Activity: 1092
Merit: 1000
I'm a Firestarter!
Ok, i got the error here, which (when happens), blockchain after that happens becomes unusable:



(red letters)

Help / Hint?
hero member
Activity: 794
Merit: 1000
Monero (XMR) - secure, private, untraceable
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed.

This are the errors I got:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
     typedef unsigned __int128 uint128_t;
                      ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
     uint128_t res = (uint128_t) a * (uint128_t) b;
     ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
     low = (uint64_t) res;
                      ^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited.


It shouldnt be too hard on Ubuntu 14.04, have you been following the instructions or using the install script from http://monero.cc/getting-started/index.html ?

I havent bothered to put the foreign bits through translator, but at a guess you might just need to try "sudo make"
Iam somewhat of a noob with Linux, but not an idiot:
Of course, I have kept to the instructions and various obstacles - such as the right boost version, for example - already circumnavigated. Also, "sudo" is quite familiar to me, otherwise the make command had not been executed.

But with the error messages shown above, I can not do anything. I do not expect complete solution, a hint in which direction I should look for, would help me.
In http://monero.cc/getting-started there is a script written by Quanttek:
Code:
cd ~ && rm -f install_monero.sh && wget https://monero.cc/downloads/install_monero.sh && bash install_monero.sh
It will install all the pre-requirements and then it'll compile it for you.
sr. member
Activity: 252
Merit: 250

hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?

thanks for you help

it kinda seems like you just forgot your password. did you try 'x' for password? or nothing? capslock?

dude theres no way i could have forgotten, i had it written on two docs, ive gone through all the previous versions of the txt doc i put it on, and the password is correct, so i dont know why i cant get into my wallet

i took extra precautions with xmr for the fact that i didnt want to lose money and its a great coin... i dont understand why it worked before and not now if its literally exactly same password
newbie
Activity: 47
Merit: 0
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed.

This are the errors I got:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
     typedef unsigned __int128 uint128_t;
                      ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
     uint128_t res = (uint128_t) a * (uint128_t) b;
     ^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
     low = (uint64_t) res;
                      ^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited.


It shouldnt be too hard on Ubuntu 14.04, have you been following the instructions or using the install script from http://monero.cc/getting-started/index.html ?

I havent bothered to put the foreign bits through translator, but at a guess you might just need to try "sudo make"
Iam somewhat of a noob with Linux, but not an idiot:
Of course, I have kept to the instructions and various obstacles - such as the right boost version, for example - already circumnavigated. Also, "sudo" is quite familiar to me, otherwise the make command had not been executed.

But with the error messages shown above, I can not do anything. I do not expect complete solution, a hint in which direction I should look for, would help me.
legendary
Activity: 3136
Merit: 1116

hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?

thanks for you help

it kinda seems like you just forgot your password. did you try 'x' for password? or nothing? capslock?
sr. member
Activity: 252
Merit: 250
so i delete the address.txt file and wallet.bin?? and save or keep the .keys file... should i place the .keys file in app roaming?? or in same folder as simplewallet....

i also created it in windows ... so you had similar issue with invalid password??

thanks a bunch for you assitance i appreciate it

Download the latest binaries, extract to a new folder, place the [wallet.bin].keys file in there, start simple wallet, load your wallet name (without the .keys extension), enter password, and it will rebuild the wallet file

hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?

thanks for you help
legendary
Activity: 3136
Merit: 1116
I don't know if it have been asked but what is the formula for calculating fees ?
Flat 0.005 fee + small quantities to burn off dust in you use dust inputs

Oh ok thanks.
Will it increase or decrease in a near future ?


I'd hope with the flat fee of 0.005 (which was just increased from 0.000001 I think a few weeks ago) we'd be ok for a good long while.
legendary
Activity: 1092
Merit: 1000
I'm a Firestarter!
1000 blocks downloaded, 103k to go  Lips sealed
If this does not get the thing to work, I DON'T care if it would be even a golden coin.
Dev team should think about it BEFORE they even started publishing anything.
And if dev team fails - success is equal to zero.

Failure to cross-platform serialize was an internal failure from the ByteCoin code, hence we updated our codebase to include mnemonic seeds to generate keys that function easily across platforms.

Unfortunately, we inherited a lot of bad code, but we're doing our best to fix it now.

Can see that.
I've been downloading a blockchain from 0.
It took me about 12 hours to finish it.
After I did, I started my wallet and all was fine.

BUT, now, again, the same problem is present.
I have backup of blockchain I've downloaded(updated) and I tried to replace the existing one, but nothing change that state.
Can anyone explain what the real problem could be?


If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.

Yes, I tried that, and here are (is) result(s) from the .log file:

Code:
2014-Jun-29 20:59:26.112671 [P2P1][94.244.155.113:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:26.114625 [P2P4][94.244.155.113:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:26.117554 [P2P4]Random connection index=6(x=14, max_index=20)
2014-Jun-29 20:59:26.119507 [P2P4]Selected peer: 18170737938260944790 178.41.54.60:18080[white=0] last_seen: d0.h0.m7.s16
2014-Jun-29 20:59:26.124390 [P2P4]Connecting to 178.41.54.60:18080(white=0, last_seen: d0.h0.m7.s16)...
2014-Jun-29 20:59:26.889039 [P2P6][94.244.155.113:18080 OUT]NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:27.242554 [P2P6][94.244.155.113:18080 OUT]-->>NOTIFY_RESPONSE_CHAIN_ENTRY: m_start_height=100914, m_total_height=106847, m_block_ids.size()=5933
2014-Jun-29 20:59:27.247437 [P2P6][94.244.155.113:18080 OUT] post struct cryptonote::NOTIFY_RESPONSE_CHAIN_ENTRY -->
2014-Jun-29 20:59:31.127320 [P2P4]Failed to connect to 178.41.54.60:18080, because of timeout (5000)
2014-Jun-29 20:59:31.140992 [P2P4][sock 4294967295] Socket destroyed without shutdown.
2014-Jun-29 20:59:31.152710 [P2P4][sock 4294967295] Socket destroyed
2014-Jun-29 20:59:31.162476 [P2P4][0.0.0.0:0 OUT]Connect failed to 178.41.54.60:18080
2014-Jun-29 20:59:31.170289 [P2P4]Random connection index=1(x=8, max_index=20)
2014-Jun-29 20:59:31.176148 [P2P4]Selected peer: 9506295159526218340 46.229.50.42:18080[white=0] last_seen: d0.h0.m0.s21
2014-Jun-29 20:59:31.186890 [P2P4]Connecting to 46.229.50.42:18080(white=0, last_seen: d0.h0.m0.s21)...
2014-Jun-29 20:59:31.294312 [P2P4]Connected success to 46.229.50.42:18080
2014-Jun-29 20:59:31.305054 [P2P4][sock 872] new connection from 46.229.50.42:18080 OUT to 192.168.0.101:51883, total sockets objects 11
2014-Jun-29 20:59:31.323609 [P2P4][46.229.50.42:18080 9d3cf0d6-659e-41d7-aedb-6eaaab3b4324 OUT] NEW CONNECTION
2014-Jun-29 20:59:31.848023 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: TIME_DELTA: 4, remote peerlist size=252
2014-Jun-29 20:59:31.861695 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: 35627ce00922a0aa 97.94.210.82:18080 last_seen: d0.h0.m0.s0

Code:
2014-Jun-29 20:59:32.791382 [P2P2][46.229.50.42:18080 OUT]Sync data returned unknown top block: 106847 -> 107148 [301 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Jun-29 20:59:32.802125 [P2P2]Remote top block height: 107148, id: <7a32a4d3735f0cd3be23cad8a3d80b8669550c2a2f9d9baa1f05292cfc3ca1e2>
2014-Jun-29 20:59:32.810914 [P2P2][46.229.50.42:18080 OUT]requesting callback
2014-Jun-29 20:59:32.816773 [P2P2][46.229.50.42:18080 OUT] request_callback
2014-Jun-29 20:59:32.821656 [P2P2][46.229.50.42:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:32.828492 [P2P4][46.229.50.42:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:32.834351 [P2P4]Random connection index=17(x=19, max_index=20)
2014-Jun-29 20:59:32.839234 [P2P4]Selected peer: 7870288044270691678 188.239.94.255:18080[white=0] last_seen: d0.h0.m30.s43
2014-Jun-29 20:59:32.848023 [P2P4]Connecting to 188.239.94.255:18080(white=0, last_seen: d0.h0.m30.s43)...
2014-Jun-29 20:59:32.828492 [P2P8][46.229.50.42:18080 OUT] fired_callback
2014-Jun-29 20:59:32.860718 [P2P8][46.229.50.42:18080 OUT]callback fired
2014-Jun-29 20:59:32.866578 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:32.874390 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_CHAIN -->
2014-Jun-29 20:59:33.444703 [P2P8][46.229.50.42:18080 OUT]NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=302, m_start_height=106846, m_total_height=107148
2014-Jun-29 20:59:33.468140 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=200, txs.size()=0
2014-Jun-29 20:59:33.479859 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_GET_OBJECTS -->
2014-Jun-29 20:59:34.936890 [P2P9][1.57.95.76:18080 OUT]NOTIFY_RESPONSE_GET_OBJECTS
2014-Jun-29 20:59:34.969117 [P2P9]tx <8eede40872a1885835eb8d87dcead63676462f1fa70f9e579efe1073d7949aec> already have transaction in blockchain
2014-Jun-29 20:59:34.981812 [P2P9]tx already have transaction in tx_pool
2014-Jun-29 20:59:34.991578 [P2P9]tx already have transaction in tx_pool
2014-Jun-29 20:59:35.089234 [P2P9]tx with id: <793bde1b414a7c8b04c696fba8b8b980cc569891a61d86bd36296707654bd73f> in block id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> already in blockchain
2014-Jun-29 20:59:35.100953 [P2P9]Block with id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> failed to add transaction to blockchain storage
2014-Jun-29 20:59:35.110718 [P2P9][1.57.95.76:18080 OUT]Block verification failed, dropping connection
2014-Jun-29 20:59:35.117554 [P2P5][sock 924] Some not success at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.129273 [P2P5][sock 924] Some problems at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.140015 [P2P5][sock 924] Socket destroyed
2014-Jun-29 20:59:35.143921 [P2P5][1.57.95.76:18080 d2fb375f-38b5-4640-8ff0-c31e6e1eead5 OUT] CLOSE CONNECTION

legendary
Activity: 2156
Merit: 1131
I don't know if it have been asked but what is the formula for calculating fees ?
Flat 0.005 fee + small quantities to burn off dust in you use dust inputs

Oh ok thanks.
Will it increase or decrease in a near future ?
xa4
member
Activity: 71
Merit: 10



Have you deleted your p2pstate.bin and poolstate.bin? They will be found with you blockchain.bin file and will be recreated upon re-opening the wallet/daemon. Also, are you using the latest daemon in the OP?

I'm running v0.8.8.1.
And, yes, I deleted that 2 files (stored in \AppData\Roaming\bitmonero) and the problem is still present. Not moving from block 105314.
Is it me only, or anyone else have the same problem?

Started my daemon today and have the same problem ... stuck at block 100228. Nothing happens. Also no error messages.
A network problem or something ?



If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.

I deleted p2pstate and poolstate, started the deamon again with set_log command and I get lot of 'socket destroyed (whitout shutdown)' messages and in green 'connection handshake ok and closed' messages.
Don't know what to do ?

EDIT : problem solved. Restarted my router and now its syncing again.
legendary
Activity: 1484
Merit: 1005
we just need to have some of the other components integrated first eg database.

Thank you for working on this.  I'd guess the database may be the most important step at the moment.

By the way, I can confirm the fix for the deterministic seed/date restore bug is good.  Tested on 64bit Arch Linux.

Cool, thanks! Smiley
Jump to: