Closed vavrusa closed 5 years ago
There's another one:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x7398ad]
goroutine 64 [running]:
github.com/Rhymen/go-whatsapp.(*Conn).writeBinary(0xc00018b860, 0xabe91b, 0x5, 0xc000656000, 0x0, 0x0, 0x800a, 0xc00024aac0, 0xe, 0xc000304f00, ...)
/go/pkg/mod/github.com/!rhymen/go-whatsapp@v0.0.0-20190208090600-c1173899de99/conn.go:241 +0x9d
github.com/Rhymen/go-whatsapp.(*Conn).query(0xc00018b860, 0xac1480, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/pkg/mod/github.com/!rhymen/go-whatsapp@v0.0.0-20190208090600-c1173899de99/contact.go:199 +0x321
github.com/Rhymen/go-whatsapp.(*Conn).Contacts(0xc00018b860, 0xc000262ce0, 0x2, 0x2)
/go/pkg/mod/github.com/!rhymen/go-whatsapp@v0.0.0-20190208090600-c1173899de99/contact.go:128 +0x76
main.(*CommandHandler).CommandSync(0xc000183680, 0xc0001f5ef8)
/go/src/github.com/mautrix-whatsapp/commands.go:160 +0x112
main.(*CommandHandler).Handle(0xc000183680, 0xc0002f0680, 0x1f, 0xc00017b980, 0xc00024a820, 0x4)
/go/src/github.com/mautrix-whatsapp/commands.go:87 +0x2f8
main.(*MatrixHandler).HandleMessage(0xc00017b3b0, 0xc00008c900)
/go/src/github.com/mautrix-whatsapp/matrix.go:161 +0x210
main.(*MatrixHandler).HandleMessage-fm(0xc00008c900)
/go/src/github.com/mautrix-whatsapp/matrix.go:43 +0x34
created by maunium.net/go/mautrix-appservice.(*EventProcessor).Start
/go/pkg/mod/maunium.net/go/mautrix-appservice@v0.1.0-alpha.3/eventprocessor.go:62 +0x55
Hi,
I have a similar problem. The bridge panics and freezes after a couple of minutes. Here is an output:
[Feb 26, 2019 20:20:51] [User/@XXXXX.XXXXX.XXXXX/ERROR] WhatsApp error: unexpected websocket close: websocket: close 1006 (abnormal closure): unexpected EOF
@enannos that output is #35
Some or all of these might be fixed with the recent go-whatsapp updates.
hi. i just made some temporary dirty workaround on Ubuntu using cronjob
SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 0 /1 root /bin/systemctl stop mautrix-whatsapp.service && /bin/systemctl start mautrix-whatsapp.service -> restart once per hour
The issue still occures with latest commit
socket close: websocket: close 1000 (normal) Mai 16 10:10:51 h2606131.stratoserver.net mautrix-whatsapp[4112]: [May 16, 2019 10:10:51] [User/@vmario89:matrix.fablabchemnitz.de/ERROR] WhatsApp error: unexpected websocket close: websocket: close 1000 (normal) Mai 16 10:10:52 h2606131.stratoserver.net mautrix-whatsapp[4112]: [May 16, 2019 10:10:52] [User/@vmario89:matrix.fablabchemnitz.de/ERROR] WhatsApp error: unexpected websocket close: websocket: close 1000 (normal) Mai 16 10:10:53 h2606131.stratoserver.net mautrix-whatsapp[4112]: [May 16, 2019 10:10:53] [User/@vmario89:matrix.fablabchemnitz.de/ERROR] WhatsApp error: unexpected websocket close: websocket: close 1000 (normal) Mai 16 10:10:54 h2606131.stratoserver.net mautrix-whatsapp[4112]: panic: repeated read on failed websocket connection Mai 16 10:10:54 h2606131.stratoserver.net mautrix-whatsapp[4112]: goroutine 24 [running]: Mai 16 10:10:54 h2606131.stratoserver.net mautrix-whatsapp[4112]: github.com/gorilla/websocket.(*Conn).NextReader(0xc00032c2c0, 0x1170f80, 0xc004d61312, 0x2, 0xc004d6c000, 0xc000001e00)
regards, Mario
That doesn't look like the latest version. The websocket close error says something more like WhatsApp error: server closed connection,code: 1000,text:
in the latest version.
Are you sure you updated properly?
yep i forgot to run "go build". I tried to clone the repo again but now i cannot compile
i have no knowledge about go.mod and dependencies :(
Sorry, committed the development replace
directives in go.mod again. Try with the latest commit
hey. thanks for the quick nightly reply 👍 i tried again now it proceeds with
but it does not generate the final built file to run. "mautrix-whatsapp" is missing
Your Go installation seems broken. If you install Go by downloading from https://golang.org/dl/, make sure you remove the old files before unpacking the new ones. Otherwise files that were removed in the new release will stick around and cause errors like that.
that was the fix :D problem of the problem. i updated go a lot in the past. but first time some error occures :) but now it seems fine. will check it out a while and will give you some feedback again. thanks for your help and all the recent updates!
regards, Mario
Seems like this issue can be closed? I've been running the bridge for a couple weeks now with no crashes.
There's several different panics after running it for a few hours:
The installed version is 485acf6de654b8fb70007876c074fb004eb9717b