Issue while sending big amounts >100 AEON #179
Comments
|
Disclaimer: I'm a plebeian who doesn't know anything really 😂. Wait for Stoffu or somebody knowledgeable. Now with that said... can you give some more information? What OS are you running on? Are you using official binaries from here (this github releases page) or did you maybe compile your own aeon binaries? Are you using a remote node, or do you have a fully synchronized copy of the blockchain with aeond on your localhost? Fill in the blanks here, it will help somebody smarter than me answer your question. I just answer the door 😂. But to me... all those boost and epee and net_utils and connection errors; that looks familiar 🤔. Like what happened when I compiled my own binary (default make release; thus a dynamically linked binary) and then I upgraded my Ubuntu to 20.04... lost all the symlinks to the older boost libraries and had to just recompile with the new libraries. If you use the official release binary tarball here, it would rule that out as it's a static build. Oh and if you are using a remote node: stop I read someplace that remote nodes can do this attack thing (something malicious; I really don't remember and don't much care because I never use remote nodes) where the first transaction attempt will fail (and you're safe) but if you immediately try again you basically lose your anonymity to the remote node or something. It is possible that you are using a remote node that is malicious and designed only to do this attack thing when TX amounts are high enough 🤔. IDK... just remember that disclaimer above. Best sync your own node (the blockchain file is only 8.1 GB as of now.) Edit: This line: Tells me you must have compiled it otherwise boost would be statically linked and not be using /usr/lib/x86.../boost stuff... try recompiling maybe it's a similar issue like I had. |
|
Ubuntu 16.04, it is full node, node used for mining at our pool. I have compiled from latest github master of AEON |
|
Can you check if this happens with the v0.13.0.0 release as well? Also, this error does not happen when you transfer smaller amounts? Finally, in general |
|
Actually it's very likely that your RPC request contains some invalid value. Specifically, aren't you specifying a floating point number to some field like the amount? All numbers in the RPC request must be integers. You can paste your RPC request here for examination. |
|
Thanks for the hint on floating point, I will have a look, and see it helps |
|
No, integer give the same error, as workaround I am sending by 32 AEON, which seems to fit some internal variable/array sizes, and never crash, it just annoying to pay users by 32 AEON |
|
Have you tried Also, please provide your JSON wallet RPC request (with addresses etc appropriately masked, as necessary). |
|
And have you tried to reproduce by sending more than 50 AEON and just fix the bug? :) I will try to collect required info meanwhile, but I think it is straight forward use case. |
|
Of course I would have fixed it by now if I could reproduce it. I confirmed that I can transfer any high amounts via wallet RPC without problem. I'm fairly certain that the bug is in your pool software. |
|
By transfer or transfer_split? |
|
I used transfer. |
|
This is how it looks on curl requests wallet - I have hidden actual wallet for transfer 178.11885908 AEON |
Obviously, this |
|
Thanks, indeed has to do with way php converted double to string. I have fixed it now. |
|
Seems was too early on conclusion Does not create txid, but instead produces below exception in aeon debug log |
|
This parameter Try again with correctly formatted payment ID or with no payment ID. |
|
no, I just made it hidden I have correct payment id 0cda49b7eb884ff1a07b9cb77bf4f2afaeb2cd8fd9d04395b18d1d6fee5d90b5 |
|
sending 10 AEON just worked, but more does not, even 32 AEON stopped to work
txiid 95993e56dc4de3adf855d4457739ce9073fa47474d89a6937df3c82749b928b3 |
|
Are you really using the official AEON software? It seems very strange because the daemon RPC FWIW, |
|
/aeon$ git status |
./aeond --version |
|
And yes, I am using get_block for other means, but it does not fail with error. Issue occurs only when sending funds, and again small amounts are send ok, but not more than 10 AEON now |
|
Sorry, but seems impossible to me to solve your issue since no one else seems to be able to reproduce it. |
|
ok, perhaps I can try to recreate wallet, do you have some hints on how to dump priv keys and recreate in new wallet file |
|
Maybe apply this patch to the v0.13.1.0-aeon tag diff --git a/src/rpc/core_rpc_server.cpp b/src/rpc/core_rpc_server.cpp
index 3e5d48193..e375ecfb2 100644
--- a/src/rpc/core_rpc_server.cpp
+++ b/src/rpc/core_rpc_server.cpp
@@ -1487,6 +1487,7 @@ namespace cryptonote
//------------------------------------------------------------------------------------------------------------------------------
bool core_rpc_server::on_get_block(const COMMAND_RPC_GET_BLOCK::request& req, COMMAND_RPC_GET_BLOCK::response& res, epee::json_rpc::error& error_resp){
PERF_TIMER(on_get_block);
+LOG_ERROR("on_get_block: hash:" << req.hash << ", height:" << req.height);
bool r;
if (use_bootstrap_daemon_if_necessary<COMMAND_RPC_GET_BLOCK>(invoke_http_mode::JON_RPC, "getblock", req, res, r))
return r;and see what the daemon reports. |
|
Recreating wallet would be best achieved by restoring from the seed. Use the CLI command But I doubt restoring the wallet would have anything to do with your issue. |
|
I can confirm that sending a considerable amount larger than 32 aeon works fine on my end with RPC on v0.13.1.0 release. |
|
@pinpins |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Ending up with following error
The text was updated successfully, but these errors were encountered: