Messages

2821

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 27, 2018, 01:32:44 PM »

Oh, wait! Maybe I just misunderstood. I thought that the 'create and attach R@H' button did more than it maybe actually does.

I thought that the 'create' portion was the creation of the R@H account, and I thought that the 'attach' portion was about 'attaching' your CPID to the blockchain.

But the 'attach' part is not about the CPID, but about attaching R@H to the Boinc client! I thought it was an all-in-one button that included attaching your CPID

Excellent!  That means the test didnt fail, great.  (Because the msgbox should show any error, even Insufficient funds).

Anywhoo,  heres what Im thinking:

Case 1:
A new biblepay user who is an existing researcher on boincstats with lots of rac.  All they do is click the Associate CPID button (thats the old button that was always there).


Case 2:
A new user who doesnt use boinc.  They click the 'Create Account & Attach project' button and that does everything Except associate the cpid with the wallet.  Then We tell them to click Associate after they get boinc running.


This way we can appeal to either group without causing duplicate DCC transactions to be sent.

2822

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 27, 2018, 11:52:03 AM »

Jaap, I tried to reproduce the "associate" button not sending the collateral, and from what I see, it does still call the same old associate code and it still works.

However I do see one potential reason it didnt work for you.  Im thinking on a brand new wallet with 0, we require the BBP to be at least 2 confirms deep before it can be spent on a collateral tx.  You should have received 'insufficient funds' in the message box, and not 'welcome to BiblePay cancer mining!'. 

See if you can remember what it said?  Anyway if you retry with a confirmed balance, it will probably work fine....

2823

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 27, 2018, 11:38:01 AM »

Testing from a clean Windows 10 PC.

Push button: 'Create and Attach R@H Account'
Popup says:
Of course, you already discussed the Linux part of things with Tigo, but I'm on Windows now. So I guess the popup should also say something about installing BOINC on Windows.

Anyway, I installed BOINC but didn't run it yet, and tried the button again. The same 'Boinc not installed' popup showed. I launched BOINC and hit the button again and the wallet started a proces. It was a succes! Very awesome! Absolutely.

The wallet created the account, Boinc started downloading tasks immediately and is crunching away now.

And is my assertion correct that you don't need any BBP in your wallet to start mining this way? Of course you need it for staking (at least for now). I sent 1000 BBP to my wallet just in case, but I don't the the 1 BBP transaction you would normally see when attaching your account to the blockchain. The wallet doesn't show my CPID yet, but it hasn't been 6 blocks yet. I will check again later...
EDIT: more than six blocks have passed and the wallet still doesn't show my CPID. So I guess something went wrong? If I can do anything to troubleshoot, please let me know

Hi Jaap,

Thats awesome on the Windows test for Create New Account!  Great, we are close.
Hmm, thats very interesting the 'associate researcher with biblepay' didnt work, as I didnt change that.  Yes that still requires something like .25 bbp for it to run - and its supposed to give you an error messagebox if it fails to send the DCC transaction, and yes you are supposed to see it in the txlist even during the 6 block wait....

Let me try to reproduce that button on windows.  Its possible I accidentally removed the actual Click behavior of the button in the last version.

Yes, correct, for a new user they could start crunching, but not receive any rewards until their UTXO amount exceeds the required minimum, so they would see the task count, and the RAC, but not be in any superblocks until they stake a minimum UTXO against the associated CPID.

2824

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 26, 2018, 04:56:22 PM »

Wow! I was gone for two days and a lot has happened 

My findings:
'Current tasks' shows correctly in the wallet.

About the buttons in the 'Distributed Computing' tab:
Maybe we can change them a bit to make them more clear. Maybe something like:
-Attach existing R@H account
-Create and attach new R@H account
-Run R@H diagnostics

Maybe even put the 'Create and attach new R@H account' button first, because if we do the installation from the wallet, that's the button most new users will use.

On this computer, BOINC and the wallet were already installed and running:

Code: [Select]

Boinc Installed: Yes
Rosetta_Account: 3e10121b68e0279c03dcc38a113a32d6
Rosetta_RAC: 214.02
CPID: c852da1a620ad630b70c8ec1ccdee366
This CPID was on a non-BiblePay Team (Russian Team), and the rewards indeed seem to have droppen 10%. They used to be around 130 and they are now around 117.

I've now changed it to Team BiblePay and will see if it will pay out 100% in the future (instead of the 90% now).

Lastly, the latest Windows version currently online doesn't have the added buttons in the 'Distributed Computing' tab yet. I don't know if the windows wallet is still on 'c'?

Good, Im glad most of your tests passed!

Yeah, I think the button captions could use a little improvement.  I changed the "Add me as a researcher" to "Associate Researcher CPID with BiblePay" (thats because I didnt want people to confuse attaching a project with attaching biblepay.  I still left it first in the order- only because I feel we will have half who already have CPIDs and they just want to associate the wallet.  The newbies will have to know to do Create then Associate.  I recaptioned the Diag button to "Run R@H Diagnostics".    This will be in the next version however.

Regarding it not being there, yes, your right but since we had this emergency release today, now 1.1.5.6 is out there.  So now you can try the buttons in windows (with the old captions ...

Great on the RAC change!

2825

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 26, 2018, 07:24:27 AM »

I saved my wallet.dat using winscp, and destroyed the server
I spun up a new Vultr server in Dallas, 2 CPU this time,
Installed BiblePay, set tesnet=1 in biblepay.conf,
I couldnt sync at first, I added addnode=testnet.biblepay.org and was able to sync
Installed lubuntu-desktop
(tried to mess with VNC but I failed, grey screen)
Connected with Vultr View Console button
Installed ipfs
Installed boinc and boinc-client
Ran through the DC tab buttons, everything worked, I have 5 rosetta tasks running

Should I set back up a masternode?

Sorry to see you go through all that.  I suppose its for the better though, because you effectively tested from an empty server (in contrast to uninstalling boinc).  On a side note, I tested the feature successfully on my debian VM and on windows 7.  (Ive been doing most of my testnet testing by picking 3 of my prod sancs, and running biblepay-qt in testnet mode using a biblepaytest.conf file, that basically shuts off listen=0,testnet=1 and allows it to run side-by-side a running sanc instance). 

On the masternode, yes, I think at this point you are so close you might as well set up a hot sanc so we can do a little testing on RAC rewards.

On a side note, Ive got some VNC hosts running, although you dont need to do this, when I ran into the grey screen issue, I did this and it worked for me on ubuntu 16:
https://askubuntu.com/questions/800302/vncserver-grey-screen-ubuntu-16-04-lts
The first answer with the 8 upvotes.  It seems there are no desktop components being launched by vncserver by default.

Were you able to see the contact list and the gospellink list and navigate to a gospel link btw?

If you want to add a gospellink feel free to add one, you can scrape it from the pool 'external links'.

2826

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 10:36:23 PM »

I went to "Distributed Computing" tab,
clicked "Create and Attach R&H Account",
got a pop up "Fix BOINC Configuration" "E-mail must be populated.Password must be populated."

Entered in email and password, clicked "Create and Attach R&H Account" again
"Fix BOINC Configuration"
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Attaching Rosetta Project: Attached Successfully
Rosetta RAC: -1
CPID:"

"R&H Diagnostics" button, have to enter in email and pass and similar output
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Rosetta RAC: -1.00"

My Current Tasks on DC Tab is 0

Do I have to start boinc manually?
Im watching top and only see boinc pop up for a split second every 30 seconds

ps -ef I see /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log

Good deal, but no , you shouldnt have to manually start rosettas tasks.  When our code attaches rosetta, it launches the tasks.

I think that machine still has something wrong; (due to unclean uninstall which I think is a boinc issue)-
Let me back up a sec; I think the entire issue on that machine was that we didnt tell the user "sudo apt update" first, then the sudo apt-get install boinc boinc-client.  I think that set you into a downward spiral.

To find the problem you have to locate the boinc log file by cding to :  cd /var/lib/boinc-client
Manually running boinc
Then wait for the error, then look for where it writes the boinc log.  In there you should find something wrong.

But I think on a normal install, things should start up and the LCD indicator jump up to the task level of the machines resources.


Try going to boinc gui (boincmgr) and see if you can see any rosetta tasks running, probably not.

2827

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 09:16:27 PM »

I ran

sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get dist-upgrade -y
sudo apt-get install boinc-client -y --reinstall

and I now have a /boinc-client folder in /var/lib

=

boinccmd help now ouputs "Authorization failure: -155",

Opened QT wallet, Debug Console, exec rosettadiagnostics email pass
Boinc Installed: Yes
Rosetta_Account: c1f31****8d5954
Rosetta_RAC: -1.00

Good deal, so far it appears to be working.  -1 RAC means it doesnt 'see' rosetta crunching yet.

So now if you want to click the "Add Rosetta" button on the GUI (from the DC page in the QT wallet) - you can simulate what a new user would go through to start crunching.

Then just click Diagnostics again and see if its accurate (IE shows your Rosetta RAC).

BTW:  In the latest version, you should see a big LCD indicator of the # of Rosetta tasks in the middle of the page that are crunching.

2828

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 08:32:34 PM »

Hmmm, there is no boinc-client folder inside of /var/lib

Ran boinc command and its running, looks like I accidentally generated boinc files into the /var/lib folder haha

Some interesting output from boinc:

[---] Data directory: /var/lib
execv: No such file or directory

dir_open: Could not open directory 'slots' from '/var/lib'

rest of output just bounces from resuming or suspending computation because CPU is busy

Got it.  Ok, I would summarize this one as boinc not being installed correctly.
Please try it on a machine with boinc that works, and see if we report Boinc Installed: Yes, then with boinc uninstalled, Boinc installed: No.

Maybe the sudo apt get commands are wrong and have hosed this particular box.  But it appears boinc is not installed correctly on that box.

2829

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 07:58:38 PM »

Correct, the text inside is "can't connect to local host", yeah so Im a noob, I never use the cat command, I thought it was trying to connect to a server given the output LOL

So boinccmd help command gives same text "can't connect to local host"

boinccmd by itself outputs all the flags, but adding help parameter it says the above

Should it be --help? boinccmd --help works, boinccmd help gives cant connect message

Tested boincmgr command, BOINC Manager GUI popped up
in bottom right said looking for connection, then said disconnected

===

cd ~/.biblepaycore/SAN
boinccmd > boinctemp help 2>&1
cat boinctemp

Does the contents say the same things as:
boinccmd help

Yes, they both say: can't connect to local host

Ok, good, then its working as expected- I believe boinc is not really running.  (On the --help instead of help, no 'help' is correct, --help is the description of the help).

So if you
cd /var/lib/boinc-client
boinc


(IE run boinc from that dir) you should see boinc start and then fail after a while - it should write the fail reason to the log.
Whatever is in that log, that explains why boinc did not install correctly on that machine.

Most likely, either the triggers didnt run when you installed it or the boinc service isnt running.  If it doesnt fail after 1 minute, try the biblepay feature again while the 1st terminal is running boinc and see if it detects boinc.  If it does, then you just have a missing service (IE a bad install of boinc).

2830

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 07:16:48 PM »

Cool, okay so SAN folder exists and it has files, it has the boinctemp file, I typed cat boinctemp but it said "can't connect to local host", ok so I opened it with vi and thats the text it says inside of it

and the built up command looks something like this for linux?

sCMD =  boinccmd > [GetSANDirectory2() + "boinctemp"] help 2>&1

boinc --version
7.6.31 x86_64-pc-linux-gnu

sudo apt-get install boinc boinc-client
(7.6.31+dfsg-6ubuntu1)

So the text inside boinccmd is "can't connect to localhost"? 
Your linux box should have "cat" on it as that should be on all machines.
If you cd ~/.biblepaycore/SAN
then
cat boinctemp
You should see the contects of boinctemp?  Should match the vi version?
Yes, you got the sCMD, but lets try it a different way - try to reproduce being able to output the same info in the boinctemp file from bash:

cd ~/.biblepaycore/SAN
boinccmd > boinctemp help 2>&1
cat boinctemp

Does the contents say the same things as:
boinccmd help

?

If so maybe boinc actually isnt working, try to run 'boincmgr' to see if its installed?

2831

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 06:35:00 PM »

No worries!

Hmm so I have boinc and boinc-client installed,
the command has message "Boinc Installed: No"
I closed and reopened QT wallet and tried again, same

Server is Ubuntu 16.04 x64 with Lubuntu GUI installed hosted on Vultr

Poking at the code:
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7313
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7254

BoincCommand()
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7238

GetSANDirectory2()
https://github.com/biblepay/biblepay/blob/87d751ea7eee9c97ded2b747b312253dc772f238/src/podc.cpp#L327

sOS
https://github.com/biblepay/biblepay/blob/8617e91c0d134c3300285bcf744e359688e49428/src/init.cpp#L1211
"LIN", "WIN" or "MAC"

Code: [Select]

std::string sPath = GetSANDirectory2() + "boinctemp";
// Boinc sends some output to stderr, some to stdout

std::string sEXEPath = sOS == "WIN" ? "\"c:\\program files\\BOINC\\boinccmd\"" : "boinccmd";

std::string sCmd = sEXEPath + " >" + sPath + " " + sCommand + " 2>&1";
Random question: if computer is Windows, boinccmd is looked for on the C: drive?

I still need to look into the GetSANDirectory2() some more and then test running the sCMD I build

Im able to run boinccmd command with no parameters, it gives help output

Code: [Select]

std::string GetSANDirectory2()
{
boost::filesystem::path pathConfigFile(GetArg("-conf", "biblepay.conf"));
     if (!pathConfigFile.is_complete()) pathConfigFile = GetDataDir(false) / pathConfigFile;
boost::filesystem::path dir = pathConfigFile.parent_path();
std::string sDir = dir.string() + "/SAN/";
boost::filesystem::path pathSAN(sDir);
if (!boost::filesystem::exists(pathSAN))
{
boost::filesystem::create_directory(pathSAN);
}
return sDir;
}
I cant find the function pathConfigFile() hmm
Is this weird C++ syntax for variable creation? lol

GetArg()
https://github.com/biblepay/biblepay/blob/082a12b0e4727c2df5363dfa14889b41b4957d3a/src/util.cpp#L473

Very good diagnosis, thanks.

So on the windows question: Yes, on windows boinc doesnt seem to be in the PATH by default, so we prefix the entire path in and use the default drive.  I realize if a user puts boinc in another drive, we fail on windows for now.  But it works on my windows machine for a good start.  On linux and mac 'boinccmd' should be in the path. 

Now that is strange your boinccmd is not working- we can diagnose this.  First lets see if biblepay created your san directory.

cd ~/.biblepaycore/SAN
ls -l

You should see a 'boinctest' file.  cat it to the screen, see if it has the boinc help output?  Its supposed to have a timestamp of right when you typed 'exec rosettadiagnostics user pass'.  See if it does get written to?  Does it contain the text 'projectattach'?  If it doesnt, let me know if you have a different version of boinc and Ill compare the output to mine.  Yes, we should get this working on your ubuntu 64, so we can work across more platforms.

The pathConfigFile just returns the full path to :  ~/.biblepaycore/, thats where the blocks directory is.  (Other parts of the code add in 'testnet3' to actually respect the blocks directory testnet is using). We add the 'SAN' suffix for Sanctuary Quorum files and other temporary stuff used by IPFS. 

2832

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 05:23:49 PM »

1.  Diagnosing Rosetta:  type 'exec rosettadiagnostics email password',

"Results": "Boinc Installed: No\n"
"Errors": "Boinc is not installed. Please run 'sudo apt-get install boincmgr boinc'

sudo apt-get install boincmgr boinc
unable to locate package: boincmgr

sudo apt-get update & sudo apt-get upgrade

Now its installing a bunch of stuff, Im a Linux newbie am I doing this right? LOL

Sorry, wherever I wrote 'boincmgr', it should have been 'boinc boinc-client', that installs boinc and boinc gui.

boincmgr is the name of the UI app boinc installs....

2833

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 03:48:00 PM »

I just updated the spork for NonBiblePayTeamPercentage to 90%, lets please test a non biblepay team superblock payout.

2834

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 03:43:52 PM »

i cant sync nothing

Please try this:

telnet testnet.biblepay.org 40001

On my screen it is succesful.  That means for you you should be able to sync.
What is your testnet node IP, let me see if banned?

2835

TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

« on: September 25, 2018, 03:30:52 PM »

addnode=dns2.biblepay.org
addnode=testnet.biblepay.org
testnet=1
genproclimit=0


i have this

Are you synced to 73635?  All 3 of my nodes are synced.