A couple of issues while running a Testnet node. I was following this guide.
The Chain Configuration section links to an example config for beta-5 but in the Discord, I noticed that beta-5 is not live yet. So unsure if this section needs to be updated.
I ran the node anyway, with the beta-5 example configuration, and it still seemed to work. However, http://84.247.141.79:4000/graphql doesn’t seem to load for me even though I noticed the following logs:
2024-02-11T07:45:35.136469Z INFO new{name=}: fuel_core::graphql_api::service: 216: Binding GraphQL provider to 0.0.0.0:4000
2024-02-11T07:45:35.136739Z INFO new{name=}:initialize_loop{service="FuelService"}: fuel_core_services::service: 330: Starting FuelService service
2024-02-11T07:45:35.136823Z INFO new{name=}:initialize_loop{service="GraphQL"}: fuel_core_services::service: 330: Starting GraphQL service
In addition, the logs being downloaded are painfully slow and I don’t think this is intentional. My machine has more than enough resources available for downloading to not be an issue, so quite unsure how to go about resolving this/understanding what’s the “normal” speed.
er::service::get_logs: 33: Downloading logs for block range: 5264197..=5264224
d2024-02-11T07:55:15.560356Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5264225..=5264256
gra2024-02-11T08:01:40.628791Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5264257..=5264285
2024-02-11T08:08:05.738313Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5264286..=5264317
2024-02-11T08:14:25.852734Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5264318..=5264349
@Lucplo, our client team is currently investigating this matter. It appears to be a DNS issue on our end. Rest assured, I will keep you updated with any progress and let you know as soon as we have a solution in place.
2024-02-26T05:55:07.461947Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5363498..=5365112
2024-02-26T06:00:02.964929Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5365113..=5365141
check my latest run’s logs - this is a bottleneck in the running of the node. are there nodes running successfully? If so, what are they doing differently? Aren’t most nodes on just VPSs available for rent? Note I’m using a Contabo box
Still the same, logs taking long to download, once every 5 mins. Was asked to take a look at https://app.fuel.network/ for the latest block #. At the time of writing, we’re at 6089957, so the sync will basically never finish haha…
2024-03-03T06:45:12.064829Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5406209..=5406240
2024-03-03T06:51:17.585347Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5406241..=5406267
2024-03-03T06:57:37.666629Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5406268..=5406298
2024-03-03T07:04:02.808739Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5406299..=5406330
2024-03-03T07:10:27.870981Z INFO new{name=}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5406331..=5406361
