-
Notifications
You must be signed in to change notification settings - Fork 49
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
Disconnecting with error: Short read #28
Comments
Probably related to #10 which was supposed to be resolved. |
Is your network connection dying? |
How often is "constantly", precisely? |
My network connection is not dying. bitlbee and my irc client are running in a tmux session in a datacenter. Constantly means every 10 minutes. |
|
So, it was happening constantly at the time of the report but now it's far more infrequent. |
Does this still happen? |
Same problem on CentOS7 with bitlbee-3.2.2-3.el7.x86_64 and current master of this repo. |
Note that getting disconnected with "short read" usually just means getting disconnected normally. If it happens once every few hours it's not a bug. |
Well ok. But everytime all my group fb chats are like this:
And I have to /join #channel back manually. Which is really annoying. |
How about |
I will give it a try and provide report after few hours. |
Ok, auto rejoin works but now I just see nothing else than rejoins every few minutes/hours. This is not a solution. |
What do you mean? You stop receiving chat messages from the auto-rejoined channel? |
I am receiving them but for example after night when nobody is writing, my backlog is full of rejoins. And maybe somewhere between them are some messages which I can overlook. |
We really have no control over this happening, but as of ef58beb, the plugin will attempt to silently reconnect. This should alleviate this issue for the most part. |
Hey. I'm back with a new bug!
I'm constantly getting disconnected with this error.
I'm using the last version from master (also tried development branch).
I tried:
The text was updated successfully, but these errors were encountered: