Topic on Project:Support desk

You're using an incompatible version of nodejs. Please see version requirements on the Parsoid page

I followed the guide posted on the Parsoid installation for Ubuntu and upon launch, this is the error I get:

Killed

{"name":"parsoid","hostname":"<hostname>","pid":17215,"level":30,"levelPath":"info/service-runner","msg":"master(17215) initializing 2 workers","time":"2019-03-12T03:07:23.720Z","v":0}

{"name":"parsoid","hostname":"<hostname>","pid":17224,"level":60,"moduleName":"/usr/lib/parsoid/src/lib/index.js","levelPath":"fatal/service-runner/worker","msg":"Unexpected token {","time":"2019-03-12T03:07:24.104Z","v":0}

{"name":"parsoid","hostname":"<hostname>","pid":17215,"level":40,"message":"first worker died during startup, continue startup","worker_pid":17224,"exit_code":1,"startup_attempt":1,"levelPath":"warn/service-runner/master","msg":"first worker died during startup, continue startup","time":"2019-03-12T03:07:25.110Z","v":0}

My configuration is correct, using curl on the api.php file works but the service does not launch. Please help.

Looks like there's something wrong in the configuration, as the message "Unexpected token {" indicates. Please review carefully the changes you made in configuration.

Thanks for the reply Ciencia,

I tried the same configuration on a different machine and it works just fine, so I'm unsure why this is happening. I think it has something to do with my hostname being incorrect.

I know there are parts of the configuration that use something like "{hostname}", which could be the problem. However, if this works with exactly the same configuration on other host, I'm out of ideas. Maybe the server where you have the problem using a different or older nodejs version that doesn't support such variables?

I think this is grounds for giving up, this software gives no indication of what's wrong.

I'm having the same issue, any tips on how to work out what this is :"Unexpected token {"

Hi all,

I have the same error on my installation.

Has anyone figured out how to fix this issue?

Thanks.

I ran into the same problem today. I was running NodeJS 4.2 on Ubuntu 16. After upgrading to NodeJS 10 the problem went away. I found a StackOverflow comment that suggested the root cause was a NodeJS incompatibility. I want to give them credit but can't add a link in this comment.