Comments (8)
public key aliases starting with prefix "tz" confused the application. Length check is added to avoid the situation. if a key starts with tz or KT and has a length of 36 then it is regarded as a PKH, else a key alias.
from tezos-reward-distributor.
So we should always use the alias? I started with a tz PKH, and got
2018-12-06 21:11:44,064 - main - DEBUG - producer - Trying payments for cycle 47
2018-12-06 21:11:44,691 - main - DEBUG - producer - checking payment_cycle <= current_cycle - (self.nw_config['NB_FREEZE_CYCLE'] + 1) - self.release_override
2018-12-06 21:11:44,692 - main - DEBUG - producer - checking 47 <= 53 - (5 + 1) - 0
2018-12-06 21:11:44,692 - main - INFO - producer - Payment cycle is 47
--- Logging error ---
Traceback (most recent call last):
File "src/main.py", line 103, in run
reward_data = reward_api.get_rewards_for_cycle_map(payment_cycle)
File "/home/tezos/scripts/tezos-tools/tezos-reward-distributor/src/tzscan/tzscan_reward_api.py", line 43, in get_rewards_for_cycle_map
nb_delegators = self.get_nb_delegators(cycle)[0]
File "/home/tezos/scripts/tezos-tools/tezos-reward-distributor/src/tzscan/tzscan_reward_api.py", line 37, in get_nb_delegators
raise Exception('GET /tasks/ {}'.format(resp.status_code))
Exception: GET /tasks/ 504
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/logging/__init__.py", line 994, in emit
msg = self.format(record)
File "/usr/lib/python3.6/logging/__init__.py", line 840, in format
return fmt.format(record)
File "/usr/lib/python3.6/logging/__init__.py", line 577, in format
record.message = record.getMessage()
File "/usr/lib/python3.6/logging/__init__.py", line 338, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/usr/lib/python3.6/threading.py", line 884, in _bootstrap
self._bootstrap_inner()
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "src/main.py", line 136, in run
logger.error("Error at reward calculation", e)
Message: 'Error at reward calculation'
Arguments: (Exception('GET /tasks/ 504',),)
--- Logging error ---
Traceback (most recent call last):
File "src/main.py", line 103, in run
reward_data = reward_api.get_rewards_for_cycle_map(payment_cycle)
File "/home/tezos/scripts/tezos-tools/tezos-reward-distributor/src/tzscan/tzscan_reward_api.py", line 43, in get_rewards_for_cycle_map
nb_delegators = self.get_nb_delegators(cycle)[0]
File "/home/tezos/scripts/tezos-tools/tezos-reward-distributor/src/tzscan/tzscan_reward_api.py", line 37, in get_nb_delegators
raise Exception('GET /tasks/ {}'.format(resp.status_code))
Exception: GET /tasks/ 504
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/logging/__init__.py", line 994, in emit
msg = self.format(record)
File "/usr/lib/python3.6/logging/__init__.py", line 840, in format
return fmt.format(record)
File "/usr/lib/python3.6/logging/__init__.py", line 577, in format
record.message = record.getMessage()
File "/usr/lib/python3.6/logging/__init__.py", line 338, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/usr/lib/python3.6/threading.py", line 884, in _bootstrap
self._bootstrap_inner()
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "src/main.py", line 136, in run
logger.error("Error at reward calculation", e)
Message: 'Error at reward calculation'
Arguments: (Exception('GET /tasks/ 504',),)
2018-12-06 21:12:49,999 - main - DEBUG - producer - Trying payments for cycle 47
2018-12-06 21:12:50,623 - main - DEBUG - producer - checking payment_cycle <= current_cycle - (self.nw_config['NB_FREEZE_CYCLE'] + 1) - self.release_override
2018-12-06 21:12:50,623 - main - DEBUG - producer - checking 47 <= 53 - (5 + 1) - 0
2018-12-06 21:12:50,624 - main - INFO - producer - Payment cycle is 47
from tezos-reward-distributor.
You got HTTP/504 (Gateway Timeout) from tzscan. You may try again. Also please update to the latest code, if you did not already.
If your problem persists, you may open another issue.
from tezos-reward-distributor.
I had today on two different nodes the same thing.
everything was decided by restarting distributor!
from tezos-reward-distributor.
Did you get 504 two times on different nodes? And does it persist even after you restart ?
from tezos-reward-distributor.
after restart i paid. after the restart, I paid for 1 cycle (47) and then I launched by default now # python3 src/main.py payNode2. I worked in this mode, but I got 504.
on another node I was paying with a duplicate program. There was also an error 504. At first there was a wrong billing address, I corrected it, but I received the same error.
then I deleted all the .csv files and made the correct billing address. I got it seems the same error (not sure now exactly)., I closed the application and paid for 1 cycle (47) everything worked out.
Now Iām running everywhere by default # python3 src / main.py - wait for the end of the cycle and see.
from tezos-reward-distributor.
tzscan mirror 4 is down. I modified application not to use mirror 4. Please update and share your results
from tezos-reward-distributor.
Closing the issue.
from tezos-reward-distributor.
Related Issues (20)
- Payment for cycle 527 was off, overpaid delegates HOT 4
- Cleanup: min_payment_amt HOT 5
- Pre-commit hooks
- Configure script requires refactor
- 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
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.