You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My bw2 agent crashes when a DR backing an ongoing subscription crashes. The crash occurs when a DR fails, comes back online, the agent reconnects to the DR and reestablishes subscriptions, and then the DR fails a second time.
When the DR first crashes, things look okay, I see things that look like the following:
peerclient.go:212 peer write error: tls: use of closed connection
peerclient.go:157 Attempting to reconnect to peer: 52.53.189.88:4514
peerclient.go:160 Peer reconnected: 52.53.189.88:4514
However, once the DR disconnects a second time, I see this:
peerclient.go:145 PEER CONNECTION to 52.53.189.88:4514: EOF
peerclient.go:157 Attempting to reconnect to peer: 52.53.189.88:4514
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xe34136]
goroutine 9188 [running]:
github.com/immesys/bw2/api.(*PeerClient).regenSubs.func1(0x0)
/go/src/github.com/immesys/bw2/api/peerclient.go:129 +0x26
created by github.com/immesys/bw2/api.(*PeerClient).rxloop
/go/src/github.com/immesys/bw2/api/peerclient.go:153 +0x664
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xe34136]
goroutine 9189 [running]:
github.com/immesys/bw2/api.(*PeerClient).regenSubs.func1(0x0)
/go/src/github.com/immesys/bw2/api/peerclient.go:129 +0x26
created by github.com/immesys/bw2/api.(*PeerClient).rxloop
/go/src/github.com/immesys/bw2/api/peerclient.go:153 +0x664
The text was updated successfully, but these errors were encountered:
My bw2 agent crashes when a DR backing an ongoing subscription crashes. The crash occurs when a DR fails, comes back online, the agent reconnects to the DR and reestablishes subscriptions, and then the DR fails a second time.
When the DR first crashes, things look okay, I see things that look like the following:
However, once the DR disconnects a second time, I see this:
The text was updated successfully, but these errors were encountered: