Author Topic: Masternodes Testing (Round 1)  (Read 185614 times)

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #300 on: January 28, 2015, 02:49:00 pm »

/bin/sh: 1: ./build_detect_platform: Permission denied
make[1]: Entering directory `/home/alfred/spreadcoin-mn-test/src/leveldb'
Makefile:18: build_config.mk: No such file or directory
make[1]: *** No rule to make target `build_config.mk'.  Stop.
chmod +x src/leveldb/build_detect_platform

Elbandi


Okay thanks for your assistance Elbandi. I made the changes to that file as per your instructions. Got a little further this time but seem to have a memory limitation issue on my VPS now (see last two lines below):

Quote
alfred@install:~/spreadcoin-mn-test$ qmake
Project MESSAGE: Building with UPNP support
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
alfred@install:~/spreadcoin-mn-test$ make
cd /home/alfred/spreadcoin-mn-test/src/leveldb && CC=gcc CXX=g++ make OPT="-m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2" libleveldb.a libmemenv.a
make[1]: Entering directory `/home/alfred/spreadcoin-mn-test/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/builder.cc -o db/builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/c.cc -o db/c.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/dbformat.cc -o db/dbformat.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/db_impl.cc -o db/db_impl.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/db_iter.cc -o db/db_iter.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/filename.cc -o db/filename.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/log_reader.cc -o db/log_reader.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/log_writer.cc -o db/log_writer.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/memtable.cc -o db/memtable.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/repair.cc -o db/repair.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/table_cache.cc -o db/table_cache.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/version_edit.cc -o db/version_edit.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/version_set.cc -o db/version_set.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c db/write_batch.cc -o db/write_batch.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/block_builder.cc -o table/block_builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/block.cc -o table/block.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/filter_block.cc -o table/filter_block.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/format.cc -o table/format.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/iterator.cc -o table/iterator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/merger.cc -o table/merger.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/table_builder.cc -o table/table_builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/table.cc -o table/table.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c table/two_level_iterator.cc -o table/two_level_iterator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/arena.cc -o util/arena.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/bloom.cc -o util/bloom.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/cache.cc -o util/cache.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/coding.cc -o util/coding.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/comparator.cc -o util/comparator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/crc32c.cc -o util/crc32c.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/env.cc -o util/env.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/env_posix.cc -o util/env_posix.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/env_win.cc -o util/env_win.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/filter_policy.cc -o util/filter_policy.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/hash.cc -o util/hash.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/histogram.cc -o util/histogram.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/logging.cc -o util/logging.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/options.cc -o util/options.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c util/status.cc -o util/status.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c port/port_posix.cc -o port/port_posix.o
rm -f libleveldb.a
ar -rs libleveldb.a db/builder.o db/c.o db/dbformat.o db/db_impl.o db/db_iter.o db/filename.o db/log_reader.o db/log_writer.o db/memtable.o db/repair.o db/table_cache.o db/version_edit.o db/version_set.o db/write_batch.o table/block_builder.o table/block.o table/filter_block.o table/format.o table/iterator.o table/merger.o table/table_builder.o table/table.o table/two_level_iterator.o util/arena.o util/bloom.o util/cache.o util/coding.o util/comparator.o util/crc32c.o util/env.o util/env_posix.o util/env_win.o util/filter_policy.o util/hash.o util/histogram.o util/logging.o util/options.o util/status.o port/port_posix.o
ar: creating libleveldb.a
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -c helpers/memenv/memenv.cc -o helpers/memenv/memenv.o
rm -f libmemenv.a
ar -rs libmemenv.a helpers/memenv/memenv.o
ar: creating libmemenv.a
make[1]: Leaving directory `/home/alfred/spreadcoin-mn-test/src/leveldb'
cd /home/alfred/spreadcoin-mn-test; /bin/sh share/genbuild.sh /home/alfred/spreadcoin-mn-test/build/build.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/sendcoinsdialog.ui -o build/ui_sendcoinsdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/coincontroldialog.ui -o build/ui_coincontroldialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/addressbookpage.ui -o build/ui_addressbookpage.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/signverifymessagedialog.ui -o build/ui_signverifymessagedialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/aboutdialog.ui -o build/ui_aboutdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/editaddressdialog.ui -o build/ui_editaddressdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/transactiondescdialog.ui -o build/ui_transactiondescdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/overviewpage.ui -o build/ui_overviewpage.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/sendcoinsentry.ui -o build/ui_sendcoinsentry.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/askpassphrasedialog.ui -o build/ui_askpassphrasedialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/rpcconsole.ui -o build/ui_rpcconsole.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/optionsdialog.ui -o build/ui_optionsdialog.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/blockexplorer.ui -o build/ui_blockexplorer.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/miningpage.ui -o build/ui_miningpage.h
/usr/lib/x86_64-linux-gnu/qt4/bin/uic src/qt/forms/masternodepage.ui -o build/ui_masternodepage.h
g++ -c -m64 -pipe -std=c++0x -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DLINUX -D_FILE_OFFSET_BITS=64 -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -Ibuild -Ibuild -o build/bitcoin.o src/qt/bitcoin.cpp
virtual memory exhausted: Cannot allocate memory
make: *** [build/bitcoin.o] Error 1

Try this to add "virtual" memory to your VPS (it be slower than real memory, since it's a diska swap, but will enable you compiling spread)

https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-12-04

daddeo

  • Newbie
  • *
  • Posts: 23
    • View Profile
Re: Masternodes Testing
« Reply #301 on: January 28, 2015, 02:49:48 pm »
Has anyone been successful in generating a mnsecret yet? I keep getting errors. I thought this was key to setting up a local/remote setup in where you could keep the coins in cold storage. I was going to try it with two different machines. Perhaps it's not implemented yet?

the help is not very good for mnsecret. What you need to do is:
find the transaction you used to transfer the funds to yourself:
./spreadcoin listtransactions
find out what is the output you want from this transaction (by trial and error, starting with 0, check if the output address is yur address and that the value matches)
./spreadcoin gettxout <long_tx_id_copied_from_above> 0
./spreadcoin gettxout <long_tx_id_copied_from_above> 1
./spreadcoin gettxout <long_tx_id_copied_from_above> 2
...
./spreadcoin gettxout <long_tx_id_copied_from_above> N
now you have: txid and outputnumber, use
./spreadcoin mnsecret <txid>:<output_number>

this worked for me as well

question - do we know for sure that mnstart=... is required in the spreadcoin.conf file? It didn't seem to do anything by adding that flag, eventually got my node onto the list by triggering ./spreadcoind mnstart <<mnsecret output>>. I assume this is only when the wallet.dat doesn't actually contain the coins or something?


Edit: wow, GUI startup of masternode is ridiculously easy. split my 200 test coins into two so I could compare the process :-)

This is what I got doing it the way I described earlier:
b3f4662ace3e850eaa5d1d92ebd7a11a8eecf391226a713ea84deb29b6089e5f:0:1b39776b442f13039016fa3e782a7a7e73524cb49178c1628a25122300b1d5a42aaad50803938ca374a05738bbaf6d0f08b63349b993fa58cb91ce1bd868ebcfb5:92VyeSmhJQqJP2inCqjTkKTUXPQbSimLm9hDbiZKsYSDL8GmRs2

The green is my output #. I guess the rest is the secret key. Does this look similar to what you get doing it as girino described?

yep that looks right to me -- I just realized that I took a bit of a shortcut when doing the above.

./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:2 // didn't work, gave error
./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:0 // didn't work, gave error
./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:1 // worked

not sure if there is any drawback to taking this approach but just fyi

Well, the drawback here is that if you have, say, 400 coins and want to set up 4 MNs, you'd send 100 spr to yourself, then try to get secret for that. The transaction would contain two outputs, one with 100 SPR to your address and another with 300 SPR to a random change address. If you do not check address and value, you might end up creating a MN with the 300 SPR instead of the 100.
which approach are you referring to; mine or snogcel's?

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #302 on: January 28, 2015, 02:52:50 pm »
yep that looks right to me -- I just realized that I took a bit of a shortcut when doing the above.

./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:2 // didn't work, gave error
./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:0 // didn't work, gave error
./spreadcoind mnsecret 124ad2be06321ca9881540818f2aad639ab963de410f8e267679c9d07833431f:1 // worked

not sure if there is any drawback to taking this approach but just fyi

Well, the drawback here is that if you have, say, 400 coins and want to set up 4 MNs, you'd send 100 spr to yourself, then try to get secret for that. The transaction would contain two outputs, one with 100 SPR to your address and another with 300 SPR to a random change address. If you do not check address and value, you might end up creating a MN with the 300 SPR instead of the 100.
which approach are you referring to; mine or snogcel's?

snogcel's. He's the one saying: "not sure if there is any drawback to taking this approach".

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #303 on: January 28, 2015, 02:56:34 pm »
Guy's,

i'm starting to agree with BitcoinTalk mods (not with the ban, which was uncalled for since Mr. Spread DID not promote the giveaway, it simply arose spontaneously in the thread, not by his suggestion): Asking for testcoins is spamming the thread.

So here is my suggestion: create another thread only for the "testcoins giveaway"

What do you think? This thread would keep technical issues and test reports, while another one would contain giveaways.

RenegadeMan

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: Masternodes Testing
« Reply #304 on: January 28, 2015, 03:13:43 pm »
RenegadeMan, yeah if you're short on RAM you'll need to add some swap space.

As root ('su root') or stick 'sudo' in front of everything...

Make some swap space and turn it on:
Code: [Select]
dd if=/dev/zero of=/swapfile bs=1M count=1024
mkswap /swapfile
swapon /swapfile

Now modify /etc/fstab so the swap is recognised at next boot:
Code: [Select]
nano /etc/fstab

If you don't have nano ( a simple text editor) you can install it with:
Code: [Select]
apt-get install nano

Add the following line to the bottom of the file:
Code: [Select]
/swapfile  swap      swap    defaults        0 0

...and try compiling again.


Okay, wow, what a process! All those XXXXXXXX.cpp files being generated.

I now have these additional files in the /spreadcoin-mn-test directory
bitcoin-qt.pro
qrc_bitcoin.cpp
spreadcoin-qt

What do I do to now run the Spreadcoin masternode wallet? (as I've tried just entering "spreadcoin-qt" at the command line like I would enter darkcoind for a DRK MN but it just returns "command not found".

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #305 on: January 28, 2015, 03:15:10 pm »
RenegadeMan, yeah if you're short on RAM you'll need to add some swap space.

As root ('su root') or stick 'sudo' in front of everything...

Make some swap space and turn it on:
Code: [Select]
dd if=/dev/zero of=/swapfile bs=1M count=1024
mkswap /swapfile
swapon /swapfile

Now modify /etc/fstab so the swap is recognised at next boot:
Code: [Select]
nano /etc/fstab

If you don't have nano ( a simple text editor) you can install it with:
Code: [Select]
apt-get install nano

Add the following line to the bottom of the file:
Code: [Select]
/swapfile  swap      swap    defaults        0 0

...and try compiling again.


Okay, wow, what a process! All those XXXXXXXX.cpp files being generated.

I now have these additional files in the /spreadcoin-mn-test directory
bitcoin-qt.pro
qrc_bitcoin.cpp
spreadcoin-qt

What do I do to now run the Spreadcoin masternode wallet? (as I've tried just entering "spreadcoin-qt" at the command line like I would enter darkcoind for a DRK MN but it just returns "command not found".

That's linux, you need to tell where the file is... always...:

Code: [Select]
./spreadcoin-qt
is the right command.

Strumpet!

  • Full Member
  • ***
  • Posts: 158
    • View Profile
Re: Masternodes Testing
« Reply #306 on: January 28, 2015, 03:21:30 pm »
RenegadeMan are you running a GUI environment on your VPS? Because if you're not you'll want to compile spreadcoind instead. If you are you can run it with ./spreadcoin-qt in a terminal or just double click on it in your GUI file browser/windowmanager/whatever

RenegadeMan

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: Masternodes Testing
« Reply #307 on: January 28, 2015, 03:24:30 pm »
RenegadeMan, yeah if you're short on RAM you'll need to add some swap space.

As root ('su root') or stick 'sudo' in front of everything...

Make some swap space and turn it on:
Code: [Select]
dd if=/dev/zero of=/swapfile bs=1M count=1024
mkswap /swapfile
swapon /swapfile

Now modify /etc/fstab so the swap is recognised at next boot:
Code: [Select]
nano /etc/fstab

If you don't have nano ( a simple text editor) you can install it with:
Code: [Select]
apt-get install nano

Add the following line to the bottom of the file:
Code: [Select]
/swapfile  swap      swap    defaults        0 0

...and try compiling again.


Okay, wow, what a process! All those XXXXXXXX.cpp files being generated.

I now have these additional files in the /spreadcoin-mn-test directory
bitcoin-qt.pro
qrc_bitcoin.cpp
spreadcoin-qt

What do I do to now run the Spreadcoin masternode wallet? (as I've tried just entering "spreadcoin-qt" at the command line like I would enter darkcoind for a DRK MN but it just returns "command not found".

That's linux, you need to tell where the file is... always...:

Code: [Select]
./spreadcoin-qt
is the right command.


Of course, that much I do know and should've realised.

So tried that and am now getting "cannot connect to X server".

Sorry for taking up your time. I probably shouldn't have attempted this as I just don't have enough knowledge around the basics to realise what's going on.

Quote
RenegadeMan are you running a GUI environment on your VPS? Because if you're not you'll want to compile spreadcoind instead. If you are you can run it with ./spreadcoin-qt from the CLI or just double click on it in your GUI file browser/windowmanager/whatever

Ah...no...not running a GUI. So I'm on the wrong track and need spreadcoind instead?

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #308 on: January 28, 2015, 03:25:08 pm »
RenegadeMan are you running a GUI environment on your VPS? Because if you're not you'll want to compile spreadcoind instead. If you are you can run it with ./spreadcoin-qt in a terminal or just double click on it in your GUI file browser/windowmanager/whatever

Yes, to build the spreadcoind you would have to go to "src" folder and then issue:

Code: [Select]
make -f makefile.unix

The qmake thing is for GUI only.


Strumpet!

  • Full Member
  • ***
  • Posts: 158
    • View Profile
Re: Masternodes Testing
« Reply #309 on: January 28, 2015, 03:29:41 pm »
Ah...no...not running a GUI. So I'm on the wrong track and need spreadcoind instead?

Yes. You can't run a GUI application in a CLI environment.  :P

Luckily, compiling the daemon is easy, and should be a lot quicker:

Navigate to the spreadcoin-mn-test/src/ directory
eg.
'cd src/'
then
'make -f makefile.unix'

...will build spreadcoind in that directory. Run with './spreadcoind' (You may need to 'chmod +x spreadcoind' first to make it executable.)

Baptism of fire!  :)

minerpage

  • Admin / Donator
  • ******
  • Posts: 115
    • View Profile
Re: Masternodes Testing
« Reply #310 on: January 28, 2015, 03:30:14 pm »
tSPR to mgwkvATo333RXpmUkPEDPvwZQGH41UCtXi for more MN's until we reach 300 8)

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #311 on: January 28, 2015, 03:33:54 pm »
Ah...no...not running a GUI. So I'm on the wrong track and need spreadcoind instead?

Yes. You can't run a GUI application in a CLI environment.  :P

Luckily, compiling the daemon is easy, and should be a lot quicker:

Navigate to the spreadcoin-mn-test/src/ directory
eg.
cd src/
then
make -f makefile.unix

...will build spreadcoind in that directory. Run with ./spreadcoind

Baptism of fire!  :)

actually, run it with
Code: [Select]
./spreadcoind -daemon so that it keeps running even if you exit the ssh session. And you'll need it running to issue commands to it (mnsecret, mnstart, etc)

Strumpet!

  • Full Member
  • ***
  • Posts: 158
    • View Profile
Re: Masternodes Testing
« Reply #312 on: January 28, 2015, 03:35:20 pm »
actually, run it with
Code: [Select]
./spreadcoind -daemon so that it keeps running even if you exit the ssh session

OK, sorry. You don't need to do that with darkcoind, I assumed spread would be the same.

girino

  • Newbie
  • *
  • Posts: 40
    • View Profile
Re: Masternodes Testing
« Reply #313 on: January 28, 2015, 03:37:52 pm »
actually, run it with
Code: [Select]
./spreadcoind -daemon so that it keeps running even if you exit the ssh session

OK, sorry. You don't need to do that with darkcoind, I assumed spread would be the same.

you are probably using
Code: [Select]
daemon=1in the darkcoin.conf, so you don't need this on the command line. That should work with spreadcoin too.

georgem

  • Tech Admin
  • ******
  • Posts: 956
    • View Profile
Re: Masternodes Testing
« Reply #314 on: January 28, 2015, 03:38:27 pm »
RenegadeMan are you running a GUI environment on your VPS? Because if you're not you'll want to compile spreadcoind instead. If you are you can run it with ./spreadcoin-qt in a terminal or just double click on it in your GUI file browser/windowmanager/whatever

If I compile and run the spreadcoind, how do I output the MN list? (the whole content of what's now visible in the Masternode-Tab within the GUI)
I think this is not possible yet, right?