Comments (15)
note that both payouts are negative, can this be the reason for error?
do i maybe need to run from first cycle i can pay? like 63 i think somewhere along something went wrong with setting all up
from tezos-reward-distributor.
Please your BussinessConfiguration you may shadow addresses.
from tezos-reward-distributor.
This looks like a service fee ratio problem. If you have your service fee %4.5 it should be set to 0.045.
Please adjust your settings.
from tezos-reward-distributor.
Omg i am not behind computer but i know fee is set at 7.00 hence the negative fees
I will set at 0.07 (7%)
Is there a way to restart payment/calculations since previous ones are not correct
from tezos-reward-distributor.
Run the application again. Closing this issue.
--
BussinessConfiguration file has example content. You can make use of it.
https://github.com/habanoz/tezos-reward-distributor/blob/master/src/BusinessConfiguration.py
from tezos-reward-distributor.
ok i also did git pull for latest update, still getting some errors!
the payments are now positive
2019-02-08 12:29:53,975 - main - DEBUG - MainThread - Client command is /home/payment/tezos/tezos-client
2019-02-08 12:29:53,975 - main - INFO - MainThread - initial_cycle set to 68
2019-02-08 12:29:53,975 - main - DEBUG - MainThread - Producer started
2019-02-08 12:29:53,976 - main - INFO - MainThread - If you want to send emails, populate email.ini file under current working directory.
2019-02-08 12:29:53,976 - main - DEBUG - MainThread - Consumer "consumer0" created
2019-02-08 12:29:59,045 - main - DEBUG - producer - Trying payments for cycle 68
2019-02-08 12:29:59,095 - main - DEBUG - producer - Checking for pending payments : payment_cycle <= current_cycle - (self.nw_config['NB_FREEZE_CYCLE'] + 1) - self.release_override
2019-02-08 12:29:59,095 - main - DEBUG - producer - Checking for pending payments : checking 68 <= 74 - (5 + 1) - 0
2019-02-08 12:29:59,095 - main - INFO - producer - Payment cycle is 68
2019-02-08 12:29:59,441 - main - INFO - producer - Total rewards=976.01381
2019-02-08 12:29:59,441 - main - INFO - consumer0 - Starting payments for cycle 68
2019-02-08 12:29:59,445 - main - INFO - producer - Reward created for cycle 68 address xxamount 0.599000 fee 0.045169 tz type D
2019-02-08 12:29:59,446 - main - INFO - producer - Reward created for cycle 68 address xxamount 0.081000 fee 0.006841 tz type D
2019-02-08 12:29:59,446 - main - INFO - producer - Reward creation done for cycle 68
2019-02-08 12:29:59,714 - main - DEBUG - consumer0 - Payment will be done in 1 batches
2019-02-08 12:29:59,714 - main - DEBUG - consumer0 - Payment of a batch started
2019-02-08 12:30:00,194 - main - DEBUG - consumer0 - head: branch xxcounter 12 protocol PsddFKi32cMJ2qPjf43Qv5GDWLDPZb3T3bF6fLKiF5HtvHNU7aP
2019-02-08 12:30:00,194 - main - INFO - consumer0 - Payment content: {"kind":"transaction","source":"xx","destination":"xx","fee":"1274","counter":"13","gas_limit": "10100", "storage_limit": "0","amount":"599000"}
2019-02-08 12:30:00,194 - main - INFO - consumer0 - Payment content: {"kind":"transaction","source":"xx","destination":"xx","fee":"1274","counter":"14","gas_limit": "10100", "storage_limit": "0","amount":"81000"}
2019-02-08 12:30:00,194 - main - DEBUG - consumer0 - Running 2 operations
2019-02-08 12:30:00,423 - main - DEBUG - consumer0 - Forging 2 operations
2019-02-08 12:30:00,888 - main - ERROR - consumer0 - Error at reward payment
Traceback (most recent call last):
File "/home/payment/xx/tezos-reward-distributor/src/pay/payment_consumer.py", line 70, in run
payment_logs = batch_payer.pay(payment_items, self.verbose, dry_run=self.dry_run)
File "/home/payment/xx/tezos-reward-distributor/src/pay/batch_payer.py", line 79, in pay
payments_log = self.pay_single_batch_wrap(payment_items_chunk, verbose=verbose, dry_run=dry_run)
File "/home/payment/xx/tezos-reward-distributor/src/pay/batch_payer.py", line 94, in pay_single_batch_wrap
return_code, operation_hash = self.pay_single_batch(payment_items, verbose, dry_run=dry_run)
File "/home/payment/xx/tezos-reward-distributor/src/pay/batch_payer.py", line 176, in pay_single_batch
signed_bytes = sign(self.client_path, bytes, self.key_name)
File "/home/payment/xx/tezos-reward-distributor/src/util/client_utils.py", line 158, in sign
raise Exception("Signature not found in response ''".format(response))
Exception: Signature not found in response ''
from tezos-reward-distributor.
Please make sure private key for the payment address is imported. If the client does not know the private key, it cannot sign the transactions.
from tezos-reward-distributor.
Hello Sir,
i am allready doing that
as you can see al is imported (unencrypted)
i even reinstalled my whole node (did quicksync) now still get similar errors
atleast i got the negative values out of the way now
as you can see it says total rewards is 976.01381
yet i makes less payout because i didnt set founder and deposit map this shouldnt be the issue right?
ps i installed on dropbox so data can be shared for maybe the dashboard i am going to build
adding to founder and deposit map didnt help, should be some how some silly setting
when doing to script nothing is being send to the node, when i do manual transaction between know address and known contract all goes good
from tezos-reward-distributor.
I made a small change. Please update and run the same command. Then share the log, please.
Error response coming from the client will be printed like below:
Signature not found in response 'client response here'
from tezos-reward-distributor.
did git pull now:
Traceback (most recent call last):
File "/home/payment/Dropbox/tezos-reward-distributor/src/pay/payment_consumer.py", line 70, in run
payment_logs = batch_payer.pay(payment_items, self.verbose, dry_run=self.dry_run)
File "/home/payment/Dropbox/tezos-reward-distributor/src/pay/batch_payer.py", line 79, in pay
payments_log = self.pay_single_batch_wrap(payment_items_chunk, verbose=verbose, dry_run=dry_run)
File "/home/payment/Dropbox/tezos-reward-distributor/src/pay/batch_payer.py", line 94, in pay_single_batch_wrap
return_code, operation_hash = self.pay_single_batch(payment_items, verbose, dry_run=dry_run)
File "/home/payment/Dropbox/tezos-reward-distributor/src/pay/batch_payer.py", line 176, in pay_single_batch
signed_bytes = sign(self.client_path, bytes, self.key_name)
File "/home/payment/Dropbox/tezos-reward-distributor/src/util/client_utils.py", line 158, in sign
raise Exception("Signature not found in response '{}'".format(response))
Exception: Signature not found in response ''
from tezos-reward-distributor.
Nothing useful here. The response seems to be empty. You will need to run sign command yourself and share the results.
I made another update, please pull it and run with -V command. There you will see the sign command. If you cannot see, you may share the log.
Run that command and see the client response. It will probably reveal what is wrong.
from tezos-reward-distributor.
done lets hope this is usefull
from tezos-reward-distributor.
Please have a look, it may help:
https://www.reddit.com/r/tezos/comments/aa5lr3/cant_deploy_a_contract_please_help/
Are you using tz or kt address?
from tezos-reward-distributor.
hmm this is strange, the tz1 works and the kt1 doenst
both have alias, as suggested i imported the unencrypted private key of the tz1
then did your suggested
tezos-client remember contract new src
why wouldnt kt1 not work? its originated from the tz1
i have to say i have set the kt1 to use my baker as delegator surely this cant be the problem
is someone actually using kt1 address as payout?
Worst case scenario accept that payout needs to be done in tz1
from tezos-reward-distributor.
My guess is when paying with kt address it is required to sign with manager account.
Please open an issue for kt payment support.
Meanwhile please use tz address for payments.
If everything is ok, you may close this issue.
from tezos-reward-distributor.
Related Issues (20)
- Update docs to use octez-*
- Dry run command not reading correctly
- Batch payer class is unmanageable.
- exit status is always 0 even when TRD fails (in single-shot mode)
- Don't require signer to know about baker address
- Problem with using the new addresses as owner and founder. HOT 10
- Smoke tests are stuck in an infinite loop on the CI only HOT 1
- payouts in failed/backtracked transactions are marked as paid
- Signer auth HOT 2
- re-running failed operations with TzKT backend is so slow, it hangs HOT 2
- use `simulate_operation` instead of `run_operation` HOT 1
- TRD exiting with status code 1, even when it succeeds HOT 2
- Payment to KT always fails on first try, it goes through in a second attempt. HOT 1
- TzStats "offline_losses" is not working HOT 4
- -M 4 seems to be broken, wrong status for backtracked transactions and ctez vaults are no longer avoided
- payment error. Cycle 669 HOT 4
- Error when using on new v19.0 node version HOT 4
- When running with switch -P tzkt no validation of payments is done
- Error: Failed to get network configuration constants from a local node (http://127.0.0.1:8732)
- Warn instead of exit when new protocol live date is exceeded HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tezos-reward-distributor.