You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2022. It is now read-only.
We're running a SoftwareFactory, a packaging of OpenStack Zuul including an etherpad. On CentOS 7 64. A yum update this morning broke etherpad : we had empty reply from the NodeJS process itself. It did work without HTTP header (like using netcat only). Looking at the update log, we tried downgrading http-parser. Then etherpad service restart. It fixed the issue.
Here are the versions
CentOS Linux release 7.7.1908 (Core)
node: v8.9.4
etherpad: 1.7.5
http-parser:
The broken version : http-parser-2.7.1-8.el7_7.2.x86_64
The functional version after downgrade : http-parser-2.7.1-8.el7.x86_64
Agreed. My problem was solved by the downgrade to begin with, I'm aware that I'm not running latest versions. Opening the issue was mostly about signaling it here and there for people search to hit some result. Sorry, I should have said this to begin with.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there
We're running a SoftwareFactory, a packaging of OpenStack Zuul including an etherpad. On CentOS 7 64. A yum update this morning broke etherpad : we had empty reply from the NodeJS process itself. It did work without HTTP header (like using netcat only). Looking at the update log, we tried downgrading http-parser. Then etherpad service restart. It fixed the issue.
Here are the versions
http-parser:
This is a duplicate of ether/etherpad-lite#3815
The text was updated successfully, but these errors were encountered: