Topic on Talk:Parsoid

Ubuntu 'service parsoid status' fails with 'could not access PID file for parsoid'

8
Summary by Arlolra

Use the 0.5.1 deb.

Planetenxin (talkcontribs)

On Ubuntu 14.04 LTS, parsoid 0.4.1all

> service parsoid status

fails with

/etc/init.d/parsoid: invalid arguments
* could not access PID file for parsoid

Parsoid has been installed via official package sources. Can someone confirm this behavior?

Scharesoft (talkcontribs)

Same error here.

This post was hidden by 129.45.19.205 (history)
191.32.54.165 (talkcontribs)

root@WIKI:/etc/mediawiki/parsoid# service parsoid status

/etc/init.d/parsoid: invalid arguments

* could not access PID file for parsoid

same error..

Nischayn22 (talkcontribs)

I am facing the same problem. On further debugging it seems I have an outdated parsoid version (through apt-get)

Install Logs:

sudo apt-get install parsoid

Reading package lists... Done

Building dependency tree

Reading state information... Done

The following NEW packages will be installed:

parsoid

0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.

Need to get 0 B/6,650 kB of archives.

After this operation, 66.5 MB of additional disk space will be used.

WARNING: The following packages cannot be authenticated!

parsoid

Install these packages without verification? [y/N] Y

Selecting previously unselected package parsoid.

(Reading database ... 70190 files and directories currently installed.)

Preparing to unpack .../parsoid_0.4.0_amd64.deb ...

Unpacking parsoid (0.4.0) ...

Processing triggers for ureadahead (0.100.0-16) ...

Setting up parsoid (0.4.0) ...

Started Parsoid server on port 8142

Afterwards it shows version 0.3.0

/mediawiki$ nodejs /usr/lib/parsoid/src/api/server.js -v

parsoid 0.3.0

On trying to manually start it throws an error:

/mediawiki$ nodejs /usr/lib/parsoid/src/api/server.js

module.js:340

throw err;

^

Error: Cannot find module 'handlebars'

at Function.Module._resolveFilename (module.js:338:15)

at Function.Module._load (module.js:280:25)

at Module.require (module.js:364:17)

at require (module.js:380:17)

at Object.<anonymous> (/usr/lib/parsoid/src/api/ParsoidService.js:11:11)

at Module._compile (module.js:456:26)

at Object.Module._extensions..js (module.js:474:10)

at Module.load (module.js:356:32)

at Function.Module._load (module.js:312:12)

at Module.require (module.js:364:17)

And on starting it says started but actually doesn't start. And gives the HTTP 500 error on using VE (see Extension:VisualEditor#Troubleshooting)

Hopefully someone can help on how to fix the errors or get a new release?

Tagging @SSastry (WMF)

SSastry (WMF) (talkcontribs)
Nischayn22 (talkcontribs)

Thanks a lot. I was able to upgrade to this version.

Faced a lot of issues later configuring it, kept getting 404s. These got fixed after I added the prefix and domain statements to my LocalSettings.php.

Apparently they are not so optional.

$wgVirtualRestConfig['modules']['parsoid'] = array(  // URL to the Parsoid instance  // Use port 8142 if you use the Debian package  'url' => 'http://localhost:8000',  // Parsoid "domain", see below (optional)  'domain' => 'localhost',  // Parsoid "prefix", see below (optional)  'prefix' => 'localhost' );

Hopefully this will help someone else :)

Noboddy (talkcontribs)

Thank you, I was having exactly the same problem. Adding both prefix and domain helped me get rid of the 404 error messages!