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

Quote from: jwinterm on April 24, 2015, 08:48:10 PM

For all intensive purposes...

Sorry, but this is a pet peeve of mine. What you should say instead is "for all intents and purposes..."

This is unfair to the rare person who really was talking about the subset of purposes that are intensive.

I agree, I think we're being Intensivest with these sort of broad, sweeping language corrections. If we're not careful it's a slippery slope towards Antidisestablishmentarianism.

5w00p

hero member

Activity: 644

Merit: 502

Quote from: aminorex on April 24, 2015, 10:53:26 PM

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I built the windows db version and got it synced a few months ago, seemed to work without a hitch for me.

Yes, you did, and I remember. But, you are pretty much the only one who had some kind of perfect hardware and OS setup that it actually worked.

I tried on a linux VM in Win 8.1 and the conversion never worked and I gave up.

And I tried in Win 8.1 and it never worked.

eizh

hero member

Activity: 560

Merit: 500

Quote from: aminorex on April 24, 2015, 10:53:26 PM

For all intensive purposes...

Sorry, but this is a pet peeve of mine. What you should say instead is "for all intents and purposes..."

This is unfair to the rare person who really was talking about the subset of purposes that are intensive.

GingerAle

legendary

Activity: 1260

Merit: 1008

For all intensive purposes...

Sorry, but this is a pet peeve of mine. What you should say instead is "for all intents and purposes..."

or did he mean this?

aminorex

legendary

Activity: 1596

Merit: 1030

Sine secretum non libertas

Quote from: oblox on April 24, 2015, 09:44:09 PM

For all intensive purposes...

Sorry, but this is a pet peeve of mine. What you should say instead is "for all intents and purposes..."

GingerAle

legendary

Activity: 1260

Merit: 1008

Quote from: ?? on ??

Too many reasons to be in Monero:

http://www.bloomberg.com/news/articles/2015-04-23/negative-interest-rates-may-spark-existential-crisis-for-cash

seriously. a lot of amazing in that article.

its really interesting thinking about cryptocurrencies when reading about that article, and wondering why they' aren't catching like wildfire for these communities trying to hoard value without being taxed to hoard it (the whole negative interest rate thing)

I guess it mainly boils down to the fact that none of the cryptocurrencies have a stable value, so they're not a definite store of value, as opposed to holding X number of a governments fiat currency - because, for various reasons, those things have a given value (backed by the government i guess?)

so the question is at what point does any cryptocurrency become a stable store of value to begin attracting those that are trying to avoid the negative interest rates that are besetting contemporary finance? I'm assuming its merely a measure of time - but how much time? and how much stability?

And it will be interesting if bitcoin can maintain its value as this fungibility thing plays out.

smooth

legendary

Activity: 2968

Merit: 1198

Connecting from the new db build to port 18081 on local causes the synced node to spit out this:

I'm not sure, maybe a Windows-specific issue. I only use Linux and I just tried it again, everything worked fine.

oblox

legendary

Activity: 1442

Merit: 1018

Quote from: smooth on April 24, 2015, 09:36:17 PM

Quote from: smooth on April 24, 2015, 09:17:17 PM

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I've built it, just no luck converting an already synced up blockchain. I really don't want to bite the bullet and do it from genesis again but may have to. Come to think of it, fuck it, I'm just going to leave it run.

If you can't get the converter or import+export to work, another option is to sync your new node from your old node using --add-exclusive-node. That is somewhat faster and obviously uses little to no external bandwidth. This can even be done on the same computer if you make sure to use different ports and different data directories.

Care to elaborate on the appropriate setup?

For all intensive purposes, the synced node is running on local ip 192.168.1.71 with an --rpc-bind-ip 0.0.0.0 argument (for linux box running a wallet connecting to the remote node for refreshes). Datadir is default so I launch with:

bitmonero --rpc-bind-ip 0.0.0.0

Trying to test the new build for the database with a datadir in D:\bitmonero. Launching the second daemon, I am using:

bitmonerod --data-dir D:\Monero\ --rpc-bind-port 18085 --add-exclusive-node 192.168.1.71:18080

This just causes the same block to continuing syncing, block 2201. Any other arguments missing from either setup?

Probably the node is connecting to itself or otherwise failing.

You need to set the --p2p-bind-port to something nonstandard, in addition to the --rpc-bind-port. If you are connecting to the same computer you can use 127.0.0.1:18080 as your exclusive node address. That will be slightly faster than using an actual IP

Yep, these two daemons would be on windows so using the local address would be fine in that regard. Adding --p2p-bind-port 5555 to the new db build still results in syncing stuck at block 2201 (sync data returned unknown top block: 2201):

bitmonerod --data-dir D:\Monero\ --p2p-bind-port 5555 --rpc-bind-port 18085 --add-exclusive-node 127.0.0.1:18080

The other daemon (pre db rollout) is synced to the latest block. Thoughts?

EDIT:

Connecting from the new db build to port 18081 on local causes the synced node to spit out this:

Code:

C:\Monero>bitmonerod.exe --rpc-bind-ip 0.0.0.0
2015-Apr-24 20:45:55.441816 Starting...
2015-Apr-24 20:45:55.441816 bitmonero v0.8.8.6-release
2015-Apr-24 20:45:55.441816 Module folder: bitmonerod.exe
2015-Apr-24 20:45:55.441816 Initializing P2P server...
2015-Apr-24 20:46:07.581833 Binding on 0.0.0.0:18080
2015-Apr-24 20:46:07.581833 Net service bound to 0.0.0.0:18080
2015-Apr-24 20:46:07.581833 Attempting to add IGD port mapping.
2015-Apr-24 20:46:11.162838 UPnP device was found but not recoginzed as IGD.
2015-Apr-24 20:46:11.162838 P2P server initialized OK
2015-Apr-24 20:46:11.162838 Initializing protocol...
2015-Apr-24 20:46:11.162838 Protocol initialized OK
2015-Apr-24 20:46:11.162838 Initializing core RPC server...
2015-Apr-24 20:46:11.162838 Binding on 0.0.0.0:18081
2015-Apr-24 20:46:11.172838 Core RPC server initialized OK on port: 18081
2015-Apr-24 20:46:11.172838 Initializing core...
2015-Apr-24 20:46:11.172838 Loading blockchain...
2015-Apr-24 20:47:26.996943 Blockchain initialized. last block: 535484, d0.h0.m3
6.s58 time ago, current difficulty: 921999187
2015-Apr-24 20:47:27.186943 Core initialized OK
2015-Apr-24 20:47:27.186943 Starting core RPC server...
2015-Apr-24 20:47:27.186943 Run net_service loop( 2 threads)...
2015-Apr-24 20:47:27.186943 [SRV_MAIN]Core RPC server started ok
2015-Apr-24 20:47:27.186943 [SRV_MAIN]Starting P2P net loop...
2015-Apr-24 20:47:27.186943 [SRV_MAIN]Run net_service loop( 10 threads)...
2015-Apr-24 20:47:27.196943 [P2P2]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon wi
th "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2015-Apr-24 20:47:27.196943 [P2P0][93.74.42.79:17428 INC]Sync data returned unkn
own top block: 535485 -> 535520 [35 blocks (0 days) behind]
SYNCHRONIZATION started
2015-Apr-24 20:47:27.196943 [P2P4][61.234.152.135:2306 INC]Sync data returned un
known top block: 535485 -> 535521 [36 blocks (0 days) behind]
SYNCHRONIZATION started
2015-Apr-24 20:47:27.196943 [P2P1][178.235.245.176:35259 INC]Sync data returned
unknown top block: 535485 -> 535520 [35 blocks (0 days) behind]
SYNCHRONIZATION started
2015-Apr-24 20:47:28.186945 [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 " comman
d*, where 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.
**********************************************************************
2015-Apr-24 20:47:28.866946 [P2P3][94.23.216.116:10201 OUT]Sync data returned un
known top block: 535485 -> 535521 [36 blocks (0 days) behind]
SYNCHRONIZATION started
2015-Apr-24 20:47:29.046946 [P2P9][46.183.145.69:18080 OUT]Sync data returned un
known top block: 535485 -> 535521 [36 blocks (0 days) behind]
SYNCHRONIZATION started
2015-Apr-24 20:47:31.336949 [P2P3][46.183.145.69:18080 OUT] SYNCHRONIZED OK
2015-Apr-24 20:47:49.657974 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣E≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:47:49.657974 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!
2015-Apr-24 20:47:56.658984 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣L≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:47:56.658984 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!
2015-Apr-24 20:48:03.658994 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣S≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:48:03.658994 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!
2015-Apr-24 20:48:10.659003 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣Z≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:48:25.560024 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!
2015-Apr-24 20:48:25.660024 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣i≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:48:25.660024 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!
2015-Apr-24 20:48:32.661034 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:355 simple_http_connection_handler
::handle_invoke_query_line(): Failed to match first line: ☺!☺☺☺☺☺☺╡ ☺Θ♥
   ☺ ☺ ☺◄☺☺☺☺☻ node_data♀►
local_time♣p≥:U ^my_port♠│§
network_id
π╬)╬♀payload_data♫current_height♣ ♠top_id
Ç└åá┤ê╙σ
r K☻ gû·~`4ëµ█ΩG╜¶ü
2015-Apr-24 20:48:32.771034 [RPC1]ERROR C:/bitmonero/contrib/epee/include/net/ht
tp_protocol_handler.inl:299 simple_http_connection_handler::handle_char_out: Err
or state!!!

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: smooth on April 24, 2015, 09:17:17 PM

Quote from: smooth on April 24, 2015, 09:17:17 PM

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I've built it, just no luck converting an already synced up blockchain. I really don't want to bite the bullet and do it from genesis again but may have to. Come to think of it, fuck it, I'm just going to leave it run.

If you can't get the converter or import+export to work, another option is to sync your new node from your old node using --add-exclusive-node. That is somewhat faster and obviously uses little to no external bandwidth. This can even be done on the same computer if you make sure to use different ports and different data directories.

Care to elaborate on the appropriate setup?

For all intensive purposes, the synced node is running on local ip 192.168.1.71 with an --rpc-bind-ip 0.0.0.0 argument (for linux box running a wallet connecting to the remote node for refreshes). Datadir is default so I launch with:

bitmonero --rpc-bind-ip 0.0.0.0

Trying to test the new build for the database with a datadir in D:\bitmonero. Launching the second daemon, I am using:

bitmonerod --data-dir D:\Monero\ --rpc-bind-port 18085 --add-exclusive-node 192.168.1.71:18080

This just causes the same block to continuing syncing, block 2201. Any other arguments missing from either setup?

Probably the node is connecting to itself or otherwise failing.

You need to set the --p2p-bind-port to something nonstandard, in addition to the --rpc-bind-port. If you are connecting to the same computer you can use 127.0.0.1:18080 as your exclusive node address. That will be slightly faster than using an actual IP

oblox

legendary

Activity: 1442

Merit: 1018

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I've built it, just no luck converting an already synced up blockchain. I really don't want to bite the bullet and do it from genesis again but may have to. Come to think of it, fuck it, I'm just going to leave it run.

If you can't get the converter or import+export to work, another option is to sync your new node from your old node using --add-exclusive-node. That is somewhat faster and obviously uses little to no external bandwidth. This can even be done on the same computer if you make sure to use different ports and different data directories.

Care to elaborate on the appropriate setup?

For all intensive purposes, the synced node is running on local ip 192.168.1.71 with an --rpc-bind-ip 0.0.0.0 argument (for linux box running a wallet connecting to the remote node for refreshes--connects fine to 192.168.1.71:18080). Datadir is default so I launch with:

bitmonero --rpc-bind-ip 0.0.0.0

Trying to test the new build for the database with a datadir in D:\bitmonero. Launching the second daemon, I am using:

bitmonerod --data-dir D:\Monero\ --rpc-bind-port 18085 --add-exclusive-node 192.168.1.71:18080

This just causes the same block to continuing syncing, block 2201. Any other arguments missing from either setup?

smooth

legendary

Activity: 2968

Merit: 1198

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I've built it, just no luck converting an already synced up blockchain. I really don't want to bite the bullet and do it from genesis again but may have to. Come to think of it, fuck it, I'm just going to leave it run.

If you can't get the converter or import+export to work, another option is to sync your new node from your old node using --add-exclusive-node. That is somewhat faster and obviously uses little to no external bandwidth. This can even be done on the same computer if you make sure to use different ports and different data directories.

oblox

legendary

Activity: 1442

Merit: 1018

TY oblox but what part of drooling masses don't you understand? Grin

Has anybody actually built the windows version?

I am looking forward to running a node again.

I've built it, just no luck converting an already synced up blockchain. I really don't want to bite the bullet and do it from genesis again but may have to. Come to think of it, fuck it, I'm just going to leave it run.

jwinterm

legendary

Activity: 3136

Merit: 1116