Stream: committers
Topic: Terminology Service Down
Paul Knapp (Jul 09 2018 at 11:59):
The service is now down, as reported by the build with errors.
Melva Peters (Jul 09 2018 at 19:02):
Is the terminology service down again? My build failed just now.
Lloyd McKenzie (Jul 09 2018 at 21:07):
Looks to be up now
David McKillop (Jul 09 2018 at 22:34):
FYI - When I check https://downforeveryoneorjustme.com/tx.fhir.org it's telling me it's down.
Grahame Grieve (Jul 09 2018 at 22:47):
I don't know what's up with it - my notification service is telling me it's up and down a lot without me doing anything
Paul Knapp (Jul 12 2018 at 11:10):
Down again.
Grahame Grieve (Jul 12 2018 at 12:56):
yes. badly broken; my upgrade process has failed and I'm still trying to debug
Paul Knapp (Jul 12 2018 at 12:57):
Example validation is also broken.
Grahame Grieve (Jul 12 2018 at 21:06):
I think it's back...
Eric Haas (Jul 18 2018 at 19:50):
Looks like the term server is down again....
Grahame Grieve (Jul 18 2018 at 20:01):
was just restarting it
Rick Geimer (Mar 04 2019 at 05:11):
Seems to be down at the moment:
Connect to Terminology Server at http://tx.fhir.org (16.0464sec)
-tx cache miss: Connect to http://tx.fhir.org//r4
Publishing Content Failed: Error sending Http Request: Connect to tx.fhir.org:80 timed out (28.0002sec)
(28.0002sec)
Use -? to get command line help (28.0002sec)
(28.0002sec)
Stack Dump (for debugging): (28.0002sec)
org.hl7.fhir.r5.utils.client.EFhirClientException: Error sending Http Request: Connect to tx.fhir.org:80 timed out
at org.hl7.fhir.r5.utils.client.ClientUtils.sendRequest(ClientUtils.java:331)
at org.hl7.fhir.r5.utils.client.ClientUtils.issueResourceRequest(ClientUtils.java:250)
at org.hl7.fhir.r5.utils.client.ClientUtils.issueResourceRequest(ClientUtils.java:234)
Grahame Grieve (Mar 04 2019 at 05:11):
windows just insisted on rebooting
Rick Geimer (Mar 04 2019 at 05:28):
Pesky windows. All good now.
Last updated: Apr 12 2022 at 19:14 UTC
