Parity RCP hangs after intensive tx generation #10321
Comments
|
Hey, didn't see your version number in chat - can you please try with the latest stable? Or if not, what's stopping you from doing so? |
jam10o-new
added
the
Z3-stale 🍃
|
@joshua-mir no, I can't, becasuse I tried but I had this problem with private keys, as you probably remember. |
|
#10160 |
|
Looks like it is. But as we discussed, keys are in proper place: diff --git a/docker-compose.yml b/docker-compose.yml
index 510821d..e256111 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -13,11 +13,11 @@ services:
--no-persistent-txqueue
volumes:
- ./parity/config:/parity/config:ro
- - authority0:/root/.local/share/io.parity.ethereum/
- - ./parity/authorities/authority0.json:/root/.local/share/io.parity.ethereum/keys/${NETWORK_NAME}/authority.json:ro
- - ./parity/keys:/root/.local/share/io.parity.ethereum/keys/${NETWORK_NAME}
+ - authority0:/home/parity/.local/share/io.parity.ethereum/
+ - ./parity/authorities/authority0.json:/home/parity/.local/share/io.parity.ethereum/keys/${NETWORK_NAME}/authority.json:ro
+ - ./parity/keys:/home/parity/.local/share/io.parity.ethereum/keys/${NETWORK_NAME}
- ./parity/authorities/authority0.pwd:/parity/authority.pwd:ro
- - ./parity/node0.network.key:/root/.local/share/io.parity.ethereum/network/key:ro
+ - ./parity/node0.network.key:/home/parity/.local/share/io.parity.ethereum/network/key:ro
ports:
- 8545:8545
networks:This was your suggested change, but it didn't work. P.S. running https://github.com/orbita-center/parity-poa-playground/tree/feature/distr (branch |
|
I don't know how we can address the issue (if it isn't already) if you can't update to a version where the fix has been applied though 😥 |
|
I'm not sure why you think it was fixed in last months, since I'm working with parity for almost a year and it never works that way, it's always up to some weird parameters and startup arguments. I'm open to the dialogue, I can fix the issue and try to migrate to newer version if you tell me what to do. I tried my best but it didn't work When I fix paths Looks like #9791 (comment) but I don't see how to solve it I tried But I get |
|
I talked a bit with my crown, they say it matters that permissions I have outside container on my host machine. Sounds weird, but they are quite convincing |
|
At least for the image we provide, the directories and files outside need to have permissions set so that the user within the container can access them. I don't know how that's related to your issue though, especially since that isn't the case as far as I'm aware with your container. |
I'm trying to migrate to latest parity to confirm it works (i.e. it doesn't) the same way on 2.2.8, because as you said "We won't learn this issue until you upgrade".
In my environment I'm running docker on Windows so I don't have any manageable permissions on my host machine. I'l probably try to workaround these changes by forcing Maybe I've spammed a lot and should create another issue when I'm done with upgrade? I just want this problem to be solved, but I don't see how can I do it. |
|
FIxed migration with following PR: https://github.com/orbita-center/parity-poa-playground/pull/19 In a nutshell: I created a new image on top of yours and chown all folders instead of mounting them. I'm going to create a new issue instead of this one because it got spammed a bit. |
For some reason after several hours of intensive block generations parity hangs for no reason.
Friday night I ran my batcher, that just call some contract in batches (50 items in batch).
Here are my logs:
As you can see, it worked fine for almost 10 hours. My setup is 5 sec so it took 10 sec (or two blocks) to insert the entire batch.
Then things get weirder, becasue now it takes almost an hour to insert the same amout of data in blockchain (I used "retry forever" policy with 30 sec awaiting between calls).
When I go to parity logs I see:
Nothing more appears, it just writes it and in 20 sec my client fails with RPC timeout. Then it retries and I get another bunch of logs, then it again writes nothing more, repeat.
I restarted all nodes, I tried to leave single node to prevent desync, I double checked system time. I don't know what can I do.
Here is a code that gets called:
It just does a lookup in the map and then insert one item in array. Nothing complicated that has to take hours to complete.
I provide logs and all info I possess. If I can do anything else I'd be rigorous in providing all required additional information.
The text was updated successfully, but these errors were encountered: