FHIR Chat · tx.fhir.org down · implementers

Stream: implementers

Topic: tx.fhir.org down

view this post on Zulip Chris Moesel (Oct 11 2017 at 18:35):

I can't run the IG Publisher today because it times out connecting to the terminology server (tx.fhir.org/r3). This has been happening since this morning.

Connect to Terminology Server at http://tx.fhir.org/r3                           (08.0413sec)
Publishing Content Failed: Error sending Http Request: Connect to tx.fhir.org:80 timed out (43.0829sec)
                                                                                 (43.0831sec)
Use -? to get command line help                                                  (43.0833sec)
                                                                                 (43.0833sec)
Stack Dump (for debugging):                                                      (43.0834sec)
org.hl7.fhir.dstu3.utils.client.EFhirClientException: Error sending Http Request: Connect to tx.fhir.org:80 timed out
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.sendRequest(ClientUtils.java:256)
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.issueResourceRequest(ClientUtils.java:177)
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.issueResourceRequest(ClientUtils.java:161)
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.issueResourceRequest(ClientUtils.java:152)
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.issueGetResourceRequest(ClientUtils.java:99)
    at org.hl7.fhir.dstu3.utils.client.FHIRToolingClient.getCapabilitiesStatementQuick(FHIRToolingClient.java:169)
    at org.hl7.fhir.dstu3.context.SimpleWorkerContext.connectToTSServer(SimpleWorkerContext.java:161)
    at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:754)
    at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:299)
    at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:3589)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to tx.fhir.org:80 timed out
    at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:129)
    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
    at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:645)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:480)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
    at org.hl7.fhir.dstu3.utils.client.ClientUtils.sendRequest(ClientUtils.java:254)
    ... 9 more

view this post on Zulip Chris Moesel (Oct 11 2017 at 18:38):

http://www.isitdownrightnow.com/tx.fhir.org.html

tx_fhir_org_down.png

view this post on Zulip Lloyd McKenzie (Oct 11 2017 at 23:06):

Back up

view this post on Zulip Chris Moesel (Mar 19 2018 at 18:39):

Publisher can't access tx.fhir.org/r4, nor can I reach it from a browser. Down for everyone according to:
https://downforeveryoneorjustme.com/tx.fhir.org

view this post on Zulip Grahame Grieve (Mar 19 2018 at 18:48):

yep. upgrade disaster. working on it

view this post on Zulip Grahame Grieve (Mar 19 2018 at 18:56):

btw, the place to bring these and other IG issues up is either committers stream or the IG publishing stream. I watch those channels much more actively than this one

view this post on Zulip Chris Moesel (Mar 19 2018 at 18:57):

Ah. OK. Will do! Thanks for the redirection.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -