Algorand Node using official docker image is not synching

Post by Sowna on Jun 27, 2023

Hi @fabrice,

I have referred Introducing Official Algod Docker Containers | Algorand Developer Portal

docker-compose file

version: ‘3’
services:
  mainnet-container:
    image: algorand/algod:latest
    container_name: mainnet-container
    ports:
      - 8080:8080
      - 7833:7833
    environment:
      - NETWORK=mainnet
      - TOKEN=test
    volumes:
      - /NewDisk71Machine/node-algorand/data:/algod/data/

Node logs:

{"file":"httpTxSync.go","function":"github.com/algorand/go-algorand/rpcs.(\*HTTPTxSync).Sync","level":"warning","line":132,"msg":"txSync POST http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/txsync: context deadline exceeded","time":"2023-06-27T09:30:27.220638Z"}
{"file":"txSyncer.go","function":"github.com/algorand/go-algorand/rpcs.(\*TxSyncer).Start.func1","level":"warning","line":91,"msg":"problem syncing transactions TxSyncer.Sync: peer 'r-ra.algorand-mainnet.network:4160' error 'Post "http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/txsync": context deadline exceeded'","time":"2023-06-27T09:30:27.220702Z"}
{"file":"wsNetwork.go","function":"github.com/algorand/go-algorand/network.(\*WebsocketNetwork).tryConnect","level":"warning","line":2239,"msg":"ws connect(ws://r-b8.algorand-mainnet.network:4160/v1/mainnet-v1.0/gossip) fail: dial tcp 74.118.143.38:4160: i/o timeout","time":"2023-06-27T09:30:34.991710Z"}
{"file":"wsNetwork.go","function":"github.com/algorand/go-algorand/network.(\*WebsocketNetwork).tryConnect","level":"warning","line":2239,"msg":"ws connect(ws://r-pm.algorand-mainnet.network:4160/v1/mainnet-v1.0/gossip) fail: dial tcp 112.80.39.155:4160: i/o timeout","time":"2023-06-27T09:30:34.991739Z"}
{"file":"wsNetwork.go","function":"github.com/algorand/go-algorand/network.(\*WebsocketNetwork).tryConnect","level":"warning","line":2239,"msg":"ws connect(ws://r-f1.algorand-mainnet.network:4160/v1/mainnet-v1.0/gossip) fail: dial tcp 169.150.224.230:4160: i/o timeout","time":"2023-06-27T09:30:34.991711Z"}
{"file":"wsNetwork.go","function":"github.com/algorand/go-algorand/network.(\*WebsocketNetwork).tryConnect","level":"warning","line":2239,"msg":"ws connect(ws://r-tm.algorand-mainnet.network:4160/v1/mainnet-v1.0/gossip) fail: dial tcp 149.28.36.5:4160: i/o timeout","time":"2023-06-27T09:30:34.991718Z"}
{"file":"bootstrap.go","function":"github.com/algorand/go-algorand/tools/network.ReadFromSRV","level":"info","line":43,"msg":"ReadFromBootstrap: DNS LookupSRV failed when using system resolver: no signature in DNS response for _algobootstrap._tcp.mainnet.algorand.network","time":"2023-06-27T09:30:57.781047Z"}

Config.json

{
  "Archival": true,
  "BaseLoggerDebugLevel": 1,
  "EndpointAddress": "0.0.0.0:8080",
  "CatchupParallelBlocks": 50,
  "DNSSecurityFlags": 0
}

output:

{
  "catchpoint": "",
  "catchpoint-acquired-blocks": 0,
  "catchpoint-processed-accounts": 0,
  "catchpoint-processed-kvs": 0,
  "catchpoint-total-accounts": 0,
  "catchpoint-total-blocks": 0,
  "catchpoint-total-kvs": 0,
  "catchpoint-verified-accounts": 0,
  "catchpoint-verified-kvs": 0,
  "catchup-time": 1793501447617,
  "last-catchpoint": "",
  "last-round": 0,
  "last-version": "https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0",
  "next-version": "https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0",
  "next-version-round": 1,
  "next-version-supported": true,
  "stopped-at-unsupported-round": false,
  "time-since-last-round": 0
}

Please help me with this.

Post by scholtz on Jun 27, 2023

this is how I run the node: AlgorandNodes/kubernetes/algod-relay/mainnet-relay/de-1-mainnet-relay/g1-deployment.yaml at main · scholtz/AlgorandNodes · GitHub

i build my own docker image so that it does not run in root environment : AlgorandNodes/docker/algod-relay/mainnet/compose-relaynode-official-3.16.3-stable.sh at main · scholtz/AlgorandNodes · GitHub

Post by fabrice on Jun 27, 2023

I’ve not seen these errors before.

My wild guess is that you have an Internet connectivity issue.

Are you behind a firewall or anything restricting your connectivity?

Are you running the node in a datacenter or at home / in a university where the ISP may be blocking some queries?

Are you running the node in a country that restricts Internet connections in any way?

Can you show the output of:

curl -s http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/block/0 | base64

## Post by Sowna on Jun 29, 2023

Hi [@fabrice](https://forum.algorand.co/u/fabrice), by running curl -s [http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/block/0](http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/block/0) | base64 not getting any output

## Post by Sowna on Jun 30, 2023

Hi [@fabrice](https://forum.algorand.co/u/fabrice), any help on this?

## Post by fabrice on Jun 30, 2023

So you most likely have a connectivity issue.

Are you behind a firewall, a proxy, or anything restricting your connectivity?

Are you running the node in a datacenter or at home / in a university where the ISP may be blocking some queries?

Are you running the node in a country that restricts Internet connections in any way?

Try with `-v` instead of `-s`:

```bash
curl -v http://r-ra.algorand-mainnet.network:4160/v1/mainnet-v1.0/block/0 | base64

Post by scholtz on Jun 30, 2023

for the record I get this output for the request