Everything seems to be stable till now. No unsynced node yet.

@Allen said in Fullnode not able to sync with NTP server - Google VPS:

It has nothing to do with the ntp service but just somehow google's vps got unstable connection to our wss server. I can give you a hotfix file in case you would like to see the result before the formal release.

Yes please! I'd like to try it out on one node!

Thank you!

@Allen said in Fullnode not able to sync with NTP server - Google VPS:

We have located the uptime problem for google vps. Expect a fix in the next gvite release soon!

So there was something specific for Google? I saw the ntp message on digital ocean droplet as well (second post). That node did not unsync though...

There aren't any other major processes running on the system. Its a VPS specifically for Vite. On one of the other nodes which hasn't gone down yet (but is syncing very slowly), gvite is using 90% of the available RAM.

I'll try to monitor for any other spikes though.

Similar messages are coming on a different VPS as well. Checked just now:

-> vite.ledger_getSnapshotChainHeight();
{"jsonrpc":"2.0","id":3,"method":"ledger_getSnapshotChainHeight","params":[]}
DBUG[01-16|08:21:19] msg="sending {"jsonrpc":"2.0","id":3,"method":"ledger_getSnapshotChainHeight","params":[]}"
{"jsonrpc":"2.0","id":3,"result":"3682878"}
"{"id":0,"jsonrpc":"2.0","result":"3682878"}"
-> EROR[01-16|08:21:20] can not get ntp server time: read udp 178.128.208.192:41187->203.107.6.88:123: i/o timeout module=ntp
EROR[01-16|08:21:30] can not get ntp server time: read udp 178.128.208.192:42092->203.107.6.88:123: i/o timeout module=ntp
EROR[01-16|08:21:40] can not get ntp server time: read udp 178.128.208.192:42906->203.107.6.88:123: i/o timeout module=ntp

Would this also cause the sync to go slower if the node does not go down fully?

Hi Dev team,

My fullnode has not been able to sync fully since yesterday as it keeps going down with an out of memory error. It has 4 GB RAM which should be sufficient for a full node. The error message is pretty long so just pasting the first few lines from the log:

*fatal error: runtime: out of memory

runtime stack:
runtime.throw(0xde3fda, 0x16)
/usr/local/go/src/runtime/panic.go:616 +0x81
runtime.sysMap(0xc4ff020000, 0x2f60000, 0xa5f300, 0x145c5f8)
/usr/local/go/src/runtime/mem_linux.go:216 +0x20a
runtime.(*mheap).sysAlloc(0x1442680, 0x2f60000, 0xb2d520)
/usr/local/go/src/runtime/malloc.go:470 +0xd4
runtime.(*mheap).grow(0x1442680, 0x17aa, 0x0)
/usr/local/go/src/runtime/mheap.go:907 +0x60
runtime.(*mheap).allocSpanLocked(0x1442680, 0x17aa, 0x145c608, 0xc41deb7423)
/usr/local/go/src/runtime/mheap.go:820 +0x301
runtime.(*mheap).alloc_m(0x1442680, 0x17aa, 0x101, 0x18)
/usr/local/go/src/runtime/mheap.go:686 +0x118
runtime.(*mheap).alloc.func1()
/usr/local/go/src/runtime/mheap.go:753 +0x4d
runtime.(mheap).alloc(0x1442680, 0x17aa, 0x10101, 0x0)
/usr/local/go/src/runtime/mheap.go:752 +0x8a
runtime.largeAlloc(0x2f53fc9, 0xc420060101, 0x4559fa)
/usr/local/go/src/runtime/malloc.go:826 +0x94
runtime.mallocgc.func1()
/usr/local/go/src/runtime/malloc.go:721 +0x46
runtime.systemstack(0x0)
/usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
/usr/local/go/src/runtime/proc.go:1175

Hi Dev team,

My fullnodes on google VPS have been going down multiple times a day since the upgrade to 1.2.1 and 1.2.2. When I connect to the IPC, I see that the nodes are having a difficulty syncing with the ntp server.

EROR[01-15|15:30:53] can not get ntp server time: read udp 10.140.0.2:48614->114.118.7.163:123: i/o timeout module=ntp

Due to that, they are considered 'not alive' even though they are syncing the blocks. Restarting gvite is the only option but is not viable.

Can you please check and provide a solution for this?

You can now trade Vite on Bittrex!

The Vite market is open, and trading will begin shortly on https://international.bittrex.com/

Nice! Great effort sandunfernando!

I think the intuitiveness and simplicity of the wallet is its most important feature.

@Shar99 said in Vite Vs. Campaign:

Is the compaign for sharing Vite Testnet Experience still on? Can't find the topic anywhere.

The Vite testnet experience campaign is still on. You can refer the following for more details:

https://medium.com/vitelabs/forum-write-up-campaign-2ec99cfbf23c