[XMR] Monero - A secure, private, untraceable cryptocurrency

[GingerAle]

Trying to sync the newest bitmonerod on a new VPS, it keeps crashing after this point:

Code:

2015-Dec-01 00:26:43.936098 [P2P9]LMDB Mapsize increased.  Old: 1024MiB, New: 2048MiB

Is there anything I can do to get past this?

Join IRC please. I'd like to get to the bottom of this, as I've seen it reported before.

Thanks again for your help, but I'm going to have to look for a new VPS, since I've been suspended for causing high load. No idea what the problem was, as I've run a node successfully on Digital Ocean on a VPS with the same specs.

Anyway, does anyone have a recommendation for a non-US VPS provider that accepts bitcoin?

What is your goal? Why not just run a node from home?

this is fun: http://lowendbox.com/

[elrippo]

Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?

Code:

2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

The CPU load returns to "normal" but the process does not store and exit....

[equipoise]

Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?

Code:

2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

The CPU load returns to "normal" but the process does not store and exit....

It was reported previously on some systems. Enter 'exit' again.

[elrippo]

Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?

Code:

2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

The CPU load returns to "normal" but the process does not store and exit....

It was reported previously on some systems. Enter 'exit' again.

As you can see from the output, i did it several times, and even if i do that 10 times, it won`t exit...

[saddambitcoin]

what about ctrl+c?

[elrippo]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

[GingerAle]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

[elrippo]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx 

[GingerAle]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx 

beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.

[elrippo]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx 

beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.

Yeeaaahhh, but i use Linux so the winbeta is like nuts for me 
Needless to say, we all are waitng for the official release   

Thanks for your help!

[GingerAle]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx 

beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.

Yeeaaahhh, but i use Linux so the winbeta is like nuts for me 
Needless to say, we all are waitng for the official release   

Thanks for your help!

then its even easier! Just compile!

[elrippo]

what about ctrl+c?

Code:

exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

Yeah that's 8.6. Known issue, been pretty much fixed with new version

I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx  

beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.

Yeeaaahhh, but i use Linux so the winbeta is like nuts for me  
Needless to say, we all are waitng for the official release    

Thanks for your help!

then its even easier! Just compile!

My fullnode is running on the compiled version, for my "productive" environment i will wait for the official binaries  

[canth]

https://www.zapchain.com/a/l/what-is-monero/ebbUzmGoEr

Feel free to jump in and add some comments.

[samaricanin]

My fullnode is running on the compiled version, for my "productive" environment i will wait for the official binaries  

Everyone is waiting official wallet 

[magico]

Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?

Code:

2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent

The CPU load returns to "normal" but the process does not store and exit....

It was reported previously on some systems. Enter 'exit' again.

Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".

[MoneroMooo]

Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".

I think I know what the problem is. It requires a coder with Windows (and some knowledge of windows APIs) to add a bit of code though. In contrib/epee/include/console_handler.h, the wait_stdin_data needs some code to implement what the select does (wait till there is data on stdin, while we're not told to stop). As it is, the Windows version will not care about that and go into a blocking std::getline, and I think there's a good chance you're getting stuck in that. Anyone with the above description to do this ? It's pretty simple if you know the right Windows API for this (assuming the API is not stupidly).

[luigi1111]

Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".

I think I know what the problem is. It requires a coder with Windows (and some knowledge of windows APIs) to add a bit of code though. In contrib/epee/include/console_handler.h, the wait_stdin_data needs some code to implement what the select does (wait till there is data on stdin, while we're not told to stop). As it is, the Windows version will not care about that and go into a blocking std::getline, and I think there's a good chance you're getting stuck in that. Anyone with the above description to do this ? It's pretty simple if you know the right Windows API for this (assuming the API is not stupidly).

On the other hand, I run a daemon on Windows and *never* have to exit twice. Though, if I "exit" while the daemon is still starting up, craziness happens (it has to be killed).

[papa_lazzarou]

THIS IS GENTLEMEN! 

moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.

[GingerAle]

THIS IS GENTLEMEN! 

moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.

marvelous work!

now its blatantly obvious how opaque monero transactions really are. There'll be a tip coming your way!!!

[MoneroMooo]

Git updates since last time:

Since last post:

- the IP banning code from Aeon got merged, and new commands/RPC for managing bans
- wallet refresh speedup (both parallelizing things, and avoiding others)
- a --restricted-rpc for the daemon (so others can't mine on your public node, for example)
- an option to let the wallet autmatically refresh periodically from the daemon
- a new show_transfers command to display transactions in a more useful way
- outgoing transactions info is now kept in the wallet cache so show_transfers can be even more useful
- the daemon will relay transactions periodically if they stay in the pool for too long (if they failed to relay, for instance if the network connection was down when the tx was first sent, for instance)