matrix-puppet-hangouts icon indicating copy to clipboard operation
matrix-puppet-hangouts copied to clipboard

Long-polling request failed: Request connection error: Response payload is not completed

Open MurzNN opened this issue 8 years ago • 5 comments

After some days of work - matrix-puppet-hangouts bridge show the errors in logs:

10:08
WARNING:hangups.channel:Long-polling request failed: Request connection error: Response payload is not completed
10:08
WARNING:hangups.channel:retry attempt count is now 1
10:08
WARNING:hangups.channel:Long-polling request failed: SID became invalid
10:08
WARNING:hangups.channel:retry attempt count is now 2

After this - when I try to send message - it show error:

16:16
Message send failure! Exception: Session is closed

Restarting bridge solve the problem. Can I fix this problem without full restarting of puppet?

MurzNN avatar Aug 16 '17 13:08 MurzNN

What version of hangups are you using?

AndrewJDR avatar Aug 16 '17 21:08 AndrewJDR

hangups (0.4.3)

MurzNN avatar Aug 17 '17 05:08 MurzNN

Ah ok, I fixed a similar issue with retries within hangups, but it should be in there if you have 0.4.3. I'm really not sure what the problem is unfortunately. I've had a hangups bridge running for quite some time (months) without any issues. It does look like something failed inside the retry logic of hangups, if I had to guess. You can see if @tdryer and the folks over at the hangups project have any ideas.

AndrewJDR avatar Aug 17 '17 05:08 AndrewJDR

You could also try running the latest git version of hangups instead of the tagged one to see if they fixed an issue recently. To do that, you can follow the instructions I left in this thread: https://github.com/matrix-hacks/matrix-puppet-hangouts/issues/7

AndrewJDR avatar Aug 17 '17 05:08 AndrewJDR

Another option you have is to run the same exact commit of hangups that I have been running on my bridge, which is: 30ba087bd5b99da98e463c1b03405c06eeaad519 Run git reset --keep 30ba087bd5b99da98e463c1b03405c06eeaad519 inside your hangups repo to reset to that.

Maybe some bug was introduced recently (sometime between that commit but before 0.4.3) into hangups, and that would help you identify whether that was the case.

AndrewJDR avatar Aug 17 '17 05:08 AndrewJDR