Mainnet participant node syncing problem - Algorand
Mainnet participant node syncing problem
post by Cryptocurv on Dec 10, 2021
My node seems to have stopped syncing. Its sync time keeps increasing. Can someone help me? I captured the following outputs.
[/var/lib/algorand] $ goal version -v
Version: [v1 v2]
GenesisID: mainnet-v1.0
Build: 3.2.1.stable [rel/stable] (commit #b6cbbf34)
[/var/lib/algorand] $ goal node status
Last committed block: 17947900
Time since last block: 4.7s
Sync Time: 1805.9s
Last consensus protocol: https://github.com/algorandfoundation/specs/tree/bc36005dbd776e6d1eaf0c560619bb183215645c
Next consensus protocol: https://github.com/algorandfoundation/specs/tree/bc36005dbd776e6d1eaf0c560619bb183215645c
Round for next consensus protocol: 17947901
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: mainnet-v1.0
Genesis hash: wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=
[/var/lib/algorand] $ tail -f node.log | grep DNS
{"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":"2021-12-10T15:20:27.501305-08:00"}
{"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 _archive._tcp.mainnet.algorand.network","time":"2021-12-10T15:20:27.586418-08:00"}
[/var/lib/algorand] $ dig _algobootstrap._tcp.mainnet.algorand.network srv +dnssec
;; Truncated, retrying in TCP mode.
; <<>> DiG 9.16.1-Ubuntu <<>> _algobootstrap._tcp.mainnet.algorand.network srv +dnssec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43834
;; flags: qr rd ra; QUERY: 1, ANSWER: 109, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 65494
; OPT=5: 05 07 08 0a 0d 0e 0f (".......")
; OPT=6: 01 02 04 ("...")
; OPT=7: 01 (".")
;; QUESTION SECTION:
;_algobootstrap._tcp.mainnet.algorand.network. IN SRV
;; ANSWER SECTION:
_algobootstrap._tcp.mainnet.algorand.network. 299 IN SRV 1 1 4160 r-ba.algorand-mainnet.network.
_algobootstrap._tcp.mainnet.algorand.network. 299 IN SRV 1 1 4160 r-pm.algorand-mainnet.network.
_algobootstrap._tcp.mainnet.algorand.network. 299 IN SRV 1 1 4160 r-er.algorand-mainnet.network.
_algobootstrap._tcp.mainnet.algorand.network. 299 IN SRV 1 1 4160 r-te.algorand-mainnet.network.
... (truncated for brevity)
post by fabrice on Dec 13, 2021
First and foremost, is the “last committed block” increasing?
If yes, everything is working properly.
If it increases too slow so that it’s not catching up, the issue is most likely:
- not enough RAM. Do you have at least 8GB?
- disk too slow: you need an SSD, HDD are too slow
Can you check that:
- RAM use
- CPU use
- disk use (
df -h)
EDIT: This looks like a duplicate of Node sync time keeps increasing - ver 3.2.1
post by Cryptocurv on Dec 13, 2021
Hi Fabrice,
Yes, it is a duplicate… This was an original post but was flagged and hidden as a potential spam. I think the post was unflagged today by the staff.
Thanks,
post by fabrice on Dec 13, 2021
No problem, let me mark this as a duplicate officially.