Page MenuHomePhabricator

https://translation-server.toolforge.org/ is a HTTP 502 error since DNS name change
Closed, ResolvedPublic

Description

The citation bot uses a Zotero instance located at https://translation-server.toolforge.org/ and this server has given 503 errors since the DNS change. The main operator Smith has no idea why. It does not use OAuth. Can someone check the logs or configuration. It has been restarted at least once with no improvement. Even hints to pass onto Smith would be appreciated

Event Timeline

Nintendofan885 renamed this task from Tool not working since DNS name change to https://translation-server.toolforge.org/ is not working since DNS name change.Aug 26 2020, 1:20 PM

https://admin.toolforge.org/tools lists smith609 as the only maintainer. Hence subscribing.

I've initiated an abandoned tool procedure so we can add additional maintainers and hopefully fix the tool. smith609 is reportedly busy IRL right now.

The cronjob is throwing this error:

Error: Cannot find module 'semver'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:595:15)
    at Function.Module._load (internal/modules/cjs/loader.js:521:25)
    at Module.require (internal/modules/cjs/loader.js:651:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/usr/share/npm/lib/utils/unsupported.js:2:14)
    at Module._compile (internal/modules/cjs/loader.js:703:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:714:10)
    at Module.load (internal/modules/cjs/loader.js:613:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:552:12)
    at Function.Module._load (internal/modules/cjs/loader.js:544:3)
internal/modules/cjs/loader.js:597
    throw err;

Crontab:

12 * * * * /usr/bin/jsub -N cron-29 -l mem_free=512M,h_vmem=1000M -once -quiet npm start --prefix www

Log files:

/data/project/translation-server/.npm/_logs

If anyone would like shell access to look around let me know.

After some various things, it now reports it is running

> translation-server@2.0.3 start /mnt/nfs/labstore-secondary-tools-project/translation-server/www
> node src/server.js

(3)(+0000000): Translators initialized with 544 loaded

(3)(+0000004): Listening on 0.0.0.0:1969

But can't connect

curl -d 10.2307/4486062 -H 'Content-Type: text/plain' http://0.0.0.0:1969/search
curl: (7) Failed to connect to 0.0.0.0 port 1969: Connection refused

Unclear about IP/dns setup

Is there a problem with all the toolforge servers running on one IP address and the translation server not being able to open the right port? I know http and https traffic uses http header magic to allow multiple servers on the same port

Since learned it should be installed per: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Node.js
I have not had a moments time to try it, but suspect this convention would allow the proxy to see it.

Thank you to all those looking into this.

@Green_Cardamom - any progress or thoughts on this? Thank you.

I'm not really a JS person but suspect this might be solved by simply installing the software from scratch following the directions at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Node.js and making sure everything is in the correct directories. Ideally by someone familiar with JS and/or Node. Perhaps delete everything and start over with a fresh install. What I noticed is the current install it not in the right directories per linked directions.

Aklapper renamed this task from https://translation-server.toolforge.org/ is not working since DNS name change to https://translation-server.toolforge.org/ is a HTTP 502 error since DNS name change.Feb 15 2022, 10:19 PM

After some various things, it now reports it is running

> translation-server@2.0.3 start /mnt/nfs/labstore-secondary-tools-project/translation-server/www
> node src/server.js

(3)(+0000000): Translators initialized with 544 loaded

(3)(+0000004): Listening on 0.0.0.0:1969

But can't connect

curl -d 10.2307/4486062 -H 'Content-Type: text/plain' http://0.0.0.0:1969/search
curl: (7) Failed to connect to 0.0.0.0 port 1969: Connection refused

Unclear about IP/dns setup

The service inside the pod needs to listen on port 8000 per https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Node.js#Conventions.

The bot is now using the wikipedia citoid instance, so this can probably be closed.

Hi, I would like to delete the tool entirely. If someone wants to have this service, it would best to start over with a new account and install.

Hi, I would like to delete the tool entirely. If someone wants to have this service, it would best to start over with a new account and install.

See Toolforge (Tools to be deleted) for instructions on how to request deletion of a tool you maintain.