Ok... I spoke to soon. Even after compiling with boost 1.64 as shown below, the solarisd -daemon runs, but when I change the masternode.conf and solaris.conf file according to the published instructions, it still doesn't work.
-------begin CLI commands entered snippett-------------
git clone
https://github.com/Solaris-Project/Solaris/cd Solaris/
sudo mkdir /boost164 && sudo chmod -R a+rwx /boost164 && wget
https://sourceforge.net/projects/boost/files/boost/1.64.0/boost_1_64_0.tar.bz2 && tar -xvf boost_1_64_0.tar.bz2 && cd boost_1_64_0/ && ./bootstrap.sh && ./b2 --prefix=/boost164 cxxflags=-fPIC cflags=-fPIC link=static install
cd ..
./autogen.sh
./configure --with-boost=/boost164/ LDFLAGS="-L/boost164/lib/" CPPFLAGS="-I/boost164/include" --with-incompatible-bdb
make V=1 -j4
---------end CLI commands entered snippett------------
then I can run the daemon fine till I try to alter the masternode.conf and solaris.conf file according to the instructions and I still get the same error below.
I tried it with one master node setup in .conf files, both of them and nothing works, the daemon just crashes.
Anybody got a clue on this?
~$ /home/host/Solaris/src/solarisd -daemon
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexica
l_castEEEEE
bad lexical cast: source type value could not be interpreted as target
solaris in AppInit()
THANK YOU!!!!! I will recompile with a local version I have for another node.!!!!! THANK YOU!!!!!!!!
The error you have is because you used the wrong version of boost. Please use boost 1.63 or greater.
Hey dev. Masternode setup does not work. I'm on the latest greatest code because my blockchain updates when I run ./solarisd -daemon, but masternode setup is broken. If people knew that anyone running VSphere could open up a console session and watch you setup your VPS live, you would all use your own servers for masternodes behind your own public IP address (preferably static), especially with the threats of meltdown and spectre, and NO.... don't believe the hype... There are no real fixes other than waiting until new hardware comes out that fixes this problem. But back to the masternode problem. This is the second time I've posted this and apparently there is nothing but noobs on this forum.
I'm using Ubuntu 16.04 LTS 64 bit server edition with boost 1.58
My solarisd -daemon runs fine without masternode setup.
Ports are routed at my enterprise edge and allowed on the servers.
I deposited 1000 solaris into 2 different addresses on my wallet where I'm running ./solarisd -daemon
Then I waited for 120 confirmations (and it's WAY past 120 at this point) before trying to setup a masternode.
I'm using CLI only and was able to retrieve all the information in the PDF instructions via ./solaris-cli commands
for the masternode.conf and solaris.conf file.
I try to start ./solarisd -daemon with the masternode.conf and solaris.conf file altered the way the instructions for the VPS show, using my external address as my external address in the solaris.conf file.
I've tried setting up both masternodes (since I have 2 labels, one for each masternode), and just one of them by commenting out the info for the second masternode and nothing works.
I don't want to use a VPS because I don't trust any server I can't get my hands on myself due to the threats of meltdown and spectre.
I want to use a server at my public IP address on the same node as my solarisd -daemon.
Is what I'm doing possible, or do I need to spin up a separate instance of solarisd -daemon, one for each masternode.
The instructions don't work when trying to substitute my public IP address, or 127.0.0.x for the localhost the solarisd -daemon resides on, or any other combination of the localhost IP(s), i.e. 127.0.0.1, 127.0.0.2, and/or my public IP address, or the actual LAN IP address (in which all are static, with the exception of using 127.0.0.1 and 127.0.0.2 per the old solaris master blob talking about the start many
process which uses 127.0.0.1 and 127.0.0.2 in the instructions.)
Any idea why I keep getting this regardless of what I do?
Once I've altered the masternode.conf and solaris.conf file per the directions with the proper IPs (and like I said, I've tried 127.0.0.1 and the LAN IP the host is assigned with for the masternode.conf file), I try to start ./solarisd -daemon at the command line, and this happens. I don't even get a chance to try and type: ./solaris-cli masternode start-alias . the daemon crashes and spits out the following message.
---begin CLI snippet----
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexica l_castEEEEE
bad lexical cast: source type value could not be interpreted as target
solaris in AppInit()
----end CLI snippet-----
I'm very well versed in networking and can do some debugging with google at my side, so if you need to use some tech lingo, go for it. I'll know what you are talking about, and if not, I'll google whatever term it is I'm missing.
