Stream: implementers
Topic: tx.fhir.org down?
Chris Moesel (Aug 11 2017 at 14:31):
I'm trying to run the r3 IG publishing jar, but it keeps timing out trying to reach the terminology server (http://tx.fhir.org/r3). Is tx.fhir.org down? I can't get to it via my browser either (times out, as opposed to serving an error).
Rick Geimer (Aug 11 2017 at 17:23):
Yes, definitely down. All builds seem to be breaking at the moment because of that.
Grahame Grieve (Aug 11 2017 at 20:20):
fixed. Server rebooted. I don't know why the service didn't start
Grahame Grieve (Aug 11 2017 at 20:20):
nor do I know why the server rebooted
Travis Stenerson (Aug 23 2017 at 21:02):
Is this down at the moment? I'm getting connection refused..
Bryn Rhodes (Aug 23 2017 at 22:11):
Yeah, seems to be down, I can't get any IGs to build, gets the same error.
Grahame Grieve (Aug 24 2017 at 01:23):
sorry, fixed
Bryn Rhodes (Aug 24 2017 at 16:47):
No worries, thanks Grahame
Patrick Werner (Jan 20 2020 at 11:05):
tx.fhir.org seems down atm? https://downforeveryoneorjustme.com/tx.fhir.org
Grahame Grieve (Jan 20 2020 at 11:08):
I was just restarting it after upgrading to fix a bug
Grahame Grieve (Jan 20 2020 at 11:27):
it won't start :-(
Grahame Grieve (Jan 20 2020 at 12:14):
and downgrading doesn't help - the problem was waiting for next restart whatever it is :-(
Grahame Grieve (Jan 20 2020 at 12:48):
fixed
Michael O'Keefe (Sep 23 2020 at 16:51):
Seems like tx.fhir.org may be down; http://tx.fhir.org/r4 is timing out for me
Grahame Grieve (Sep 23 2020 at 16:52):
I'm working on it
Grahame Grieve (Sep 23 2020 at 17:08):
back
Michael O'Keefe (Sep 23 2020 at 17:08):
Confirmed. Thanks!
Aleksandra Pavlyshina (Oct 12 2020 at 19:35):
Hey Grahame, seems like tx.fhir.org is down; https://downforeveryoneorjustme.com/tx.fhir.org
Aleksandra Pavlyshina (Oct 12 2020 at 19:51):
I'm trying to run the IG Publisher with the -tx n/a while the tx.fhir.org is down but getting this error: "org.hl7.fhir.exceptions.FHIRException: Attempt to use Terminology server when no Terminology server is available" (likely because I have valuesets in my IG). @Grahame Grieve please help :big_smile:
java -jar org.hl7.fhir.publisher.cli-1.1.34.jar -ig ig.ini -tx n/a
Lloyd McKenzie (Oct 12 2020 at 20:17):
The IGPublisher can't be run without a terminology server right now.
Aleksandra Pavlyshina (Oct 12 2020 at 20:25):
Ah, I see. Thank you Lloyd :smiling_face:
David Hay (Oct 12 2020 at 20:36):
The IGPublisher can't be run without a terminology server right now.
Is that temporary?
Lloyd McKenzie (Oct 12 2020 at 21:42):
Don't think so. Grahame was tired of people submitting IGs that had terminology problems because they'd hard-coded their local builds to run without the tx server. (Personally, I think there are other more preferable ways to address that though...)
@Grahame Grieve
Grahame Grieve (Oct 12 2020 at 22:02):
no plans, no. I have plenty of plans around changing the server to be more reliable
Patrick Werner (Jan 18 2021 at 08:23):
The server seems to be down since at least yesterday.
Patrick Werner (Jan 18 2021 at 08:24):
Lloyd McKenzie said:
The IGPublisher can't be run without a terminology server right now.
The IG publisher detects offline mode, but then fails at:
Publishing Content Failed: Attempt to use Terminology server when no Terminology server is available (01:26.0087)
(01:26.0091)
Use -? to get command line help (01:26.0092)
(01:26.0092)
Stack Dump (for debugging): (01:26.0094)
org.hl7.fhir.exceptions.FHIRException: Attempt to use Terminology server when no Terminology server is available
at org.hl7.fhir.r5.context.BaseWorkerContext.validateCodeBatch(BaseWorkerContext.java:815)
Jose Costa Teixeira (Jan 18 2021 at 10:41):
if you want to continue building IGs locally , you can run genonce.bat -tx n/a (I think this disables terminology server checks and functionality)
Patrick Werner (Jan 18 2021 at 14:25):
tried that, fails. The genonce.sh detects that the tx fhir is down:
Checking internet connection...
curl: (7) Failed to connect to tx.fhir.org port 80: Operation timed out
Offline
-tx n/a
Patrick Werner (Jan 18 2021 at 14:25):
but fails later:
Processing Conformance Resources (00:57.0077)
Generating Snapshots (01:06.0216)
Generating Narratives (01:18.0357)
Publishing Content Failed: Attempt to use Terminology server when no Terminology server is available (01:26.0087)
(01:26.0091)
Use -? to get command line help (01:26.0092)
(01:26.0092)
Stack Dump (for debugging): (01:26.0094)
org.hl7.fhir.exceptions.FHIRException: Attempt to use Terminology server when no Terminology server is available
at org.hl7.fhir.r5.context.BaseWorkerContext.validateCodeBatch(BaseWorkerContext.java:815)
at org.hl7.fhir.r5.renderers.ValueSetRenderer.getConceptsForCodes(ValueSetRenderer.java:1001)
at org.hl7.fhir.r5.renderers.ValueSetRenderer.genInclude(ValueSetRenderer.java:825)
at org.hl7.fhir.r5.renderers.ValueSetRenderer.generateComposition(ValueSetRenderer.java:748)
at org.hl7.fhir.r5.renderers.ValueSetRenderer.render(ValueSetRenderer.java:84)
at org.hl7.fhir.r5.renderers.ValueSetRenderer.render(ValueSetRenderer.java:73)
at org.hl7.fhir.r5.renderers.ResourceRenderer.render(ResourceRenderer.java:74)
at org.hl7.fhir.igtools.publisher.Publisher.generateNarratives(Publisher.java:1135)
at org.hl7.fhir.igtools.publisher.Publisher.loadConformance(Publisher.java:3826)
at org.hl7.fhir.igtools.publisher.Publisher.createIg(Publisher.java:877)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:732)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:8417)
Grahame Grieve (Jan 18 2021 at 21:04):
it should be back now
Martin Morrey (Feb 17 2021 at 15:17):
Seems to be down again image.png
Rob Hausam (Feb 17 2021 at 15:20):
I'm checking it.
Kirstine Rosenbeck Gøeg (Feb 17 2021 at 15:21):
Perfect. Thanks Rob. I have the same problem.
Mark Iantorno (Feb 17 2021 at 15:22):
I've given the service a boot twice this morning
Mark Iantorno (Feb 17 2021 at 15:22):
The box may need to be reset
Mark Iantorno (Feb 17 2021 at 15:22):
@Rob Hausam are you resetting it?
Rob Hausam (Feb 17 2021 at 15:23):
Yes. The service is coming back up. I just restarted the server maybe an hour ago.
Rob Hausam (Feb 17 2021 at 15:31):
It takes a while to start. Should be up now.
Rob Hausam (Feb 17 2021 at 15:33):
FYI, I'm working on getting the SNOMED CT International Edition updated to the latest Jan 2021 version, and hopefully that will be available soon.
Martin Morrey (Feb 17 2021 at 15:35):
Yes, I can see it now. Thank you :)
Martin Morrey (Feb 22 2021 at 11:39):
Hi Rob. It's down again I'm afraid :(
Juan Manuel Caputo (Feb 22 2021 at 14:24):
I confirme, for now is down
Lloyd McKenzie (Feb 22 2021 at 15:05):
@Rob Hausam @Grahame Grieve @Mark Iantorno
Mark Iantorno (Feb 22 2021 at 15:05):
I'll fix it now
Rob Hausam (Feb 22 2021 at 15:12):
Just saw this.
Mark Iantorno (Feb 22 2021 at 15:16):
I just reset the box
Mark Iantorno (Feb 22 2021 at 15:17):
making sure the service is starting
Mark Iantorno (Feb 22 2021 at 15:17):
Just started the service
Mark Iantorno (Feb 22 2021 at 15:17):
give it like 5-10 min
Martin Morrey (Feb 22 2021 at 15:21):
Thanks Mark :smile:
Juan Manuel Caputo (Feb 22 2021 at 18:04):
It's Working, Thank you very Much!
Fabien Rica (Jul 05 2021 at 11:38):
Hi all, is it possible that maybe tx.fhir.org is down?
Fabien Rica (Jul 05 2021 at 11:43):
I get a "Connect to tx.fhir.org:80 timed out", I remembered it happened some months ago and it was quickly fixed at the time by rebooting the machine :)
Roeland Luykx (Jul 05 2021 at 12:17):
Fabien Rica said:
I get a "Connect to tx.fhir.org:80 timed out", I remembered it happened some months ago and it was quickly fixed at the time by rebooting the machine :)
see https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Term.20server.20is.20down.2E.2E.2E
Fabien Rica (Jul 05 2021 at 12:24):
Thanks @Roeland Luykx
Patrick Werner (Nov 16 2021 at 14:24):
seems to be down, shows: Unable to find homepage.html
Lloyd McKenzie (Nov 16 2021 at 15:07):
@Mark Iantorno @Rob Hausam
Patrick Werner (Nov 16 2021 at 16:24):
(dirty) fix for my gitlab ci pipeline: commenting out line 38 in _updatePublisher.sh
Rob Hausam (Nov 16 2021 at 18:50):
According to the monitor it's been up for the past 10 hours. There are no announcements that it was intentionally taken down (and that would show up in the monitor, anyway). It's responding to my requests - so I assume it's ok for others, too?
Patrick Werner (Nov 16 2021 at 19:03):
curl on tx.fhir.org returns http status code 500, which then causes the updatePublisher Script to fail
Matt Rouhana (Nov 16 2021 at 19:04):
_updatePublisher.sh results:
> [ig-build 13/14] RUN _updatePublisher.sh -y:
#19 0.578 Checking internet connection
#19 1.979 curl: (22) The requested URL returned error: 500 Internal Server Error
#19 1.982 Offline (or the terminology server is down), unable to update. Exiting
Patrick Werner (Nov 16 2021 at 19:05):
so tx.fhir.org/r4 is working, but tx.fhir.org itself is returning the wrong status code
Rob Hausam (Nov 16 2021 at 19:16):
Yes, that's interesting. As I mentioned, the last restart of the server was a bit over 11 hours ago. That roughly corresponds with @Grahame Grieve's release of FHIRServer v2.0.2.
Patrick Werner (Nov 16 2021 at 19:35):
ah! ok so the release probably changed the status code then.
Jacob Percival (Nov 16 2021 at 19:53):
Looks like the same thing is happening for _genOnce.sh. Narrative generation fails, and I'm guessing it's the same issue of terminating if it encounters a 500 Error. Screen-Shot-2021-11-16-at-11.49.33-AM.png
Patrick Werner (Nov 16 2021 at 20:19):
Yes. as the termserver itself is working fine i changed the curl line to curl -sSf google.com > /dev/null
Patrick Werner (Nov 16 2021 at 20:20):
this way the IG is built WITH tx support. (dirty fix, but working until the page is fixed
Grahame Grieve (Nov 16 2021 at 20:29):
restarting tx.fhir.org to fix this
Grahame Grieve (Nov 16 2021 at 20:32):
back
Jacob Percival (Nov 16 2021 at 20:37):
Grahame Grieve said:
restarting tx.fhir.org to fix this
Looks good from here. Thank you so much!
Patrick Werner (Nov 17 2021 at 09:14):
thanks @Grahame Grieve !
Richard Ettema (Dec 10 2021 at 21:28):
@Grahame Grieve , @Rob Hausam - looks like tx.fhir.org/r4 is having issues returning the TerminologyCapabilitiesStatement. I'm getting an "Out of memory" on this url http://tx.fhir.org/r4/metadata?mode=terminology
Rob Hausam (Dec 10 2021 at 21:49):
I'm trying to look at it. But it hasn't responded yet - probably because it's "out of memory".
Rob Hausam (Dec 10 2021 at 21:53):
Remote desktop isn't responding for me, so I suspect we may need to bounce the VM instance itself. @Grahame Grieve @Mark Iantorno
Grahame Grieve (Dec 10 2021 at 21:54):
whatever went wrong was so bad that the monitor process couldn't deal with it either
Rob Hausam (Dec 10 2021 at 21:55):
right
Richard Ettema (Dec 10 2021 at 21:56):
Ouch
Rob Hausam (Dec 10 2021 at 22:25):
It didn't restart cleanly - but it's back up again now.
Rob Hausam (Dec 10 2021 at 22:26):
@Richard Ettema
Richard Ettema (Dec 10 2021 at 22:26):
Thank you!
Last updated: Apr 12 2022 at 19:14 UTC
