Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panic on reconnect #272

Closed
AhaEdgar opened this issue Dec 26, 2018 · 2 comments · Fixed by #353
Closed

panic on reconnect #272

AhaEdgar opened this issue Dec 26, 2018 · 2 comments · Fixed by #353

Comments

@AhaEdgar
Copy link

WARN: 2018/12/26 11:53:00 Reconnection sucessful
2018-12-26T11:53:00.758819594Z panic: runtime error: invalid memory address or nil pointer dereference
2018-12-26T11:53:00.758841266Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x6e9e5e]
2018-12-26T11:53:00.758845334Z
2018-12-26T11:53:00.758848408Z goroutine 8231 [running]:
2018-12-26T11:53:00.758851484Z mqtt-go/vendor/github.com/eclipse/paho%2emqtt%2egolang.(*client).internalConnLost(0xc000217880, 0xafd6e0, 0xc0304e4af0)
2018-12-26T11:53:00.758854779Z /go/src/mqtt-go/vendor/github.com/eclipse/paho.mqtt.golang/client.go:460 +0x5e
2018-12-26T11:53:00.758858029Z created by mqtt-go/vendor/github.com/eclipse/paho%2emqtt%2egolang.errorWatch
2018-12-26T11:53:00.758861003Z /go/src/mqtt-go/vendor/github.com/eclipse/paho.mqtt.golang/net.go:332 +0x1df

@kbudde
Copy link

kbudde commented Jan 5, 2019

Hi,

I think I had the same issue.
In my case it was caused because I triggered a (re)connect in the connectionLostHandler.
At the same time the Autoreconnect was trying to connect as well.

I think it is not a good idea to disturb the automatic reconnect.

@zcxzcxczcx
Copy link

hi,i want to know you how to reconnect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants