 Show Posts
|
|
Pages: [1] 2 3
|
When trying to run the new wallet installer from Biblepay.org, I get an error:
Installer integrity check has failed.
Also a question about the new dual mining, is it required to use the CLI miner or does the new wallet dual mine as well? Thanks!
A) Could you please provide the link that you downloaded that from - and does the error occur when you first execute the installer? EDIT: I just upgraded my home windows node without a problem - although remember everyone to move your folder to %appdata%\biblepay when doing this upgrade. B) You can still solo mine after the next mandatory height, using the core wallet, but it is vehemently unprofitable because it is 40* slower than xmrig. For all intents and purposes people will need to mine with xmrig-bbp after that height: https://wiki.biblepay.org/Upgrade_to_RandomXSo does this mean moving forward all mining is pool mining or can the external miner solo mine also. Sorry late to the game here but have been helping my brother's doctor office get the supplies they need to be able to fight this wonderful virus that is going on. If anyone has a link on how to both Solo and Pool mine that would be awesome as I am only back at my house for another 24 hours or so before going to get more necessary supplies. Thanks |
|
|
|
southXchange github link is pointing to old site Anyone reached out to SouthXchange about the BBP wallet being stuck on block 162029?
how do you which block sx is on? got link? When you go into the coin you can look at wallet status.. Last night it was online and stuck there.. Today the wallet is listed as offline.. |
|
|
|
|
Anyone reached out to SouthXchange about the BBP wallet being stuck on block 162029?
|
|
|
|
Hope this helps, for the Iquidus explorer, I have a crontab that tries to run the biblepay daemon every 5 minutes: crontab -e */5 * * * * /home/biblepay-evolution/src/biblepayd > /dev/null 2>&1 Gave this to Rogue a little earlier tonight. You could use this also #!/bin/bash # checkprocess.sh PROCESS=<insert the name of what process you are kicking off> check_running_process() { sudo ps -ef | grep -v grep | grep $PROCESS > /dev/null result=$? #echo "exit code: ${result}" if [ "${result}" -eq "0" ] ; then echo "Process is Running" return 1 else echo "Process is Stopped" return 0 fi } echo Current Date and Time is: date +"%Y-%m-%d %T" if (check_running_process); then #Want to make sure it is not already being started sleep 10 if (check_running_process); then echo "Restarting Process now" #syntax to restart the process #insert your command to restart the process that is not running <-- Here is the command you would put in to start the process if it has died fi fi here is my change if you are running several MN on same Linux : ./checkprocess.bash "biblepayd" "/sbin/runuser -l bbp -c './mn/biblepayd'"
root@station:~# cat checkprocess.bash
#!/bin/bash
# checkprocess.sh
echo process to check = $1
echo running command = $2
PROCESS=$1
check_running_process()
{
sudo ps -ef | grep -v grep | grep -v checkprocess | grep $PROCESS > /dev/null
result=$?
#echo "exit code: ${result}"
if [ "${result}" -eq "0" ] ; then
echo "Process is Running"
return 1
else
echo "Process is Stopped"
return 0
fi
}
if (check_running_process); then
#Want to make sure it is not already being started
sleep 10
if (check_running_process); then
echo "Restarting Process now"
#syntax to restart the process
#insert your command to restart the process that is not running <-- Here is the command you would put in to start the process if it has died
$2
fi
fi
In crontab -e */5 * * * * /root/checkprocess.bash "biblepayd" "/sbin/runuser -l bbp -c './mn/biblepayd'" > /dev/null 2>&1
Glad this quick script could help you guys. I would think with multiple masternodes you might be able to look at ports but this should indeed do the trick. Glad i could help others here |
|
|
|
Could someone please give us an update on Tokok, if they are working yet?
I find it very unsettling to not receive a reply from them in 24 hours.
Let me know and tomorrow if we have not heard back, lets talk about forming a grievance.
Have not heard from them either and no deposits have gone through at this point in time Same here. Support chat says that "all agents are busy" when they were available in few minutes some weeks ago Ok thanks guys. Well this is pretty serious for them not to reply to us (with no mandatory upgrades yet) and a 2btc investment. Checking my inbox, nothing yet. Ill send them a new high priority email now. So we have two people here that cant even withdraw the BBP, correct? Togo and JSheets? I have deposits in flight to them. Been that way for 6 days. The wallet is not taking them in |
|
|
|
Could someone please give us an update on Tokok, if they are working yet?
I find it very unsettling to not receive a reply from them in 24 hours.
Let me know and tomorrow if we have not heard back, lets talk about forming a grievance.
Have not heard from them either and no deposits have gone through at this point in time |
|
|
|
echo Current Date and Time is: date +"%Y-%m-%d %T"
Cool thanks! The time stamp maybe isn't working exactly? # ./checkprocess.sh & [1] 21935 me@ubuntu:~# Current Date and Time is: date +%Y-%m-%d %T Process is Running I threw this one together quickly. Sorry if that is not working but I would guess the rest is and should be helpful in keeping pools up and running |
|
|
|
Hope this helps, for the Iquidus explorer, I have a crontab that tries to run the biblepay daemon every 5 minutes: crontab -e */5 * * * * /home/biblepay-evolution/src/biblepayd > /dev/null 2>&1 Gave this to Rogue a little earlier tonight. You could use this also #!/bin/bash # checkprocess.sh PROCESS=<insert the name of what process you are kicking off> check_running_process() { sudo ps -ef | grep -v grep | grep $PROCESS > /dev/null result=$? #echo "exit code: ${result}" if [ "${result}" -eq "0" ] ; then echo "Process is Running" return 1 else echo "Process is Stopped" return 0 fi } echo Current Date and Time is: date +"%Y-%m-%d %T" if (check_running_process); then #Want to make sure it is not already being started sleep 10 if (check_running_process); then echo "Restarting Process now" #syntax to restart the process #insert your command to restart the process that is not running <-- Here is the command you would put in to start the process if it has died fi fi |
|
|
|
I'm attempting to withdraw some coins out of Tokok for the first time (about $200 worth), They are stuck in "Pending approval" status the past ~30 minutes "Notice - Only after the withdrawal request pass the system audit will it be made successfully - Withdrawal of some currencies requires manual review. Review Time: 9:30-02:00 (UTC+8)" https://www.reddit.com/r/Nash/comments/c0rpql/anyone_ever_have_delays_withdrawing_from_tokok/I will report back how it goes, looks like they'll be doing manually reviewing in an hour UPDATE: An hour and a half after I posted this, All my withdrawals were approved, got emailed approval for each one So I have deposits from Leopool going to TOKOK and they are not there.. Rogue sent me the list of deposits last night and they have not made it to the account. Are we sure that their wallet is in a good condition? How can we tell? Appears that I have not been getting deposits to tokok since 11/28.. I just tried a manual one to see and waiting. Can anyone else try and make a deposit. Seems their wallet is hung Tokok says a deposit will show up in 6 confirmations. If it is not, it is possible they are stuck on a daily superblock. If you look up your deposit address in chainz or explorer.biblepay.org and it shows up, then the exchange wallet may be experiencing delays or issues. In my opinion they are indeed stuck since 11/28. I have logged a case with them, but if anyone else has more pull feel free to try. Thanks |
|
|
|
I'm attempting to withdraw some coins out of Tokok for the first time (about $200 worth), They are stuck in "Pending approval" status the past ~30 minutes "Notice - Only after the withdrawal request pass the system audit will it be made successfully - Withdrawal of some currencies requires manual review. Review Time: 9:30-02:00 (UTC+8)" https://www.reddit.com/r/Nash/comments/c0rpql/anyone_ever_have_delays_withdrawing_from_tokok/I will report back how it goes, looks like they'll be doing manually reviewing in an hour UPDATE: An hour and a half after I posted this, All my withdrawals were approved, got emailed approval for each one So I have deposits from Leopool going to TOKOK and they are not there.. Rogue sent me the list of deposits last night and they have not made it to the account. Are we sure that their wallet is in a good condition? How can we tell? Appears that I have not been getting deposits to tokok since 11/28.. I just tried a manual one to see and waiting. Can anyone else try and make a deposit. Seems their wallet is hung |
|
|
|
Does anyone know what "not yet redeemed" means when looking in the explorer?? Is there something going on that is keeping transactions from getting to various wallets? I have never seen this before and these are from transactions a few days ago. Thoughts? Here is a link with an example https://chainz.cryptoid.info/bbp/tx.dws?1178539.htmUpdate : These seem to be from LEO pool. |
|
|
|
Sun, this does not mention the qt wallet. Is the qt wallet no longer needed for solo mining? If it is needed does qt wallet need to have a mining thread running still? |
|
|
|
|
Leopool is down again. Stratum unable to connect.
|
|
|
|
|
Anyone know if leopool is down??
|
|
|
|
Sun, you were asking about 'stratum requested a work restart'. So I went through a certain amount of pain trying to reduce the chatiness and learned that in stratum its not as simple as just setting a poll setting and resetting the work restart request (as one would believe because of the interval passing). There are many factors that influence the work restart: rpc polling duration, merkle root changes (or tx list changes), someone mining the current rounds difficulty, stratum timeout between client-server, etc.
So basically what we have now when someone goes to run a pool, we have some pretty good defaults setup (they can be overridden in the config files). The client polls for new blocks every 30 seconds, but it also finds new transactions when shares are submitted. The biggest issue here is the bbpminer external miner has a default timeout (that I have not changed) of 120 seconds, and, if you dont talk to the server within 120 seconds, the client hangs up and starts a new stratum connection. So the server must always send something to client within that amount of time. (IE refresh the work).
So in our case, we send updates when either someone found a pobh solution for that diff, or, the 115 seconds is about to expire - then we send new work.
In the future I might increase the timeout on the client then we can increase the timeout on the server later, but it appears to be working relatively well now.
So this is why your client will sometimes hash longer (or shorter) and getting the 'request a work restart' message.
Nice work on this Rob. Stability seems to really be improving. Question for you on payments. I have 4 workers that have been running against the pool for a few days. What i have noticed is that when payments are made only 1 of 4 workers ever gets a payment eventhough they have all been submitting shares. Are you grouping payments by source ips as all of mine would be natted to the same source ip possibly? Just seems strange only 1 would get paid. Let me know. Thanks You have 4 workers running on which pool is it? NOMP Send me the addresses, can't check anything with no data. Sent |
|
|
|
Sun, you were asking about 'stratum requested a work restart'. So I went through a certain amount of pain trying to reduce the chatiness and learned that in stratum its not as simple as just setting a poll setting and resetting the work restart request (as one would believe because of the interval passing). There are many factors that influence the work restart: rpc polling duration, merkle root changes (or tx list changes), someone mining the current rounds difficulty, stratum timeout between client-server, etc.
So basically what we have now when someone goes to run a pool, we have some pretty good defaults setup (they can be overridden in the config files). The client polls for new blocks every 30 seconds, but it also finds new transactions when shares are submitted. The biggest issue here is the bbpminer external miner has a default timeout (that I have not changed) of 120 seconds, and, if you dont talk to the server within 120 seconds, the client hangs up and starts a new stratum connection. So the server must always send something to client within that amount of time. (IE refresh the work).
So in our case, we send updates when either someone found a pobh solution for that diff, or, the 115 seconds is about to expire - then we send new work.
In the future I might increase the timeout on the client then we can increase the timeout on the server later, but it appears to be working relatively well now.
So this is why your client will sometimes hash longer (or shorter) and getting the 'request a work restart' message.
Nice work on this Rob. Stability seems to really be improving. Question for you on payments. I have 4 workers that have been running against the pool for a few days. What i have noticed is that when payments are made only 1 of 4 workers ever gets a payment eventhough they have all been submitting shares. Are you grouping payments by source ips as all of mine would be natted to the same source ip possibly? Just seems strange only 1 would get paid. Let me know. Thanks You have 4 workers running on which pool is it? NOMP |
|
|
|
Sun, you were asking about 'stratum requested a work restart'. So I went through a certain amount of pain trying to reduce the chatiness and learned that in stratum its not as simple as just setting a poll setting and resetting the work restart request (as one would believe because of the interval passing). There are many factors that influence the work restart: rpc polling duration, merkle root changes (or tx list changes), someone mining the current rounds difficulty, stratum timeout between client-server, etc.
So basically what we have now when someone goes to run a pool, we have some pretty good defaults setup (they can be overridden in the config files). The client polls for new blocks every 30 seconds, but it also finds new transactions when shares are submitted. The biggest issue here is the bbpminer external miner has a default timeout (that I have not changed) of 120 seconds, and, if you dont talk to the server within 120 seconds, the client hangs up and starts a new stratum connection. So the server must always send something to client within that amount of time. (IE refresh the work).
So in our case, we send updates when either someone found a pobh solution for that diff, or, the 115 seconds is about to expire - then we send new work.
In the future I might increase the timeout on the client then we can increase the timeout on the server later, but it appears to be working relatively well now.
So this is why your client will sometimes hash longer (or shorter) and getting the 'request a work restart' message.
Nice work on this Rob. Stability seems to really be improving. Question for you on payments. I have 4 workers that have been running against the pool for a few days. What i have noticed is that when payments are made only 1 of 4 workers ever gets a payment eventhough they have all been submitting shares. Are you grouping payments by source ips as all of mine would be natted to the same source ip possibly? Just seems strange only 1 would get paid. Let me know. Thanks |
|
|
|
|
Is the NOMP pool down for a specific reason?
|
|
|
|
@jsheets1970 from mining the previous method I have multiple copies of my wallet running. some on linux, some on Windows 10. For those getting errors when running the external miner please be aware that all the wrinkles are not yet ironed out. This is a normal message if you forgot to unlock your wallet for mining OR your abnweight (minimum 125,000 abnweight) is too low and the miner is waiting for it to reach the minimum limit of 125k abnweight again: json_rpc_call failed, retry after 30 seconds
BBP Core Mining Error: Wallet Locked/ABN Required you will also get this one and a few others that "fix" themselves: [2019-10-15 21:06:09] HTTP request failed: Send failure: Broken pipe while this one is a mystery to me, I am sure that it will be looked into and resolved soon: (This is what I found while leaving the external miner running overnight with no abnweight. However it did seem to recover at one point only to error out again later.) KJV Loaded
Using bbpminer version 1004
Erroring out
Erroring out
Erroring out
Erroring out
Erroring out It also seems the external miner could use a "standby" type of connection/message as when the abnweight is too low it keeps thinking the connection to the wallet died and makes new connections every few seconds. So I did find one with Linux miner and Linux wallet so I am sure that is working well. Sunk made a great point about AVX/AVX2.. We definitely do not want to rule out the people that might have older machines that do not support AVX2.. I believe other miners have handled this issue as I believe, and I might be mistaken, some AMD chips do not support AVX2 |
|
|
|
|
