BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 119.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on July 14, 2019, 05:20:56 PM

Quote from: Gilligan_M on July 14, 2019, 05:09:29 PM

Quote from: bible_pay on July 14, 2019, 04:55:46 PM

Quote from: Gilligan_M on July 14, 2019, 04:52:09 PM

If there was something I could be curious about, it may be ABN randomly eaten out of my wallet (pool confirms that I didn't have a block found recently) as my weight went from 800k to 400k (not a mining issue, but just curious as to where it went) Is it a part of ABN funding for the funded miners?

When you pool mine, a pool miner could actually use your ABN to solve their block. (So it wouldnt be that you solved the pool block).

The only thing I can suggest is if you ask us to write a Spent ABN report, then you could see where they were used. Do you want us to write that?

Sure, could it be emailed? Also, it's for the sake of curiosity so don't let it impede with any important matters.

I just realized we have a report in the wallet that shows sent GSC transmissions for one day (this shows donations, POG points, Healing points) and used coin age on GSC transmissions.

I just modified it to report for the last 7 days on both GSC transmissions and ABN hits. Then you can see anything that consumes coin age, the height, the date and the txid.

You can also test the new version at the same time; please give us about 30 mins to release it.

I see for example today my ABN was used to solve block 131665 in the pool - but the solver was murof.core7. What you can do is get the height from the 'exec sentgsc' report (when its released) and then compare it to the blocks history report in the pool.

OK, windows 1.4.4.2c is out there, please test it:

exec sentgsc

To see the last 7 days of GSCs & ABNs.

Also, please test the dual mining feature again.

Also please ensure no crash occurs in windows 10.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 14, 2019, 05:09:29 PM

Quote from: bible_pay on July 14, 2019, 04:55:46 PM

Quote from: Gilligan_M on July 14, 2019, 04:52:09 PM

If there was something I could be curious about, it may be ABN randomly eaten out of my wallet (pool confirms that I didn't have a block found recently) as my weight went from 800k to 400k (not a mining issue, but just curious as to where it went) Is it a part of ABN funding for the funded miners?

When you pool mine, a pool miner could actually use your ABN to solve their block. (So it wouldnt be that you solved the pool block).

The only thing I can suggest is if you ask us to write a Spent ABN report, then you could see where they were used. Do you want us to write that?

Sure, could it be emailed? Also, it's for the sake of curiosity so don't let it impede with any important matters.

I just realized we have a report in the wallet that shows sent GSC transmissions for one day (this shows donations, POG points, Healing points) and used coin age on GSC transmissions.

I just modified it to report for the last 7 days on both GSC transmissions and ABN hits. Then you can see anything that consumes coin age, the height, the date and the txid.

You can also test the new version at the same time; please give us about 30 mins to release it.

I see for example today my ABN was used to solve block 131665 in the pool - but the solver was murof.core7. What you can do is get the height from the 'exec sentgsc' report (when its released) and then compare it to the blocks history report in the pool.

Gilligan_M

newbie

Activity: 28

Merit: 0

Quote from: bible_pay on July 14, 2019, 04:55:46 PM

Quote from: Gilligan_M on July 14, 2019, 04:52:09 PM

If there was something I could be curious about, it may be ABN randomly eaten out of my wallet (pool confirms that I didn't have a block found recently) as my weight went from 800k to 400k (not a mining issue, but just curious as to where it went) Is it a part of ABN funding for the funded miners?

When you pool mine, a pool miner could actually use your ABN to solve their block. (So it wouldnt be that you solved the pool block).

The only thing I can suggest is if you ask us to write a Spent ABN report, then you could see where they were used. Do you want us to write that?

Sure, could it be emailed? Also, it's for the sake of curiosity so don't let it impede with any important matters.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 14, 2019, 04:52:09 PM

If there was something I could be curious about, it may be ABN randomly eaten out of my wallet (pool confirms that I didn't have a block found recently) as my weight went from 800k to 400k (not a mining issue, but just curious as to where it went) Is it a part of ABN funding for the funded miners?

When you pool mine, a pool miner could actually use your ABN to solve their block. (So it wouldnt be that you solved the pool block).

The only thing I can suggest is if you ask us to write a Spent ABN report, then you could see where they were used. Do you want us to write that?

Gilligan_M

newbie

Activity: 28

Merit: 0

If there was something I could be curious about, it may be ABN randomly eaten out of my wallet (pool confirms that I didn't have a block found recently) as my weight went from 800k to 400k (not a mining issue, but just curious as to where it went) Is it a part of ABN funding for the funded miners?

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 14, 2019, 02:33:49 PM

Quote from: bible_pay on July 14, 2019, 02:20:17 PM

Quote from: Gilligan_M on July 14, 2019, 01:41:41 PM

Afternoon, I've had two silent crashes on win 10, one occuring about 6am EST, and another around 2:30pm EST.

Does this mean in your case the 1.4.4.1 version didnt do anything for windows 10 stability, and you are just as unstable as you were before we started adding ABNs?

Also, did running with litemode=1 change anything?

Also, what exec getabnweight version do you show? (It should be 2.x)?

15:31:54

exec getabnweight 125000 1

15:31:54

{

"total_required 125000.00": 194713
}

15:32:01

getmininginfo

15:32:01

Code:

{
  
  "abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

ABN appears to be fine, on the debug.log it was similar to the ones that I have posted to you before as well.

At first I thought it was because I pushed my theadlimit up to 8 from 7, utilizing 100% of my CPU, but it occured again when I was only running 7 threads.

I have not tried litemode yet, I will give it a go now (restarting miner.)

quick edit: I'd have to say the miner is 90% more stable than what it was initially. It ran for a day and a half before the early morning crash.

another edit: I switched on litemode, (litemode=1 in biblepay.conf) but I had to RPC the miner to start mining (setgenerate true) after unlocking my encrypted wallet. (It was giving me this error even after unlocking the wallet)

15:38:18

getmininginfo

15:38:18

{

"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RM_07-14-2019 19:37:43; RMC_07-14-2019 19:37:43; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:43; RMC_07-14-2019 19:37:43; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}

"ABN appears to be fine, on the debug.log it was similar to the ones that I have posted to you before as well."

-> I believe most of our ABN fringe case issues are solved as Ive stopped hearing complaints on that - and JSheets has been testing that with me via email- and we are down to the final problem that him and Borg are having - the wallet uses the internal ABN, switches to Funded when it needs to and never switches back - I just debugged that and found the bug - re-releasing a new release for that issue now.

At first I thought it was because I pushed my theadlimit up to 8 from 7, utilizing 100% of my CPU, but it occured again when I was only running 7 threads.
I have not tried litemode yet, I will give it a go now (restarting miner.)
quick edit: I'd have to say the miner is 90% more stable than what it was initially. It ran for a day and a half before the early morning crash.

-> OK, this is good to know the stability increased by 90% as of this weeks releases. Because we are using a new TestBlockValidity routine, and I was wondering if that helped stability on Windows10. Let me try to hone in on that now, for this next release, we will try applying this change a little further and let me know if stability increases on Win10 after this next release.

another edit: I switched on litemode, (litemode=1 in biblepay.conf) but I had to RPC the miner to start mining (setgenerate true) after unlocking my encrypted wallet. (It was giving me this error even after unlocking the wallet)

-> Regarding this unlock error message, this should only happen when the wallet cold boots, but if you give it a few minutes of mining, the errors clear and it adjusts (to a locked or non locked wallet), including - the dual-mining feature - it takes a few minutes for errors to clear, etc.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: dave_bbp on July 14, 2019, 02:32:48 PM

Quote from: bible_pay on July 14, 2019, 01:23:50 PM

Did it silently exit or was there an exception on the screen? The screen exception is probably the most helpful in this case.

Is this the latest 64 bit version from yesterday or the day before (1441), and what is the 'version' from 'exec getabnweight'?
Log is not revealing.

Also, I still need to know if the "old crash" (pre ABN) that you experienced on windows 10 went away in this new version - IE did it just crash once this time and its been working and stable and solved?

Nope, just silently exiting. getabnweight shows version 2.4 (client is latest from webpage). Some time ago it exited again, but log isn't really helpful again.

I think I'll now go back to Win7 compatibility mode and leaving the second workerid commented out, let's see if it's stable over night.

Ok, and on win7 compatibility mode, is that actually keeping it from crashing? That would be a huge clue for us if it is.

I might have to go out and buy or build a windows10 box.

bbptoshi

copper member

Activity: 39

Merit: 0

Quote from: MIP on July 03, 2019, 02:29:24 PM

Quote from: bbptoshi on July 02, 2019, 09:46:11 PM

Thanks. I did the 1 click sanctuary script and got version 1.4.3.3. What would I do in this case?

This means something went wrong when replacing older binaries, as the current published version is 1.4.3.9.
Try to stop daemon manually then, download latest script version and then run

./masternode-setup.sh -u -n

This should run an unattended update.

Thanks MIP. Sorry, I meant originally I did that and got 1.4.3.3. I am simply running your script again now to upgrade. Thanks!

edit: It worked perfectly, and even auto-started. Thanks!

Gilligan_M

newbie

Activity: 28

Merit: 0

Quote from: bible_pay on July 14, 2019, 02:20:17 PM

Quote from: Gilligan_M on July 14, 2019, 01:41:41 PM

Afternoon, I've had two silent crashes on win 10, one occuring about 6am EST, and another around 2:30pm EST.

Does this mean in your case the 1.4.4.1 version didnt do anything for windows 10 stability, and you are just as unstable as you were before we started adding ABNs?

Also, did running with litemode=1 change anything?

Also, what exec getabnweight version do you show? (It should be 2.x)?

15:31:54

exec getabnweight 125000 1

15:31:54

{
  "Command": "getabnweight",
  "version": 2.2,
  "weight": 880160.7734490741,
  "total_required": 395461,
  "coin_age_data_pre_select": "1000.0000(2.05)=[2046.12] depth=434, 1270.5400(2.09)=[2651.10] depth=443, 192442.9022(2.09)=[401718.22] depth=443, ",
  "weight 125000.00": 406415.4386111111,
  "total_required 125000.00": 194713
}

15:32:01

getmininginfo

15:32:01

{
  "blocks": 131714,
  "currentblocksize": 1855,
  "currentblocktx": 1,
  "difficulty": 2898.175787728027,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 7,
  "networkhashps": 448849.7124697737,
  "hashps": 126001.257634149,
  "minerstarttime": "07-14-2019 18:41:58",
  "hashcounter": 378314114,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
  "poolinfo2": "Submitting Solution 07-14-2019 19:31:10; Submitting Solution 07-14-2019 19:31:09; Submitting Solution 07-14-2019 19:31:09; Submitting Solution 07-14-2019 19:31:09; ",
  "poolinfo3": "",
  "abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

ABN appears to be fine, on the debug.log it was similar to the ones that I have posted to you before as well.

At first I thought it was because I pushed my theadlimit up to 8 from 7, utilizing 100% of my CPU, but it occured again when I was only running 7 threads.

I have not tried litemode yet, I will give it a go now (restarting miner.)

quick edit: I'd have to say the miner is 90% more stable than what it was initially. It ran for a day and a half before the early morning crash.

another edit: I switched on litemode, (litemode=1 in biblepay.conf) but I had to RPC the miner to start mining (setgenerate true) after unlocking my encrypted wallet. (It was giving me this error even after unlocking the wallet)

15:38:18

getmininginfo

15:38:18

{
"blocks": 131716,
"currentblocksize": 1753,
"currentblocktx": 1,
"difficulty": 3169.410964597423,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 7,
"networkhashps": 446194.0693028863,
"hashps": 0,
"minerstarttime": "07-14-2019 19:37:43",
"hashcounter": 0,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RM_07-14-2019 19:37:43; RMC_07-14-2019 19:37:43; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:44; RMC_07-14-2019 19:37:43; RMC_07-14-2019 19:37:43; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; Unable to Create ABN: Sorry, the wallet must be unlocked to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}

dave_bbp

jr. member

Activity: 405

Merit: 3

Quote from: bible_pay on July 14, 2019, 01:23:50 PM

Did it silently exit or was there an exception on the screen? The screen exception is probably the most helpful in this case.

Is this the latest 64 bit version from yesterday or the day before (1441), and what is the 'version' from 'exec getabnweight'?
Log is not revealing.

Also, I still need to know if the "old crash" (pre ABN) that you experienced on windows 10 went away in this new version - IE did it just crash once this time and its been working and stable and solved?

Nope, just silently exiting. getabnweight shows version 2.4 (client is latest from webpage). Some time ago it exited again, but log isn't really helpful again.

I think I'll now go back to Win7 compatibility mode and leaving the second workerid commented out, let's see if it's stable over night.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: kudos_mpm on July 14, 2019, 10:37:09 AM

Quote from: bible_pay on July 14, 2019, 09:56:04 AM

Quote from: kudos_mpm on July 14, 2019, 09:53:20 AM

Quote from: bible_pay on July 14, 2019, 08:16:34 AM

Quote from: kudos_mpm on July 14, 2019, 01:33:11 AM

Quote from: bible_pay on July 13, 2019, 09:16:30 AM

Quote from: jsheets1970 on July 13, 2019, 08:44:26 AM

Quote from: kudos_mpm on July 13, 2019, 04:45:16 AM

windows 10(64bit) wallet 1.4.4.1(h) cant connet to the pool.. I dont have problem connecting to the pool on windows 7 (64bit)

addnode=explorer.biblepay.org

pool=http://pool.biblepay.org

poolport=80

workerid=KMIS *note (Funded worker)

genproclimit=60

minersleep=0

gen=1

----------------------------

"blocks": 131417,
  "currentblocksize": 2484,
  "currentblocktx": 2,
  "difficulty": 3493.889791328252,
  "errors": "",
  "pooledtx": 2,
  "chain": "main",
  "genproclimit": 60,
  "networkhashps": 454494.8052647252,
  "hashps": 0,
  "minerstarttime": "07-13-2019 09:25:23",
  "hashcounter": 0,
  "pooledtx": 2,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti

Paste the full output of getnining info. Looks to me like it could not find your miner name and reverted you to solo mining or your use is not listed as funded. So grab a snapshot of your worker list also. That might be setup wromg

Yes, and I see a lot of windows10 users appear to not edit the correct biblepay.conf file.

Please navigate to:
%appdata%\biblepayevolution

Create the biblepay.conf there. Then look at it in DOS, and ensure its called "biblepay.conf" not "biblepay.conf.conf.txt" etc.

Happy mining!

im sure im on the right biblepay.conf... also looked it at DOS, it doest NOT have the .TXT extention.

I see the problem; please change pool=http to pool=https:// (Evo only supports HTTPS).
Remove poolport also.

already replaced http to https and omitted poolport. same im on solo mining. windows 10 64bit... win7 64bit no problem

Then please try 'genproclimit=9' in your config file, and restart and confirm your getmininginfo shows 9 for genproclimit?

yes my genproclimit became 9 in getmininginfo. but poolmining is still false.

Ok good, at least we know the biblepay.conf is the exact and correct one.

Could you try this:

First, delete the contents of your biblepay.conf in notepad.
Then re-type all of it with one between each row.

Then re-save it and try again.

If it does not connect to the pool, please paste the contents here.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 14, 2019, 01:41:41 PM

Afternoon, I've had two silent crashes on win 10, one occuring about 6am EST, and another around 2:30pm EST.

Does this mean in your case the 1.4.4.1 version didnt do anything for windows 10 stability, and you are just as unstable as you were before we started adding ABNs?

Also, did running with litemode=1 change anything?

Also, what exec getabnweight version do you show? (It should be 2.x)?

Borgholio

newbie

Activity: 99

Merit: 0

Quote from: Borgholio on July 14, 2019, 11:07:51 AM

For me it seems that the wallet prefers the funded ABN instead of the unfunded. Exec getabnweight shows I have over 400k but it still goes for the funded worker instead. Also in a maybe-related note, when I disabled the funded ABN worker in my config file last night, it seems I stopped mining about 4 hours ago even though I have enough ABN.

As an update, I'm mining normally again. Before I had the following error when I ran getmininginfo:

"gsc_errors": "low abn weight 0",

That error has since vanished, so the gsc could somehow have been interfering with my ABN. Although the whole time I was getting this notice so I thought it was ok:

"abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",

Exec getabnweight was showing this:

{
"Command": "getabnweight",
"version": 2.4,
"weight": 492855.5429745371,
"total_required": 237881
}

Gilligan_M

newbie

Activity: 28

Merit: 0

Afternoon, I've had two silent crashes on win 10, one occuring about 6am EST, and another around 2:30pm EST.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Borgholio

newbie

Activity: 99

Merit: 0

For me it seems that the wallet prefers the funded ABN instead of the unfunded. Exec getabnweight shows I have over 400k but it still goes for the funded worker instead. Also in a maybe-related note, when I disabled the funded ABN worker in my config file last night, it seems I stopped mining about 4 hours ago even though I have enough ABN.

kudos_mpm

newbie

Activity: 14