Closed chiptus closed 5 years ago
Which command did you run - have you checked that tezos-client
can sign & send transactions?
yes, just did a tezos-client transfer
and it worked.
backerei shows Running "tezos-client ... sign bytes ... for bakepay" in a pty
, but stays there forever
Try running the command manually and see if tezos-client
signs the transaction successfully.
i tried and it did sign it successfully, no errors from tezos-client
it signs successfully, but when I try to decode it on https://kukai.app/offline-signing it didn't work. I guess there's something wrong with the bytes it tries to sign. where can we chat so I can send you the exact output without exposing it to public? are you on obisidian's bakers slack?
i think i have the same running no-dry run gives me
xx@payment:~/tezos$ backerei payout --no-dry-run Enter source account password: Total payouts: 0.191056, payout account balance: xx For cycle 64 delegator xx should be paid 0.191056 XTZ Running '/home/xx/tezos/tezos-client -c /home/xx/.tezos-client/config sign bytes 0x031e3cf235638312719aff8222a1835e3629656642896b3f213a4ac0f168c2247e080000571bd249326124a9b101eb101b39515e8b356fdb009f8f35f85500d0d40b01fe0be860211931133e81111a25ed21a82a9d09c90000 for xx' in a pty
here it stays forever what to do?
UPDATE: running it manual signs the transaction Also fee in yaml file is set like fee:
do i need to place like a 0?
@chiptus Did you test running the sign
command manually? backerei
just produces whatever signature output tezos-client
would produce. You shouldn't need to show me the exact output.
@issie81 I answered here - https://github.com/cryptiumlabs/backerei/issues/27#issuecomment-457960275.
chiptus are you running vanity address? is there a pass set.. i did have same did (had account without pass, vanity) made a new address (normal) and with pass after that all went good
running the sign
command manually produces a string successfully. But trying to decode it using something like https://kukai.app/offline-signing failed.
Hmm, the Tezos client & that webapp might pad the signed string differently.
I'm pretty sure the signature produced by backerei
is correct for the purpose of signing transactions. Signature format is probably not related to backerei
hanging - is that still happening? The terminal code used to call tezos-client
might be a bit finicky - are you running on Linux in a standard terminal?
osx, terminal
Possibly the code which backerei
uses to interact with tezos-client
through a virtual pty isn't OSX compatible.
Can you possibly try on Linux?
Otherwise you could play around with the sign
function at the bottom of app/Payout.hs
.
Thanks for the answer, I will have a look at both.
Any luck?
Closing, but reopen if you still need help debugging.
I'm seeing the same thing. Sometime last week, backerei just stopped doing the automatic transactions, and when trying to restart it, I see that it's stuck on
Running '/home/tezos/tezos/tezos-client -c /home/tezos/.tezos-client/config sign bytes ** for **' in a pty
When running the command manually it runs, and says "Signature: ***" but the transactions are never completed.
Any ideas? :)
Update: Running on Linux
Are you using a remote signer, or did you change your configuration at all prior to the issue?
Nothing changed before this stopped, and I don't think I'm using a remote signer. Everything is running on the node :)
I've tried updating the entire node now, inlcuding backerei, and it still get's stuck on running xxx sign bytes..
Hmm, strange, unfortunately I don't really know where to start to help you.
Are you familiar with Haskell? Try modifying the code at the bottom of app/Payout.hs
which handles signing (the sign
function).
After fixing the yaml and revealing our public key, now the client hangs forever without sending any rewards.