0

The question is the same as here Run the safe-global/safe-infrastructure service for a sample test.

It was done all steps, but the answer did not help to resolve the problem. So we still get the error during indexing/creating the wallet process:enter image description here CGW logs returned error Code 600: Error fetching Safe info (42: ) Logs:

[2023-09-04T08:04:53Z INFO  _] Response succeeded.
[2023-09-04T08:05:00Z INFO  rocket::server] GET /v1/chains/1230/safes/0xD29e6bAF19795291724B1766fbd1F04dcb76b5bB:
[2023-09-04T08:05:00Z INFO  _] Matched: (get_safe_info) GET /v1/chains/<chain_id>/safes/<safe_address>
[2023-09-04T08:05:00Z ERROR safe_client_gateway::utils::errors] ERR::404::/v1/chains/1230/safes/0xD29e6bAF19795291724B1766fbd1F04dcb76b5bB::ApiErrorMessage: code:42; message:Some(""); arguments:None
[2023-09-04T08:05:00Z INFO  _] Outcome: Success
[2023-09-04T08:05:00Z INFO  safe_client_gateway::monitoring::performance] MT::GET::/v1/chains/<chain_id>/safes/<safe_address>::1::404::/v1/chains/1230/safes/0xD29e6bAF19795291724B1766fbd1F04dcb76b5bB::1230::167.233.10.221
[2023-09-04T08:05:00Z INFO  _] Response succeeded.

Master copy was added manually in admin: Master copy was added manually in admin

Also, SafeProxyFactory was added manually in admin: SafeProxyFactory was added manually in admin

What are we missing? Could anyone help to understand the issue 42 without the message? enter image description here Thank you!

Improve this question
6
  • Does it never resolve? I believe in the creation flow the UI polls the CGW until the account is available.
    – mikheevm
    Sep 5 at 11:57
  • @mikheevm I'm, sorry, what do you mean?
    – Yevheniia
    Sep 5 at 13:09
  • When you create a safe in the UI, it takes some time for the backend to index it, so it's totally expected to see a few 404s until it gets indexed
    – mikheevm
    Sep 5 at 15:30
  • @mikheevm I got it, it does never resolve. We were waiting for 24 hours and even 1+ week. What are the issues here might be?
    – Yevheniia
    Sep 5 at 15:54
  • We found the reason of the errors. Thank you for your help! ethereum.stackexchange.com/a/154160/124073
    – Yevheniia
    Sep 5 at 18:45

2 Answers 2

Reset to default
1
  1. The first problem was the wrong RPC_NODE_URL (where the wrong address was specified).
  2. Then the following problem: 2 records were created for the history chain for the transaction service - but there must be 1 Tx Service per Chain, with different workers, PostgreSQL, Redis and RabbitMQ.. https://github.com/safe-global/safe-infrastructure/tree/main
  3. So, we deleted the entry from the database and the errors in logs disappeared, after that, all workers that were shut down started to work without errors.
Improve this answer
0

Will add more information

Here is log from CGW service

[2023-09-05T10:36:54Z ERROR safe_client_gateway::utils::errors] ERR::404::/v1/chains/1230/safes/0xD29e6bAF19795291724B1766fbd1F04dcb76b5bB::ApiErrorMessage: code:1337; message:Some(""); arguments:None
[2023-09-05T10:36:54Z INFO  _] Outcome: Success
[2023-09-05T10:36:54Z INFO  safe_client_gateway::monitoring::performance] MT::GET::/v1/chains/<chain_id>/safes/<safe_address>::46::404::/v1/chains/1230/safes/0xD29e6bAF19795291724B1766fbd1F04dcb76b5bB::1230::167.233.10.221
[2023-09-05T10:36:54Z INFO  _] Response succeeded.

Maybe it can help

Improve this answer
1
  • Yes, there are two errors, 42 and 1337. 1337 Appears once at first time when requesting the GET /cgw/v1/chains/1230/safes/0x04202a.. , but 42 errors appears all the time after for the same endpoint
    – Yevheniia
    Sep 5 at 13:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.