Bastien

Hello ! Any news on that issue ? My near node that is still in v1.37 is stuck and the one I updated to v1.38 is very slow and can’t...

Actually by looking at the graphql code I can see that it tries to call the metadata server. Which takes A huge time to answer :  ``` time curl https://tokens.cardano.org/metadata/healthcheck...

Ok so it looks like there is no timeout at least configured on graphql so this is coming from the server or something in between... weird that I don’t have...

ok so it seems that it’s due to cloudflare. From the other region (zurich) querying the above endpoint is fast (2 sec). But from geneva it’s not.. Is there any...

Hello ! Just wanted to mention that we are experiencing the same issues with our 2 polygon bor nodes. I have setup a liveness probe (k8s) to restart the node...

I addition this is the parameters I use for starting my optimism node : ``` /usr/bin/geth \ --http \ --http.port=8545 \ --http.addr=0.0.0.0 \ --authrpc.addr=0.0.0.0 \ --authrpc.jwtsecret=/secrets/jwt.hex \ --authrpc.vhosts="*" \ --http.vhosts="*"...

Same for us node stuck at exactly the same height. I migrated the bor node from v1.2.3 to v1.2.8 this morning hoping to fix the issue. But it doesn’t change...

So indeed our node recovered after 30 minutes. It wasn’t at first because I had a probe that was killing my container if it stayed stuck for more than 15...

Ok looking at the code it seems like despite what is mentioned in the node documentation, gcmode=archive is mandatory to sync index the state of the blocks. `EnableStateIndexing: cfg.ArchiveMode,` I...

@553589912 I got the same issue on my arbitrum nitro node. I also enabled the `--subscribe-all-data-subnets` flag on my prysme node. My guess is that it needs to backfill some...