Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - putzlappen

Pages: [1] 2
Mining / Re: Mining limited to 40 Cores?
« on: January 19, 2018, 03:44:10 AM »
My advice: setup a second wallet and miner in a docker image, that's the easiest way to setup another wallet at the same time on the same ubuntu system.

Might help:

Big Thanks @Lichtsucher for this great idea,

i will try it with your docker container!

Mining / Mining limited to 40 Cores?
« on: January 18, 2018, 07:51:40 AM »
In the last hours i setup two servers with each 64 CPU-Cores. I install Ubuntu and the Wallet Version, wrote the config for 64 Cores an then: poolmining: false:o

It seems that the max cores that i can use (ans setup in con-file) got a cap at 40 ! If i write more in the conf file i get an pool-error back.
What is the reason for that? At the moment i use only 2/3 of all Power...

Mining / Re: Trouble Getting Miner to Start
« on: January 16, 2018, 09:47:04 PM »
Hello all, I need some help setting up my miner.  I followed the Reddit post but it does not appear to be mining in a pool.

So far, I have downloaded the windows 64-bit exe wallet.  I created my biblepay.config file using "One Click Mining".  The config file is as follows:

I set up a worker in the mining pool which is GatorFan in the config file noted above.

My getmininginfo command returns the following:

  "blocks": 0,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 4.656542373906925e-009,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 0,
  "hashps": 0,
  "minerstarttime": "01-16-2018 15:02:49",
  "hashcounter": 0,
  "competetive_mining": true,
  "competetivemining_hash_counter": 0,
  "global_competetive_mining_tithe": 0,
  "competetive_mining_ratio": 0,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 0,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false

I am not sure what my problem is.  I see that poolmining is set to false.  How do I get it to true?  Perhaps that is the problem?

Hello @BuckeyeFan and welcome to our forum <3

here is my own conf i only replaced the worker-ID:

Code: [Select]

Can you please post the feedback from getinfo instead of getmininginfo?
The other Question is: Did you open the config-file through the Wallet (Tools -> Open Wallet Configuration File), or do you find the path manuelly?

General Discussion / Re: CCEX
« on: January 08, 2018, 06:50:02 PM »
Is it me or can anyone else not log into their CCEX account?  And if nobody can, how is there price changes on the exchange?  Are these orders that were placed before and are somehow being triggered on their own?  Thanks!

My login works normaly.

Mining / Re: I cannot get into mining pool
« on: January 05, 2018, 12:05:28 PM »
Yes i have registered and i have added my worker and i have my worker id in the config file. I am still getting this error : "poolinfo3": "WORKER ID EMPTY IN POOL CONFIG; WORKER ID EMPTY IN POOL CONFIG;

What exactly is everything i should have in the conf file? Thank you

Hello Cjm_258  :D

Here you can see my own config-file.
Code: [Select]

myworkername is just the name of the worker i has added in the poolinterface. In some pools you have to do this with some synthax like "username.workername", here not. Your username is unimportant. You just need your workername.
The second thing is: sometimes the pool interface is realy slow, so it can takes up to a half hour to update.

General Support / Re: Help with Mining Set Up
« on: January 03, 2018, 03:39:37 AM »
Your English is just fine Sebastian I can assure you it is a lot better than my German would be. The reason I asked about the second worker is because I saw the option of adding a second worker and just wondered if it was possible to use it along side my first worker. But now you mention it I can see the logic that it would be no faster with my one pc  and the second pc would be needed.

You are absolutly right. The thing with the second worker within one config-file is useless i think...

Nice to meet u and: you are welcome <3

General Support / Re: Help with Mining Set Up
« on: January 03, 2018, 03:14:22 AM »
Yes I can see my worker on there, the question I had about a second worker was regarding as to how I add it to the code as in the example below


would it be


or another way ?

Maybe i dont understand the Question (My english is horrible^^), but i think it is not possible to mine with more then one worker in the same wallet.
I think you have a second Computer and trying to setup the mining there.

What is the reason to add a second worker? You cant get faster or something like this...

General Support / Re: Help with Mining Set Up
« on: January 03, 2018, 02:36:33 AM »
Thank you Sebastian for answering, I can feel a lot better now when I leave it mining unattended knowing that I am actually doing something right :)

When you can see your worker in the Landing-Page of pool(2) under "my Leaderboard", everything would be fine!

General Support / Re: Help with Mining Set Up
« on: January 03, 2018, 02:26:00 AM »
Hello @madmurphy,

Iam a Newby too, but i will try to bring some light into the dark:

Hello everyone

I'm new to all this so please be gentle with me :)

I have had a lot of trouble getting started mining, well I think that's what I am doing now. I have two question as below, any help would be greatly appreciated.

1. Do I still need to keep setting the miner for the Test network or can it be left on the Main one ?

I dont know why you mine in the testnet, but all you need is the Setup for the Main-Net.

2. do the lines of code below look correct ?

  "blocks": 23992,
  "currentblocksize": 1375,
  "currentblocktx": 1,
  "difficulty": 720.2589167829533,
  "errors": "",
  "genproclimit": 2,
  "networkhashps": 77138470084.95967,
  "hashps": 1901.576766935003,
  "minerstarttime": "01-03-2018 04:50:33",
  "hashcounter": 823455,
  "competetive_mining": true,
  "competetivemining_hash_counter": 6214095,
  "global_competetive_mining_tithe": 107,
  "competetive_mining_ratio": 7,
  "pooledtx": 1,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL; BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL; BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL; ",
  "poolinfo2": "Submitting Solution 01-03-2018 04:57:24; Submitting Solution 01-03-2018 04:57:32; Submitting Solution 01-03-2018 04:49:26; ",
  "poolinfo3": "",
  "miningpulse": 1106,
  "poolmining": true,
  "pool_url": "",
  "poolmining_use_ssl": false
Bob Marley would be singing: "Everything it's gonna be alright"

Sorry thought of a third question

How do I add a second miner or more, I seem to have missed where that solution is posted/placed.

Thanks for your time in looking at this

Thats realy easy. Go to the Miner-Tab in the Pool-Interface an click on "Add". Thats it. The same like for your first Worker.

Best regards

General Support / Mysterious Pool Outputs...
« on: December 29, 2017, 06:17:28 PM »
Hello Community,

since a couple of hours i got some strange Information. What could that be? A minus (-) before the available Balance?

If you have some Impressions, let me hear!

General Support / Re: Sanctuary disappeared overnight..
« on: December 28, 2017, 05:57:01 AM »
My deamon stopped working also. But I'm not on a Vultr vps, so I think we can delete that from the equation.

Maybe we could use a script that will check the deamon status and restart if necessary. Something like this:

If someone could rewrite that for BBP, that would be awesome :)

This seems to be simple (dont stings me if its wrong, i start to work with linux one month ago^^):

Go to YOUR biblepay-path. For example: /home/root/biblepay/src

Create a file with this code:

Code: [Select]
if ps ax | grep -v grep | grep $SERVICE > /dev/null
  echo "$SERVICE is already running!"
  ./biblepayd -daemon

Now we need to add this as an cronjob:

Code: [Select]
export EDITOR=nano
crontab -e
Go to the end an paste:

Code: [Select]
*/2 * * * * sh /home/root/biblepay/src/ >/dev/null 2>&1
Please Check and correct it to YOUR Path.

General Support / Re: Sanctuary disappeared overnight..
« on: December 28, 2017, 05:19:53 AM »
Woke up this morning to it being expired, and seemingly the daemon shutdown around 11.00pm UTC for some reason..

Both mnsync status and masternode status returned "error: couldn't connect to server"..

Restarted the daemon, and it synced eventually, and appeared enabled again..

I was assuming it was something I've done during setting it up, but it had been running on it's own for 3 days now, so was confident it was working.. But then I noticed a whole bunch of other MNs were in Expired states on the MN list.. Not just me.. Though as of writing this, that seems to have reduced somewhat..

I know there's not a whole bunch of technical info to go on, but just trying to work out if there's something wrong with my setup, or of some event last night, triggered the glut of Expired statuses..

Edit: Think I've got to the bottom of why it happened, seems that it was scheduled maintenance on the vultr network, which resulted in network being down.. Which explains the other Expired nodes I saw, they were probably all on the same server location.. Would that explain the MN service stopping ? Does it shutdown in the absence of network connectivity ?

Hi m00,
i have a VPS on vultr too, but there was no maintenace.
Maybe the reason is block 23000? And your masternote need an upgrade to ?

If not, just ignore my answer, iam just a noob  ;D

HappyBee Host

Thank you for telling <3

Then i can stopp to trying solve this problem. And can start to find a "better" provider  ;D

Same with you , I cancelled it as I tried many times to test,  look like the provider had a detector tool for monitor their vps ....

Which Provider did you mean?

>> got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

is that 1GB or 2GB RAM VPS you've got random daemon failures at ?

Its the 2 GB RAM Quadcore VPS.

Pages: [1] 2