Move monitor to GCP - Githubissues

ethereum / sourcify

Decentralized Solidity contract source code verification service

https://sourcify.dev

MIT License

775 stars 384 forks source link

Move monitor to GCP #1524

Closed marcocastignoli closed 4 weeks ago

marcocastignoli commented 1 month ago

We need to move monitor to the new infra on GCP

marcocastignoli commented 1 month ago

I moved monitor to GCP but there seems to be several problems:

communication issues between between monitor and server (it happens apparently randomly):
```
{"address":"0x4bD4425E2E3AEf4F579bd74FA78831525A0BD110","error":{"cause":{"code":"ECONNRESET","host":"sourcify-staging-server-lidblonrca-ew.a.run.app","path":null,"port":443},"code":"ECONNRESET","config":{"adapter":["xhr","http","fetch"],"data":"..."}
```
- I thought it could be the "min number of instances = 0" settings for Cloud Run Services for which Sourcify server took too long to reply because it had to start a new instance before receiving a request from monitor. But it doesn't seem to be the case
- I'm using axios in monitor instead of fetch because otherwise errors are not logged
- I improved logging in a separate monitor docker image (europe-west1-docker.pkg.dev/sourcify-project/marco-personal/marcocastignolieth/sourcify-monitor@sha256:1255cd8c738c886cb17afa34ea35bd9c6acf013972ac417b482594f2648a085f), the error above is caused by this error: Client network socket disconnected before secure TLS connection was established.
block polling fails too many times leaving monitor behind.

Todo:

[x] Use filebase private gateway instead of a public IPFS gateway

marcocastignoli commented 4 weeks ago

I published both monitor-staging and monitor-production on GCP.

I didn't find a solution for the ECONNRESET error explained above. But I implemented a retry mechanism #1561 that should mitigate the problem.