Open hossnys opened 8 months ago
we updated the README, you didn't provide stellar configs
added the missing stellar configs , but after that the bot panic and throw this error
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4 pc=0x85dfdc]
goroutine 220 [running]:
github.com/centrifuge/go-substrate-rpc-client/v4/types.(*Metadata).FindStorageEntryMetadata(0xc0004a4b40?, {0xb3036e?, 0x12?}, {0xb2d38d?, 0x0?})
/home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/metadata.go:298 +0x1c
github.com/centrifuge/go-substrate-rpc-client/v4/types.CreateStorageKey(0xa1e9a0?, {0xb3036e, 0xc}, {0xb2d38d, 0x5}, {0xc0004a4b40, 0x2, 0x2})
/home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/storage_key.go:76 +0x11b
github.com/threefoldtech/tfchain/clients/tfchain-client-go.(*Substrate).GetTwin(0xc00040a140?, 0x1ce764?)
/home/runner/go/pkg/mod/github.com/threefoldtech/tfchain/clients/tfchain-client-go@v0.0.0-20231129121046-56ffc1f8f5c6/twin.go:106 +0xd4
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(*twinDB).Get(0xc0005260a0, 0x15)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/twindb.go:45 +0x1c7
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.VerifySignature({0xd07540?, 0xc0005260a0?}, 0xc0003f0bb0)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/sig.go:97 +0x47
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.Peer.handleIncoming({0xc0006f8240, {0xd0c370, 0xc00040a0c0}, {0xd07540, 0xc0005260a0}, 0xc00010c380, 0xc0003c0120, 0xc0003c0300, 0xc000526080}, 0xc0003f0bb0)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:178 +0xf5
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(*Peer).process(0xc0007d00f0, {0xd09320, 0x1179920})
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:223 +0xd6
created by github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.NewPeer in goroutine 1
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:159 +0x805
It will be fixed through the in the new release:
verified
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4 pc=0x85dbfc]
goroutine 22582 [running]: github.com/centrifuge/go-substrate-rpc-client/v4/types.(Metadata).FindStorageEntryMetadata(0xc000644c00?, {0xb2f5f2?, 0x12?}, {0xb2c611?, 0x10e6048?}) /home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/metadata.go:298 +0x1c github.com/centrifuge/go-substrate-rpc-client/v4/types.CreateStorageKey(0xa1d9c0?, {0xb2f5f2, 0xc}, {0xb2c611, 0x5}, {0xc000644c00, 0x2, 0x2}) /home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/storage_key.go:76 +0x11b github.com/threefoldtech/tfchain/clients/tfchain-client-go.(Substrate).GetTwin(0xc0008320c0?, 0xa2212c?) /home/runner/go/pkg/mod/github.com/threefoldtech/tfchain/clients/tfchain-client-go@v0.0.0-20231129121046-56ffc1f8f5c6/twin.go:106 +0xd4 github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(twinDB).Get(0xc0000325a0, 0x15) /home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/twindb.go:45 +0x1c7 github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.VerifySignature({0xce39a8?, 0xc0000325a0?}, 0xc000576fd0) /home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/sig.go:97 +0x47 github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.Peer.handleIncoming({0xc000630240, {0xce8810, 0xc000832080}, {0xce39a8, 0xc0000325a0}, 0xc000306180, 0xc00042a360, 0xc00042a480, 0xc000032590, {0xce4ec8, ...}}, ...) /home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:232 +0xb7 github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(Peer).process(0xc000bd66c0, {0xce5788, 0x1154600}) /home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:277 +0xc5 created by github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.NewPeer in goroutine 1 /home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:164 +0x89e
@hossnys I think you can try the new release v0.13.0
@rawdaGastan will do
got panic also with this version v0.13.0
2023/12/27 15:28:37 Connecting to wss://tfchain.grid.tf/ws...
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
2023/12/27 15:28:37 Connecting to wss://tfchain.grid.tf:443...
2023/12/27 15:28:38 Connecting to wss://tfchain.grid.tf/ws...
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
2023/12/27 15:28:38 Connecting to wss://tfchain.dev.grid.tf/ws...
3:28PM INF starting peer session=monbot-2031321 twin=6
2023/12/27 15:28:39 Connecting to wss://tfchain.dev.grid.tf:443...
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
2023/12/27 15:28:39 Connecting to wss://tfchain.dev.grid.tf/ws...
3:28PM ERR check node 55 failed error="rmb version call in devnet failed using node twin 273 with node ID 55: relay info is not set for this twin"
2023/12/27 15:28:39 Connecting to wss://tfchain.dev.grid.tf:443...
3:28PM ERR failed to read message error="websocket: close 1006 (abnormal closure): unexpected EOF"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4 pc=0x85dbfc]
goroutine 261 [running]:
github.com/centrifuge/go-substrate-rpc-client/v4/types.(*Metadata).FindStorageEntryMetadata(0xc0008941b0?, {0xb2f5f2?, 0x12?}, {0xb2c611?, 0x4196e5?})
/home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/metadata.go:298 +0x1c
github.com/centrifuge/go-substrate-rpc-client/v4/types.CreateStorageKey(0xa1d9c0?, {0xb2f5f2, 0xc}, {0xb2c611, 0x5}, {0xc0008941b0, 0x2, 0x2})
/home/runner/go/pkg/mod/github.com/centrifuge/go-substrate-rpc-client/v4@v4.0.12/types/storage_key.go:76 +0x11b
github.com/threefoldtech/tfchain/clients/tfchain-client-go.(*Substrate).GetTwin(0xc0006200c0?, 0x6a6630?)
/home/runner/go/pkg/mod/github.com/threefoldtech/tfchain/clients/tfchain-client-go@v0.0.0-20231129121046-56ffc1f8f5c6/twin.go:106 +0xd4
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(*twinDB).Get(0xc00031a0a0, 0x1348)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/twindb.go:45 +0x1c7
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.VerifySignature({0xce39a8?, 0xc00031a0a0?}, 0xc0005aa210)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/sig.go:97 +0x47
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.Peer.handleIncoming({0xc000620040, {0xce8810, 0xc000620080}, {0xce39a8, 0xc00031a0a0}, 0xc00010c380, 0xc00052e000, 0xc00052e120, 0xc00031a090, {0xce4ec8, ...}}, ...)
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:232 +0xb7
github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.(*Peer).process(0xc0005f2000, {0xce5788, 0x1154600})
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:277 +0xc5
created by github.com/threefoldtech/tfgrid-sdk-go/rmb-sdk-go/peer.NewPeer in goroutine 1
/home/runner/work/tfgrid-sdk-go/tfgrid-sdk-go/rmb-sdk-go/peer/peer.go:164 +0x89e
@hossnys can you try to run the bot without the bridges checks?
tested it , and didn't panic till now , but it keep sending messages without respecting MINS env variable .
It is recommended to use any of the latest versions
updated the bot to version 0.13.13 and disabled bridge monitoring to check the reason of panic .
seems that bridge monitoring part was the cause of panic as bot works fine after disabling it , this need to be fixed to get bridge monitoring working again.
@hossnys do you still have some issues with it?
it's working fine now but without bridge monitoring part
Did you try the latest version?
the latest version on mainnet is 0.15.10 , and we was already running it but with disabling bridge monitoring , let me enable it and watch what will happen there .
Describe the bug
after updating monitoring bot to latest version (v0.11.9) and running it , it stopped working
logs :