-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
etherpad start fail with abiword #3157
Comments
What OS are you using? |
sorry, code is a little bit hard to follow there... Can you give 0604649 a try? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
etherpad version: v1.6.1
abiword version : v3.0.2
etherpad always start fail when i enable abiword in setting.json .
"abiword" : "/usr/local/bin/abiword",
console err message:
Ensure that all dependencies are up to date... If this is the first time you have run Etherpad please be patient.
Ensure jQuery is downloaded and up to date...
Clearing minified cache...
Ensure custom css/js files are created...
Started Etherpad...
[2017-04-01 14:33:59.709] [ERROR] console - TypeError: stdoutCallback is not a function
at ChildProcess. (/opt/etherpad/etherpad-lite/src/node/utils/Abiword.js:94:7)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[2017-04-01 14:33:59.710] [INFO] console - graceful shutdown...
[2017-04-01 14:33:59.711] [INFO] console - Installed plugins:
[2017-04-01 14:33:59.714] [INFO] console - Report bugs at https://github.com/ether/etherpad-lite/issues
[2017-04-01 14:33:59.715] [INFO] console - Your Etherpad version is 1.6.1 (ed029b5)
[2017-04-01 14:33:59.831] [INFO] console - You can access your Etherpad instance at http://0.0.0.0:9001/
[2017-04-01 14:33:59.831] [INFO] console - The plugin admin page is at http://0.0.0.0:9001/admin/plugins
[2017-04-01 14:33:59.834] [INFO] console - db sucessfully closed.
ethpad start successful without abiword plugin.
The text was updated successfully, but these errors were encountered: