-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to get output distribution #3581
Comments
I have the same error after hard fork. Completely impossible to send any transaction. Please help. |
Try #3584 |
Thank you, I accepted the pull request locally and after recompilation, the transfers are working. |
I have the same error too. ("failed to get output distribution") |
It is a good solution. We have no offices. I don't understand the third question. It is not committed to master yet. |
I'm also getting this today, on my 1st block. Do we have an official solution? Or and ETA on release? |
Did you try 3584, and did it work ? |
Not really good with these merges and pulls, still learning. Do I have to manually make the change to the file on my server, or just do a fresh download? EDIT: Can see, it's not in the latest master, have downloaded it, edited, compiling. |
Can confirm this change fixes my issue too. |
Great, thanks for testing. |
How can I get the build this is in? I can't send anything from my wallet. I have the release build v12 on Ubuntu 16.04. I am not sure how to use git to just pull in this PR |
@shnetinka I just did this. In the @moneromooo-monero I had this problem (with |
This may or may not be related, but I wanted to mention it in case this change caused the issue I had. Full details in: Snipa22/nodejs-pool#397 1st block paid out fine, after I made this manual change (adding * 1000) to the timeout. I did increase limits in Ubuntu and MySQL which could have resolved it, but I saw everything working once I updated to the latest Daemon, which does not have this manual fix in (which I initially tested working). Please let me know your thoughts. |
@scoobybejesus thanks. That worked. I thought that was how to do it but I think I had a master in the path somewhere which was obviously wrong. @moneromooo-monero - updated yesterday and the wallet appears to be working well. Thanks! |
+resolved |
After upgrading my monero tools to reflect PoW change, I'm getting the following errors anytime I try to make a transfer through monero-wallet-rpc.
and in the wallet I can see this:
I tried to renew blockchain (deleting ~/.bitmonero and importing it from scratch) and the same error remains.
The text was updated successfully, but these errors were encountered: