Search results

yeah I´m going to pass this one

76e29ba65b6a99ffb900f5bf4649a50ac193678bbc4904c24a7a8fab74be34cd 9266d28ca1d2b3b37daf8a49cda0d6b1f66c70e2fba081afcb78c8d7c6c0d626 68cd304933349e6857d48bd2a27edd7d7c3500ca0ccbd86feb6419b54d37a872 6c0e1a1267ae16e17e50e8d3b11251ed882e1ccf1474011d21e8dfeb434d0efe...

Thanks, downloading now

I´m not able to compile V12.0.47 on my pi model B, g++ crashes. Added more swap Can someone upload a compiled version? I only need dashd & dash-cli thanks

My MN would not start if I didn´t add rpc-ports for .dash1 & .dash2 with diffrent local bind-addess Here is my config: My first dash.conf for .dash folder: rpcuser=x rpcpassword=x rpcallowip=127.0.0.1 masternodeaddr=external_ip1:9999 bind=127.0.0.2 bind=external_ip1 listen=1 server=1...

It also works if you create diffrent copies of .dash for the same user. Like, .dash .dash1 .dash2, just remember to rename the dash-daemon to: dashd dashd1 dashd2 Then I start the MNs with this command: ./.dash/dashd -datadir=/home/user/.dash ./.dash1/dashd1 -datadir=/home/user/.dash1...

bind=127.0.0.3 rpcport=8002

It´s a VPS with 1 core cpu, 512mb ram, 2gb swap and 20gb disk. 4 public IP. It swaps around 200-400mb but it was really stable with 0.11.1.26. With the new version the dashd-daemon seems to crash quite often. I hope for a quick fix soon.

Your netstat shows that bind :::9998 listens on all interfaces for masternode1. Perhaps thats the reason your second masternode wont start? I think you need to specify a diffrent port/loopback IP for bind for the other masternodes. This is how my remote dash.conf looks like on two masternodes...

This is how my remote dash.conf looks like on two masternodes on the same server: Masternode 1 --------------------------------------- #---- rpcuser=xxxxx rpcpassword=xxxxxx rpcallowip=127.0.0.1 masternodeaddr=my external ip:9999 bind=127.0.0.2 bind=my external ip listen=1 server=1 daemon=1...

Is it possible to run masternode on a raspberry pi?