Closed AndrewIsh closed 6 years ago
Is this with the Docker Hub version or the current master? If the latter, how are you building it?
Thanks for your reply.
Ah, this may be part of the problem. I deployed this a while ago so my memory is a bit hazy, but I'm pretty sure I deployed using the Docker Hub version. Whereas, I forgot that when bringing everything up to date, so I've just pulled the repos and not rebuilt or anything (go easy on me, I'm not a regular Docker user). OK, so I think my first step should be to update properly (using the Docker Hub version presumably) and then see if I'm still experiencing the problem. Thanks!
The Docker Hub version is theoretically the current stable version. But we do plan to upload the current master
to Docker Hub soon, so if you do build from that and run into trouble, let us know.
OK. Well I've ditched my Docker Hub version and cloned master just to make sure I'm up to date. I'm having some weirdness trying to get it working. Sorry, this is unrelated to the original problem, but I'm hoping it'll either lead to a resolution or a clearer understanding of the problem.
I've followed the instructions on https://github.com/zotero/translation-server#development as I wanted a custom port number and it seemed the only way to get that was to modify config.js
then rebuilt. I did this but am not seeing the custom port number being used:
zotero@connect-1:~/translation-server$ docker run --rm -p 8080:8080 translation-server
From https://github.com/zotero/translators
* branch master -> FETCH_HEAD
Already up-to-date.
JavaScript warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://zotero/bluebird/util.js, line 201: unreachable code after return statement
JavaScript warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://zotero/bluebird/util.js, line 201: unreachable code after return statement
zotero(3)(+0000000): HTTP GET resource://zotero/schema/dateFormats.json
zotero(3)(+0000007): HTTP GET resource://zotero/schema/dateFormats.json succeeded with 200
Loading translators from /opt/translation-server/app/translators
zotero(3)(+0000234): HTTP server listening on *:1969
This is the relevant line in config.js
:
ref("translation-server.httpServer.port", "8080");
After making this change, I ran ./build.sh
and it seemed to complete almost immediately, which was a bit odd.
Any ideas what I might have done wrong? Many thanks :)
Don't change the config file. The port visible to the rest of your machine is just the first port passed to the -p
flag.
@dstillman Aha, useful to know, thanks. Any idea why that's being ignored then in the example above?
The debug output will still show 1969, because that's what it's bound to inside the container.
Ahaaaa
Right. After getting it up, everything seems to be working now on latest master. Many thanks @dstillman for your help, very much appreciated :) I'll close this issue.
We are using translation-server to allow us to convert materials supplied in CSL JSON to RIS. When I initially set up a translation-server instance a few months ago it was working perfectly. However, now it does not appear to be, and I'm at something of a loss as to why, I'm hoping someone here can give some pointers as to where to look. I've brought the repo and it's submodules up to date, but am still seeing the same problem.
I have been trying to figure out what's going on using Postman and watching the translation-server console. Here's an example of a request and what I'm seeing in the console:
Request (curl):
Console output:
I'm confused as to why this is running into an XML parsing error, but really don't know where to start looking.
I've also tried the BibTeX example from the docs, but am seeing a similar error:
Request (and response):
Console output:
I am sure this is going to be something obvious, but I'm failing to see what it is. Can anyone shed any light please?