Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 210. (Read 1210779 times)
December 27, 2014, 02:35:09 PM
Lol, i was working hard this week with coin dev for the wallet on Linux, so no, coin has not been abandoned. Coin will be part of SuperNET, so please dump them before it goes online.
December 27, 2014, 11:52:57 AM
coin has been abandonned, better luck on the louis d'or thread.
in before louisd'or is a special order from jl777 and windjc for their supernet.
in before louisd'or is a special order from jl777 and windjc for their supernet.
December 26, 2014, 10:18:08 AM
It also eats a lot of memory for doing nothing..
December 26, 2014, 10:09:59 AM
Quote
**********************************************************************
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 with "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.
**********************************************************************
2014-Dec-25 17:09:31.639308 [P2P0]Connect failed to 201.248.99.222:10101
2014-Dec-25 17:09:31.639438 [P2P0]Connecting to 178.130.36.81:10101(white=0, last_seen: d27.h3.m4.s13)...
2014-Dec-25 17:09:31.677886 [P2P0]Connect failed to 178.130.36.81:10101
2014-Dec-25 17:09:31.677963 [P2P0]Connecting to 94.232.214.80:10101(white=0, last_seen: d42.h15.m44.s14)...
2014-Dec-25 17:09:36.678241 [P2P0]Connect failed to 94.232.214.80:10101
2014-Dec-25 17:09:36.678335 [P2P0]Connecting to 89.248.160.238:10101(white=0, last_seen: d0.h16.m26.s28)...
2014-Dec-25 17:09:36.678701 [P2P0]Connect failed to 89.248.160.238:10101
2014-Dec-25 17:09:36.678744 [P2P0]Connecting to 101.69.219.140:10101(white=0, last_seen: d11.h3.m59.s36)...
2014-Dec-25 17:09:41.678936 [P2P0]Connect failed to 101.69.219.140:10101
2014-Dec-25 17:09:41.679001 [P2P0]Connecting to 69.30.251.251:10101(white=0, last_seen: d5.h22.m50.s58)...
2014-Dec-25 17:09:46.679335 [P2P0]Connect failed to 69.30.251.251:10101
2014-Dec-25 17:09:46.679405 [P2P0]Connecting to 80.186.42.180:10101(white=0, last_seen: d29.h23.m12.s33)...
2014-Dec-25 17:09:51.679878 [P2P0]Connect failed to 80.186.42.180:10101
2014-Dec-25 17:09:53.680037 [P2P1]Connecting to 183.136.214.7:10101(white=0, last_seen: d8.h23.m53.s59)...
2014-Dec-25 17:09:58.680366 [P2P1]Connect failed to 183.136.214.7:10101
2014-Dec-25 17:09:58.680469 [P2P1]Connecting to 123.162.24.121:10101(white=0, last_seen: d1.h4.m58.s2)...
2014-Dec-25 17:10:03.680984 [P2P1]Connect failed to 123.162.24.121:10101
2014-Dec-25 17:10:03.681077 [P2P1]Connecting to 54.84.54.139:10101(white=0, last_seen: d37.h21.m8.s9)...
2014-Dec-25 17:10:03.764806 [P2P1]Connect failed to 54.84.54.139:10101
2014-Dec-25 17:10:03.764848 [P2P1]Connecting to 23.92.210.2:10101(white=0, last_seen: d38.h18.m49.s48)...
2014-Dec-25 17:10:08.765124 [P2P1]Connect failed to 23.92.210.2:10101
2014-Dec-25 17:10:08.765273 [P2P1]Connecting to 80.186.216.94:10101(white=0, last_seen: d48.h2.m14.s35)...
2014-Dec-25 17:10:13.765826 [P2P1]Connect failed to 80.186.216.94:10101
2014-Dec-25 17:10:13.765981 [P2P1]Connecting to 209.73.145.187:10101(white=1, last_seen: d0.h0.m10.s36)...
2014-Dec-25 17:10:14.223901 [P2P4][209.73.145.187:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.224076 [P2P1]Connecting to 91.121.221.92:10101(white=1, last_seen: d0.h12.m24.s5)...
2014-Dec-25 17:10:14.247516 [P2P4][91.121.221.92:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.247604 [P2P1]Connecting to 5.9.81.9:10101(white=1, last_seen: d0.h0.m41.s54)...
2014-Dec-25 17:10:14.284622 [P2P4][5.9.81.9:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:36.361844 Connections:
Remote Host Peer id Recv/Sent (idle,sec) State Livetime(seconds)
[OUT]38.93.234.100:10101 536377261e2a67f2 679564(21)/11137(21) state_normal 82
[OUT]185.11.72.235:10101 39be3d71fedfa692 966650(21)/17590(21) state_normal 81
[OUT]195.154.170.196:10101 5dce4bd82420f4f7 1049086(11)/18427(11) state_normal 82
[OUT]209.73.145.187:10101 2addbf4a61085eec 12504(5)/1614(5) state_normal 23
[INC]140.206.245.68:4325 17664cad1ca0eeb3 402(70)/4321(21) state_synchronizing 71
[OUT]188.226.215.102:10101 e8bd5efe6ee7c067 1064126(21)/16229(21) state_normal 82
[OUT]91.121.221.92:10101 c50117279b338a6c 2801(21)/777(21) state_normal 22
[OUT]5.9.81.9:10101 42b33c50d2afa4fe 3425(21)/777(21) state_normal 22
[OUT]95.85.21.33:10101 1549c89cc5eafc01 953559(21)/18347(21) state_normal 80
2014-Dec-25 17:31:34.343818 [P2P1]Connecting to 80.186.10.183:10101(white=0, last_seen: d32.h20.m0.s38)...
2014-Dec-25 17:31:35.683496 [P2P1]Connect failed to 80.186.10.183:10101
2014-Dec-25 17:31:35.683629 [P2P1]Connecting to 5.9.23.116:10101(white=0, last_seen: d0.h3.m3.s44)...
2014-Dec-25 17:31:35.720692 [P2P9][5.9.23.116:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 18:14:22.239667 [P2P4][sock 21] Some problems at write: Broken pipe:32
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 with "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.
**********************************************************************
2014-Dec-25 17:09:31.639308 [P2P0]Connect failed to 201.248.99.222:10101
2014-Dec-25 17:09:31.639438 [P2P0]Connecting to 178.130.36.81:10101(white=0, last_seen: d27.h3.m4.s13)...
2014-Dec-25 17:09:31.677886 [P2P0]Connect failed to 178.130.36.81:10101
2014-Dec-25 17:09:31.677963 [P2P0]Connecting to 94.232.214.80:10101(white=0, last_seen: d42.h15.m44.s14)...
2014-Dec-25 17:09:36.678241 [P2P0]Connect failed to 94.232.214.80:10101
2014-Dec-25 17:09:36.678335 [P2P0]Connecting to 89.248.160.238:10101(white=0, last_seen: d0.h16.m26.s28)...
2014-Dec-25 17:09:36.678701 [P2P0]Connect failed to 89.248.160.238:10101
2014-Dec-25 17:09:36.678744 [P2P0]Connecting to 101.69.219.140:10101(white=0, last_seen: d11.h3.m59.s36)...
2014-Dec-25 17:09:41.678936 [P2P0]Connect failed to 101.69.219.140:10101
2014-Dec-25 17:09:41.679001 [P2P0]Connecting to 69.30.251.251:10101(white=0, last_seen: d5.h22.m50.s58)...
2014-Dec-25 17:09:46.679335 [P2P0]Connect failed to 69.30.251.251:10101
2014-Dec-25 17:09:46.679405 [P2P0]Connecting to 80.186.42.180:10101(white=0, last_seen: d29.h23.m12.s33)...
2014-Dec-25 17:09:51.679878 [P2P0]Connect failed to 80.186.42.180:10101
2014-Dec-25 17:09:53.680037 [P2P1]Connecting to 183.136.214.7:10101(white=0, last_seen: d8.h23.m53.s59)...
2014-Dec-25 17:09:58.680366 [P2P1]Connect failed to 183.136.214.7:10101
2014-Dec-25 17:09:58.680469 [P2P1]Connecting to 123.162.24.121:10101(white=0, last_seen: d1.h4.m58.s2)...
2014-Dec-25 17:10:03.680984 [P2P1]Connect failed to 123.162.24.121:10101
2014-Dec-25 17:10:03.681077 [P2P1]Connecting to 54.84.54.139:10101(white=0, last_seen: d37.h21.m8.s9)...
2014-Dec-25 17:10:03.764806 [P2P1]Connect failed to 54.84.54.139:10101
2014-Dec-25 17:10:03.764848 [P2P1]Connecting to 23.92.210.2:10101(white=0, last_seen: d38.h18.m49.s48)...
2014-Dec-25 17:10:08.765124 [P2P1]Connect failed to 23.92.210.2:10101
2014-Dec-25 17:10:08.765273 [P2P1]Connecting to 80.186.216.94:10101(white=0, last_seen: d48.h2.m14.s35)...
2014-Dec-25 17:10:13.765826 [P2P1]Connect failed to 80.186.216.94:10101
2014-Dec-25 17:10:13.765981 [P2P1]Connecting to 209.73.145.187:10101(white=1, last_seen: d0.h0.m10.s36)...
2014-Dec-25 17:10:14.223901 [P2P4][209.73.145.187:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.224076 [P2P1]Connecting to 91.121.221.92:10101(white=1, last_seen: d0.h12.m24.s5)...
2014-Dec-25 17:10:14.247516 [P2P4][91.121.221.92:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.247604 [P2P1]Connecting to 5.9.81.9:10101(white=1, last_seen: d0.h0.m41.s54)...
2014-Dec-25 17:10:14.284622 [P2P4][5.9.81.9:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:36.361844 Connections:
Remote Host Peer id Recv/Sent (idle,sec) State Livetime(seconds)
[OUT]38.93.234.100:10101 536377261e2a67f2 679564(21)/11137(21) state_normal 82
[OUT]185.11.72.235:10101 39be3d71fedfa692 966650(21)/17590(21) state_normal 81
[OUT]195.154.170.196:10101 5dce4bd82420f4f7 1049086(11)/18427(11) state_normal 82
[OUT]209.73.145.187:10101 2addbf4a61085eec 12504(5)/1614(5) state_normal 23
[INC]140.206.245.68:4325 17664cad1ca0eeb3 402(70)/4321(21) state_synchronizing 71
[OUT]188.226.215.102:10101 e8bd5efe6ee7c067 1064126(21)/16229(21) state_normal 82
[OUT]91.121.221.92:10101 c50117279b338a6c 2801(21)/777(21) state_normal 22
[OUT]5.9.81.9:10101 42b33c50d2afa4fe 3425(21)/777(21) state_normal 22
[OUT]95.85.21.33:10101 1549c89cc5eafc01 953559(21)/18347(21) state_normal 80
2014-Dec-25 17:31:34.343818 [P2P1]Connecting to 80.186.10.183:10101(white=0, last_seen: d32.h20.m0.s38)...
2014-Dec-25 17:31:35.683496 [P2P1]Connect failed to 80.186.10.183:10101
2014-Dec-25 17:31:35.683629 [P2P1]Connecting to 5.9.23.116:10101(white=0, last_seen: d0.h3.m3.s44)...
2014-Dec-25 17:31:35.720692 [P2P9][5.9.23.116:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 18:14:22.239667 [P2P4][sock 21] Some problems at write: Broken pipe:32
After that the vps is still running (has 2.5GB RAM and 2.5GB SWAP), but the daemon is gone.
December 26, 2014, 12:46:15 AM
The daemon runs, but after 45 minutes it quits itself. Very annoying and no solution to this. It needs to run for SuperNET.
Can you post here an errors from daemon log files?
December 25, 2014, 09:21:46 PM
Cannot wait for the new wallet 
December 25, 2014, 07:02:43 PM
Tried to open up ports in iptables:
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
The problems are not only the ping rate its also the speed of the servers. Thats why many people keep getting reconnects when mining
I don't want to mine, i want to keep up a wallet for the instantdex supernet servers. Also it is a dedicated server which has quod core processors and 32GB of RAM.
The daemon runs, but after 45 minutes it quits itself. Very annoying and no solution to this. It needs to run for SuperNET.
December 25, 2014, 02:11:32 PM
What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.
Yes, it is good idea, and not very difficult in implementation, as far as I can see. We need to implement it in the future versions.)
December 25, 2014, 01:54:08 PM
i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now
Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.
no, thats not what i mean, but no problem reminding it to you, though i dont even understand what you are talking about
What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.
Also, who is : 1G467p3k4qGiqQCwFPDqSc46wzQZ9qnXB9JtLW9WD7T5UbnnT3imGsLeMnfjW5tsbBAibLbafcARU5e jW17mgYSd2Nxnq2W
?
He's taking all the good aliases
I'm interested in "@" and "0" and "1" PM ME !
December 25, 2014, 01:04:44 PM
i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now
Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.
no, thats not what i mean, but no problem reminding it to you, though i dont even understand what you are talking about
What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.
Also, who is : 1G467p3k4qGiqQCwFPDqSc46wzQZ9qnXB9JtLW9WD7T5UbnnT3imGsLeMnfjW5tsbBAibLbafcARU5e jW17mgYSd2Nxnq2W
?
He's taking all the good aliases
I'm interested in "@" and "0" and "1" PM ME !
December 25, 2014, 12:39:35 PM
i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now
Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.
December 25, 2014, 10:11:12 AM
i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now
December 25, 2014, 05:47:05 AM
Tried to open up ports in iptables:
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
The problems are not only the ping rate its also the speed of the servers. Thats why many people keep getting reconnects when mining
December 23, 2014, 09:46:30 AM
Tried to open up ports in iptables:
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT
But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds
I can ping the IP's though
$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms
December 23, 2014, 09:09:38 AM
Strange, the vps has 2.5GB of RAM and 2.5GB of swap. But indeed, it was making numerous cc1plus services. Did it without -j and it worked.
Ok, so i ran ./boolbd from /home/badass/boolberry/build/release/src and got this:
all the time. Any idea? Opening ports in iptables? addnodes to a config?
Ok, so i ran ./boolbd from /home/badass/boolberry/build/release/src and got this:
Quote
2014-Dec-23 13:55:16.569447 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.718748 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:16.718786 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.804009 [P2P9]Connect failed to 107.170.97.197:10101
2014-Dec-23 13:55:16.804056 [P2P9]Connecting to 188.226.215.102:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.805721 [P2P9]Connect failed to 188.226.215.102:10101
2014-Dec-23 13:55:16.805758 [P2P9]Connecting to 128.199.196.65:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.149151 [P2P9]Connect failed to 128.199.196.65:10101
2014-Dec-23 13:55:17.149201 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.300777 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:17.300816 [P2P9]Failed to connect to any of seed peers, continuing without seeds
2014-Dec-23 13:55:16.718748 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:16.718786 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.804009 [P2P9]Connect failed to 107.170.97.197:10101
2014-Dec-23 13:55:16.804056 [P2P9]Connecting to 188.226.215.102:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.805721 [P2P9]Connect failed to 188.226.215.102:10101
2014-Dec-23 13:55:16.805758 [P2P9]Connecting to 128.199.196.65:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.149151 [P2P9]Connect failed to 128.199.196.65:10101
2014-Dec-23 13:55:17.149201 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.300777 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:17.300816 [P2P9]Failed to connect to any of seed peers, continuing without seeds
all the time. Any idea? Opening ports in iptables? addnodes to a config?
If you're on AWS you can open ports from the web interface console, you don't need to mess with iptables or anything. I guess it depends on your VPS provider how you would unblock that port.
December 23, 2014, 06:49:17 AM
Strange, the vps has 2.5GB of RAM and 2.5GB of swap. But indeed, it was making numerous cc1plus services. Did it without -j and it worked.
Ok, so i ran ./boolbd from /home/badass/boolberry/build/release/src and got this:
all the time. Any idea? Opening ports in iptables? addnodes to a config?
Ok, so i ran ./boolbd from /home/badass/boolberry/build/release/src and got this:
Quote
2014-Dec-23 13:55:16.569447 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.718748 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:16.718786 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.804009 [P2P9]Connect failed to 107.170.97.197:10101
2014-Dec-23 13:55:16.804056 [P2P9]Connecting to 188.226.215.102:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.805721 [P2P9]Connect failed to 188.226.215.102:10101
2014-Dec-23 13:55:16.805758 [P2P9]Connecting to 128.199.196.65:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.149151 [P2P9]Connect failed to 128.199.196.65:10101
2014-Dec-23 13:55:17.149201 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.300777 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:17.300816 [P2P9]Failed to connect to any of seed peers, continuing without seeds
2014-Dec-23 13:55:16.718748 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:16.718786 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.804009 [P2P9]Connect failed to 107.170.97.197:10101
2014-Dec-23 13:55:16.804056 [P2P9]Connecting to 188.226.215.102:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:16.805721 [P2P9]Connect failed to 188.226.215.102:10101
2014-Dec-23 13:55:16.805758 [P2P9]Connecting to 128.199.196.65:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.149151 [P2P9]Connect failed to 128.199.196.65:10101
2014-Dec-23 13:55:17.149201 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2014-Dec-23 13:55:17.300777 [P2P9]Connect failed to 107.170.228.11:10101
2014-Dec-23 13:55:17.300816 [P2P9]Failed to connect to any of seed peers, continuing without seeds
all the time. Any idea? Opening ports in iptables? addnodes to a config?
December 23, 2014, 01:36:54 AM
December 23, 2014, 01:36:09 AM
I'm trying to install Boolberry wallet headless in Ubuntu. As far as i know it needs libboost1.55-all-dev which can be downloaded from repo ppa:boost-latest/ppa.
It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
Quote
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
Connection to 89.248.X.X closed.
Connection to 89.248.X.X closed.
It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
Try changing -j to like -j2 or even get rid of it if it doesn't compile. It takes a lot of memory depending on how many cores you have, and it looks like it ran out.
Or make a swap file if that still doesn't solve the problem. I've been able to compile wallets with only 512 MB of RAM on a vps using a 2 GB swap file. See here:
http://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/
December 22, 2014, 11:21:11 PM
I'm trying to install Boolberry wallet headless in Ubuntu. As far as i know it needs libboost1.55-all-dev which can be downloaded from repo ppa:boost-latest/ppa.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
Connection to 89.248.X.X closed.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
Connection to 89.248.X.X closed.
It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
Try changing -j to like -j2 or even get rid of it if it doesn't compile. It takes a lot of memory depending on how many cores you have, and it looks like it ran out.
[/quote]
Or make a swap file if that still doesn't solve the problem. I've been able to compile wallets with only 512 MB of RAM on a vps using a 2 GB swap file. See here:
http://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/
December 22, 2014, 10:52:44 PM
I'm trying to install Boolberry wallet headless in Ubuntu. As far as i know it needs libboost1.55-all-dev which can be downloaded from repo ppa:boost-latest/ppa.
But if i do sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake, i get this:
But now i got this:
It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
But if i do sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake, i get this:
But now i got this:
Quote
$ cd boolberry; make -j
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/bin/git
-- Configuring done
-- Generating done
-- Build files have been written to: /home/badass/boolberry/build/release
cd build/release && make
..........
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/rpc.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
Connection to 89.248.X.X closed.
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/bin/git
-- Configuring done
-- Generating done
-- Build files have been written to: /home/badass/boolberry/build/release
cd build/release && make
..........
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See
make[3]: *** [src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/rpc.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
Connection to 89.248.X.X closed.
It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea?
Try changing -j to like -j2 or even get rid of it if it doesn't compile. It takes a lot of memory depending on how many cores you have, and it looks like it ran out.
Jump to: