-
Notifications
You must be signed in to change notification settings - Fork 613
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
Handle malformed XMPP packet responses #209
Comments
Just confirmed that the Unicode was the problem - filed #210 to track the fact that Matterbridge is generating malformed stanzas. I think this one should probably be kept open though - if another bug like this happens in the future, it really shouldn't break everything. The program should just handle the error. |
The problem here is with the underlaying library. Maybe it's better to open a bug report there. |
@42wim I can definitely file this upstream. What XMPP library does Matterbridge use? |
@strugee that would be https://github.com/mattn/go-xmpp |
This completely dropped off my radar lol, but I just filed xmppo/go-xmpp#96 👍 Sorry for the (extreme) delay! |
Thanks! |
On my production Matterbridge install, I noticed that the XMPP user had disconnected. Looking at my systemd logs showed the following:
Here's my config file:
If really necessary I can adjust my systemd unit to invoke Matterbridge with
-debug
, but I'd rather not as it will probably take a while for this to happen again and in the meantime my logs will fill up.For reference, the last IRC message sent before the bridge disconnected was from user
puckipedia
, who said:scribenick: puckipedia
. The message that seemed to cause the malformed packet is here: https://chat.indieweb.org/social/2017-06-28#t1498665324747000It includes some funky Unicode, perhaps that was it? Happy to file a separate issue if you want to track the buggy XMPP packet generation code separately from the error-handling. Note that nothing was said on the XMPP side at the time.
I'm running version
0.15.0 822605c
as reported bymatterbridge -version
.The text was updated successfully, but these errors were encountered: