Topic on Project:Support desk

Nodejs needed update

Hi. When trying to edit any page using visual editor (http://dragon-mania-legends-wiki.mobga.me/Main_Page), I get the following error: http://prnt.sc/etwoev

I've checked the parsoid log and this is what I get: https://pastebin.com/kMbgmfv7 Unfortunately, I don't understand where it's going wrong, especially since I've been able to edit just fine a few days ago. I googled the issue and found other people with this problem, but no solution seemed to have helped (that or I didn't apply it correctly). Would anyone know what's going wrong?

It looks like you may not have VE set up correctly since VE seems to having trouble connecting to parsoid. See http://dragon-mania-legends-wiki.mobga.me/api.php?action=visualeditor&format=json&paction=parse&page=Main_Page&uselang=en

Did you modify your LocalSettings.php recently?

The last time VE worked properly was 4 days ago, on the 5th of April. And yes, I did. I installed GoogleSiteSearch and added the code some lines above VE. Thinking that was the problem, I added it at the bottom and even disabled it, but no change.

Verify your Parsoid is running (and/or the Parsoid address is correct); possibly it stopped because of server restart or whatever; verify it is automatically started when the server start (with systemd: sudo systemctl enable parsoid).

I reproduced this error (curl error: 7) on a test wiki where I intentionally stopped the Parsoid service. For reference, I also tried when the Parsoid service is running behind a nginx reverse proxy and, when nginx cannot contact the Parsoid service, the error when trying the VisualEditor is "apierror-visualeditor-docserver-http: HTTP 502" (which is quite logical: 502 "Bad Gateway"/"Proxy Error").

In your Parsoid logs, there are many "Killed" at the end, it could confirm Parsoid is completely dead, apparently because of a dependency error or internal error. If it does not restart or does not respond correctly, could you post only the log excerpt related to this event (by selecting only the related hours instead of the whole log). Did you upgrade recently Parsoid? What method do you use to install/upgrade Parsoid?

I just see there is a new Parsoid version (0.7.1) which requires node.js 4.0, instead of the previous version 0.6.1 which required node.js 0.8. See also Topic:To64c6edrctczmuc and Topic:To43iqflctsgx5ml, the second is exactly your error, so either you should install node.js 4.0 (possibly with Jessie backports) either you should downgrade Parsoid to 0.6.1.

Indeed that was the issue and I fixed it by following the instructions here. Thanks a lot!

But since this issue and past issues of mine have been related to outdated software, is there some sort of way of keeping oneself up-to-date, other than by checking each extension/feature individually? I gather the MW mailing lists do not send updates for these softwares, do they?

For Mediawiki there is the low-traffic mailing list mediawiki-announce, but there are no other such list for extension or external services like Parsoid.

I’m not sure that it would be practical to create 2000+ mailing lists for all MediaWiki extensions and external services, but perhaps a script or special page checking if there are newer versions for each installed extension could be practical. In fact there are ideas around for a bigger extension management (see phabricator:T118188) but possibly a smaller program checking the versions against WikiApiary could be easier and quicker to implement -- that’s an idea.

That task sounds good and I see there's been some progress. With any luck, maybe we'll see something like this before MW 1.30. Thanks again!

Hey I know this thread is 2 years old but just wanted to say that I'm having similar problems. I'm a designer learning to code so I'm not quite savvy on the backend stuff. I got MediaWiki installed on my server though, and installed the Visual Editor, and also started installing the Parsoid service etc, but I've run into this error and I have no clue what I've done wrong or what is broken. I found the installation instructions for installing and enabling the Visual Editor extremely hard to follow, even by the normal "open source backend server type stuff" standards. Are there any easier ways of dealing with this issue now?