Open jeremyshannon opened 8 months ago
And here's the tail end of the other one, looks basically the same.
[147469] DEBUG gateway: [func1:gateway/gateway.go:508] => Send from irc.free (#exile) to api.minetest (api) took 184.089µ
s
[148260] ERROR irc: [doConnect:bridge/irc/irc.go:194] disconnect: error: timed out waiting for a requested PING respo
nse
[148260] INFO irc: [doConnect:bridge/irc/irc.go:202] reconnecting in 30 seconds...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb5d75e]
goroutine 141361 [running]:
github.com/42wim/matterbridge/bridge/irc.(*Birc).handlePrivMsg(0xc0002ea840, 0x442371?, {0x0, 0x0, {0xc141440430659774, 0x86de
a86004aa, 0x342fe20}, {0xc000716700, 0x6}, {0xc0000b2200, ...}, ...})
/go/src/github.com/42wim/matterbridge/bridge/irc/handlers.go:189 +0x13e
github.com/42wim/matterbridge/bridge/irc.(*Birc).handleNotice(0xc0002ea840, 0x0?, {0x0, 0x0, {0xc141440430659774, 0x86dea86004
aa, 0x342fe20}, {0xc000716700, 0x6}, {0xc0000b2200, ...}, ...})
/go/src/github.com/42wim/matterbridge/bridge/irc/handlers.go:154 +0xf3
github.com/lrstanley/girc.HandlerFunc.Execute(0xc0003f6d98?, 0x2093700?, {0x0, 0x0, {0xc141440430659774, 0x86dea86004aa, 0x342
fe20}, {0xc000716700, 0x6}, {0xc0000b2200, ...}, ...})
/go/src/github.com/42wim/matterbridge/vendor/github.com/lrstanley/girc/handler.go:67 +0x45
github.com/lrstanley/girc.(*Caller).exec.func1.1()
/go/src/github.com/42wim/matterbridge/vendor/github.com/lrstanley/girc/handler.go:220 +0x1d5
created by github.com/lrstanley/girc.(*Caller).exec.func1
/go/src/github.com/42wim/matterbridge/vendor/github.com/lrstanley/girc/handler.go:215 +0x625
Describe the bug Two of our three servers' matterbridge instances got disconnected from freeirc and shortly after, both segfaulted. It happened before a few days ago, (before I set up multiple IRC channels) but this time I had --debug enabled on all three.
To Reproduce Connect to freeirc and minetest, and sometimes this happens.
Screenshots/debug logs Here's the tail end of the log from one:
Environment (please complete the following information):
Additional context Config file for the older one, the v4 server is substantially the same, except its main channel is hooked up to #Exile-v4: