Topic on Talk:Parsoid

Parsoid is not running Ubuntu 18.10

3
Summary by Arlolra

The exit status 126 is probably a permission error when trying to execute service-runner.

2A0B:33C0:2:22:A4FA:7E0C:919F:30E7 (talkcontribs)

I installed the parsoid as described in the official doc. But it is not running and throws that error:


1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]

2 info using npm@5.8.0

3 info using node@v8.11.4

4 verbose run-script [ 'prestart', 'start', 'poststart' ]

5 info lifecycle parsoid@0.10.0~prestart: parsoid@0.10.0

6 info lifecycle parsoid@0.10.0~start: parsoid@0.10.0

7 verbose lifecycle parsoid@0.10.0~start: unsafe-perm in lifecycle true

8 verbose lifecycle parsoid@0.10.0~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/lib/parsoid/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

9 verbose lifecycle parsoid@0.10.0~start: CWD: /usr/lib/parsoid

10 silly lifecycle parsoid@0.10.0~start: Args: [ '-c', 'service-runner' ]

11 silly lifecycle parsoid@0.10.0~start: Returned: code: 126  signal: null

12 info lifecycle parsoid@0.10.0~start: Failed to exec start script

13 verbose stack Error: parsoid@0.10.0 start: `service-runner`

13 verbose stack Exit status 126

13 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)

13 verbose stack     at emitTwo (events.js:126:13)

13 verbose stack     at EventEmitter.emit (events.js:214:7)

13 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)

13 verbose stack     at emitTwo (events.js:126:13)

13 verbose stack     at ChildProcess.emit (events.js:214:7)

13 verbose stack     at maybeClose (internal/child_process.js:925:16)

13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

14 verbose pkgid parsoid@0.10.0

15 verbose cwd /usr/lib/parsoid

16 verbose Linux 4.18.0-16-generic

17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"

18 verbose node v8.11.4

19 verbose npm  v5.8.0

20 error code ELIFECYCLE

21 error errno 126

22 error parsoid@0.10.0 start: `service-runner`

22 error Exit status 126

23 error Failed at the parsoid@0.10.0 start script.

23 error This is probably not a problem with npm. There is likely additional logging output above.

24 verbose exit [ 126, true ]


does anybody have an idea how to fix it?

Arlolra (talkcontribs)

The exit status 126 is probably a permission error when trying to execute service-runner.

2A0B:33C0:2:22:A4FA:7E0C:919F:30E7 (talkcontribs)

Thanks a lot. Seems like the service-runner.js caused the problems.