-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Running etherpad-lite on nodejs 4.2.0 doesn't connect to Mysql #2803
Comments
You have this problem because of a configuration problem. Add This needs to be added to the default configuration file shipped with etherpad-lite! |
I just tested it. Doesn't work either. https://github.com/Pita/ueberDB/wiki/MySQL-Sockets I also couldn't find socketPath in the code: I used "port" to specify the socket, as it is written in the documentation. Or is the documentation out of date? 🙈 |
@MorrisJobke can you post your current output of etherpad-lite, when running with the above mentioned settings? Just asking, because I suspect something else here, as we seem to be running the same software, but for me it's working! |
This is the output for nodejs 0.12.x:
And this is the output for nodejs 4.2.0
Also connecting to the socket works:
I just noticed following line during the startup:
This means something like "the rule for targe 'Release/obj.target/bufferutil/src/bufferutil.o' failed". I think that this is the problem. |
Ha! still on nodejs 4.1.2 here! |
Let me check that. |
Yes. Works just fine with 4.1.2. I used a version from the Arch Rollback Machine: http://seblu.net/a/arm/packages/n/nodejs/ \o/ |
thanks for testing! |
v4.2.1 is out and should fix this. please reopen the issue if the bug remains/reoccurs. |
upstream fix nodejs/node@c245a199a7 |
Just upgraded to 4.2.1 and it works 👍 Thanks :) |
@webzwo0i Thanks for the good work! |
I then downgraded to nodejs 0.12.7 and etherpad just starts fine.
cc @Gared
This could also be very likely a nodejs problem, but I'm unsure where and how to report this.
@Gared I add you, because you added the switch: Gared@bf7930f - I also admit that I used a 1.5.7 and only applied your patch. Maybe this couldn't work, but on ther other side I also couldn't find big changes between 1.5.7 and the current HEAD: 8359756...develop#diff-5d2aa4336c4964b828a123e20e09b73c
Feel free to simply close this, if I just did it the wrong way.
The text was updated successfully, but these errors were encountered: