go-spacemesh
go-spacemesh copied to clipboard
node stopped syncing for more than 5 hours
Description
My spacemesh node version is 1.2.13 and I deployed it on Ubuntu 18. The server has 8g+ memory and has plenty of disk. I don't use it smesh but sending transactions. This node has been working fine for weeks until it stops at layer 51219!
Steps to reproduce
Above
Actual Behavior
curl -X POST http://localhost:9094/v1/node/status
It yields
{"status":{"connectedPeers":"25", "isSynced":false, "syncedLayer":{"number":51262}, "topLayer":{"number":51322}, "verifiedLayer":{"number":51219}}}
If I check the logs, it keeps dumping something like this:
hint: ATXDB, hash: 0x67a21aceadc2d769becd4eb9c93e8f8d1b1441361b38376624cfaf4fb16608a5, err: stream reset\nhint: ATXDB, hash: 0x4bd3865563c836589a454a218414417e74c2dd510e43d6572a65ec4b96775ec0, err: stream reset\nhint: ATXDB, hash: 0xc7f1d3329cace8325fdebf705a5de0460f3bd64e8fb2096919d0b4048f298d6d, err: stream reset\nhint: ATXDB, hash: 0x45aefbb58a0b8eab0b45614757eb2e762dcaa9aea462f2cbd142ba0353fa3ec6, err: stream reset\nhint: ATXDB, hash: 0x09d25b649abdff236266483276cc4bd093993f6c4f326a3d39e13a131119e473, err: stream reset\nhint: ATXDB, hash: 0xd9b652c783bfd9fdfce9863570530a5bfb5f08a658d211fd8ac8971333a74971, err: stream reset\nhint: ATXDB, hash: 0x50b009301a75ce819558cf634afd4e6c9f23d63516d0077b522985f2200c4f7e, err: stream reset\nhint: ATXDB, hash: 0xaa5df37306ebd8452c2910693317d6088961cca2a6a21d2ca70ae9d49432a72a, err: stream reset\nhint: ATXDB, hash: 0x92ee4eeae23464a24e4c7b96639b22b277abd6ec2c8503c975d46e1dba6606e7, err: stream reset\nhint: ATXDB, hash: 0x84a97517e70f4c7e209967db78069b15aa13de660a130599d74f8bf0e1c50f26, err: stream reset\nhint: ATXDB, hash: 0xc238bee53f3db9afbfe319b77cd31ba848c005cd30ab0f6b48e5c1be4db80400, err: stream reset\nhint: ATXDB, hash: 0x16ceab213e6b8edb34b2ab351cde9f6e82b07fbeb5464bc1a4ccb529dce4d7a4, err: stream reset\nhint: ATXDB, hash: 0x28e13aa3722bc088a78e2b916bfb82a5354b2209686ce0881b34c2848be149ef, err: stream reset\nhint: ATXDB, hash: 0xc2b76264e94d3af1cef5e85e685b8f499c6f8e99784a23a15054d2f2fd8bcb9c, err: stream reset\nhint: ATXDB, hash: 0x9ad4f60d25e63709f96caeebe4ebb9e46f1de89f16789aaca158b219f8d32759, err: stream reset\nhint: ATXDB, hash: 0xe469b2355d2085c269716707675db23d565029d23c4d9f141881c41ea1747409, err: stream reset\nhint: ATXDB, hash: 0x80c9289ddafe81742caac0836b07dbe3f71948c4b914270ac5783707c33017bb, err: stream reset\nhint: ATXDB, hash: 0x7f39177a8702f3088c2ad5f80af2d4541425e1e352525f4e5e72640a937229db, err: stream reset\nhint: ATXDB, hash: 0x84fc25c895ffc0c50c34b3ce23a0464b507751b57f20d1728b80363dcae848b3, err: stream reset", "name": "sync"}
Environment
- OS: Ubuntu 18
- Node Version: 1.2.13
Additional Resources
I want to confirm two things:
- How do I fix this?
- Is there any public , reliable rpc endpoint that supports submitting transactions and querying user balance though port 9094?
Thanks
Is that still the case with recent versions?
please reopen if reproduces on v1.4