-
Notifications
You must be signed in to change notification settings - Fork 54
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
"Max processing time reached" error #118
Comments
I cannot access to https://parity.poa from my system by using
|
Thanks for quick response. The link is https://nile.dev-ocean.com (sorry for not including the real link) Below is the tx info:
|
@gongf05 Which linux distro do you use? |
Hi I use MacOS 10.14.2 |
I had this issue as well and tried to change the MAX_PROCESSING_TIME var without success. As far as i can tell this is caused by the fact that the calls to the node url don`t get a response and the containers hangs waiting until MAX_PROCESSING_TIME is reached and the get shut down. In my case, I was trying to hit a local ganache node and i had the node url set like |
I have the same issue. I tried increasing the
FYI, I use the npm processes because the Docker container wasn't able to connect to RabbitMQ. Using npm, I got it to connect to Redis and RabbitMQ and most of the transfer worked, except for the last part implicating the Here is my .env file (with keys and ID removed):
Do you think it's related to the Here are my System Specs: Thanks |
@jrainville I see two issues here:
First of all could you specify exact branch/commit of the token bridge repo you cloned? Next, for the first issue could you provide the And could you also provide entire log for the issue with the Redis DB: starting from the oracle run till the moment when the issue happens. Thanks, |
Branch/commit: Master 7863197
This is what I have in the UI, it gets stuck at this step. Hopefully the logs are clear enough. Let me know if you need anything more. |
@jrainville hi! In your docker logs I see that RabitMQ container was not started at all. Could it be a windows specific issue since we use the docker volumes to keep the MQ data on disk in case of the container restart: From your logs that are got after start by NPM I see that you enabled 'INFO' logs verbosity could you extend it to |
Hi @akolotov , I reran I didn't re-attempt a transfer of tokens, as the last one seemed still in the "queue" ( As for using Let me know what command to enter and I'll quickly give you the output. |
Examples of the command parameters could be found here: https://github.com/poanetwork/token-bridge/tree/master#redis. |
Sorry, I just noticed I didn't paste my gist last time. Here it is: https://gist.github.com/jrainville/81b062670ceac9388146b83d33554ceb I tried the redis-cli command, but it keeps returning
So either I'm doing something wrong, or Redis doesn't store anything. |
@akolotov any luck with this? |
Thanks for detailed logs First of all I see that the Redis could be updated with new block values in the watchers whereas the code cannot lock a resource from the sender. That's very strange. Could you stop redis, find redisbd files on the disk, remove them and start redis? Is it possible for you try to run the bridge oracle on a Linux machine? I am worrying if it could windows specific. |
You can run command From the error log, it seems that key |
I had one of my colleagues test with a Linux machine and even though he ran in the same issue as me using Docker, once using the yarn/npm commands, he manages to make it work. Transfers from and to the child network worked for him. He used the same exact env files as I so the only conclusion is that there is an issue running the bridge-oracle in Windows. Thanks for taking the time to try to debug this with me. |
I had tried to test token bridge between Ropsten and Parity POA network. I had managed to deloy the contracts to both networks. The .env file for token bridge part is
I tried to run
docker-compose run bridge npm run watcher:signature-request
and found error as:Is there anyone find a similar issue and any suggestion would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: