FHIR Chat · tx.fhir.org down? · IG creation

Stream: IG creation

Topic: tx.fhir.org down?

Patrick Werner (Dec 02 2020 at 10:39):

Hi, the server seems to be down.

Patrick Werner (Dec 02 2020 at 10:41):

And the IG build fails without the tx server:

curl: (7) Failed to connect to tx.fhir.org port 80: Operation timed out
Offline
-tx n/a
`````

Patrick Werner (Dec 02 2020 at 10:42):

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:802)
        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)

Grahame Grieve (Dec 02 2020 at 10:42):

yes I am upgrading it

Grahame Grieve (Dec 02 2020 at 12:36):

it's back. should be stable now, except for a few minuets when I restart once more

Patrick Werner (Dec 02 2020 at 18:08):

We are now getting Unable to resolve value set (from http://tx.fhir.org/r4)on Codings containing valid loinc codes or

{
            "coding": [
              {
                "system": "http://terminology.hl7.org/CodeSystem/observation-category",
                "code": "laboratory"
              }
            ]
          }

Patrick Werner (Dec 02 2020 at 18:09):

building locally produces less errors, but i get some: Previous POST attempt returned HTTP<422> from url

Grahame Grieve (Dec 02 2020 at 19:32):

@Mark Iantorno still getting those http logs

Mark Iantorno (Dec 02 2020 at 19:33):

What build?

Mark Iantorno (Dec 02 2020 at 19:33):

(deleted)

Mark Iantorno (Dec 02 2020 at 19:34):

Looks as though I missed an error state somewhere

Mark Iantorno (Dec 02 2020 at 19:35):

I will look into after the validation task I"m currently on, but it shouldn't be visible unless something is wrong.

Grahame Grieve (Dec 02 2020 at 20:02):

@Patrick Werner how to reproduce this?

Sarah Gaunt (Dec 02 2020 at 23:34):

Is this the same issue (this is a new error - it wasn't there yesterday)?:

Observation/observation-postpartum-status-eve-everywoman: Observation.value.ofType(CodeableConcept) (l132/c27)  warning [Unable to determine whether the provided codes are in the value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.87 because the value set or code system is not known to the validator]
Observation/observation-postpartum-status-eve-everywoman: Observation.value.ofType(CodeableConcept) (l132/c27)  error   This version of SNOMED is not loaded (from http://tx.fhir.org/r4)

        <coding>
            <system value="http://snomed.info/sct"/>
            <code value="42814007"/>
            <display value="Mid postpartum state (finding)"/>
        </coding>

https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.11.20.9.87/expansion/Latest

https://browser.ihtsdotools.org/?perspective=full&conceptId1=10152009&edition=MAIN/2020-07-31&release=&languages=en

Sarah Gaunt (Dec 03 2020 at 01:04):

I see that the vsac package lists the snomed version for that value set as US (none of the codes are us specific, so I have no clue why it's doing that). "version": "http://snomed.info/sct/731000124108/version/2020-03",
Will try pointing to US snomed and see if that fixes it.

Grahame Grieve (Dec 03 2020 at 01:09):

this is in case reporting?

Sarah Gaunt (Dec 03 2020 at 01:23):

Yes

Sarah Gaunt (Dec 03 2020 at 01:24):

Just pushed the change to make it point to USA Snomed

Sarah Gaunt (Dec 03 2020 at 01:36):

Woohoo! That fixed it. No idea why it all of a sudden decided to error but...

Grahame Grieve (Dec 03 2020 at 01:42):

great

Patrick Werner (Dec 03 2020 at 10:38):

Grahame Grieve said:

Patrick Werner how to reproduce this?

Checkout: git@github.com:HL7/genomics-reporting.git
./genonce.sh

Grahame Grieve (Dec 03 2020 at 22:07):

ok fixed shortly - by upgrading tx.fhir.org. You'll have to rebuild the tx-cache

Jean Duteau (Dec 07 2020 at 17:19):

Appears to be down again?

Connect to Terminology Server at http://tx.fhir.org                              (00:13.0907)
Publishing Content Failed: Unable to connect to terminology server. Error = An error fetching the server's capability statement: timeout (00:31.0548)

@Grahame Grieve @Rob Hausam anyone?

Rob Hausam (Dec 07 2020 at 17:22):

I'll check.

Rob Hausam (Dec 07 2020 at 17:24):

It seems to be up. Try again?

Jean Duteau (Dec 07 2020 at 17:50):

thanks it is working now

Jean Duteau (Dec 07 2020 at 18:19):

and now it's not...

Grahame Grieve (Dec 07 2020 at 19:55):

it's still running fine, so it seems as though you have a connection problem

Jean Duteau (Dec 07 2020 at 19:55):

yeah, connection to it has been touch and go all day

Sarah Gaunt (Dec 07 2020 at 21:02):

Does seem to be down.

Grahame Grieve (Dec 07 2020 at 21:03):

what do you get if you go to tx.fhir.org/r4 in your browser?

Jean Duteau (Dec 07 2020 at 21:04):

i get a timeout - ah, spoke too soon, it immediately refreshed and I get a web page returned. so it might be taking too long to return?

Sarah Gaunt (Dec 07 2020 at 21:05):

It failed in the CI build not locally

Sarah Gaunt (Dec 07 2020 at 21:05):

http://build.fhir.org/ig/HL7/case-reporting/branches/master/failure/build.log

Sarah Gaunt (Dec 07 2020 at 21:06):

I got a time out:

Hmm. We’re having trouble finding that site.
We can’t connect to the server at tx.fhir.org.

Grahame Grieve (Dec 07 2020 at 21:06):

you will now ;-)

Grahame Grieve (Dec 07 2020 at 21:07):

it's coming back up - 2-3 minutes

David deRoode (Feb 02 2021 at 18:56):

capabilitystatement

Lloyd McKenzie (Feb 02 2021 at 19:21):

@David deRoode wrong stream?

David deRoode (Feb 02 2021 at 19:26):

Yes, actually wrong forum entirely- apologies, disregard.

Jose Costa Teixeira (May 10 2021 at 15:54):

Is the terminology server down?
https://downforeveryoneorjustme.com/tx.fhir.org

Lloyd McKenzie (May 10 2021 at 16:33):

@Rob Hausam @Mark Iantorno

Rob Hausam (May 10 2021 at 16:35):

Yes, it seems so. I'll restart it.

Rob Hausam (May 10 2021 at 16:46):

@Jose Costa Teixeira It's up again now.

Jose Costa Teixeira (May 10 2021 at 17:35):

thanks

Corey Smith (Jun 02 2021 at 20:26):

hello. the terminology server seems to be down. can someone please confirm? thank you. @Monique van Berkum @Rob Hausam

Corey Spears (Jun 02 2021 at 20:33):

It seems to be down for the github IG Publisher build.

Corey Smith (Jun 02 2021 at 20:41):

Corey Spears said:

It seems to be down for the github IG Publisher build.

Thanks for confirming, Corey. We are hitting tx.fhir.org as part of a Trifolia IG build. I'm assuming that's the same tx server instance you are referring to.

Corey Spears (Jun 02 2021 at 20:57):

That is correct. Timeout error when trying to retrieve the CapabilityStatement from http://tx.fhir.org.

Rob Hausam (Jun 02 2021 at 20:58):

I'm restarting the service.

Rob Hausam (Jun 02 2021 at 21:05):

Should be working now.

Corey Spears (Jun 02 2021 at 21:13):

Confirmed. We are back up.

Lloyd McKenzie (Jun 02 2021 at 21:15):

@Grahame Grieve Do we have any idea what's bringing it down so often?

John Moehrke (Jun 02 2021 at 21:51):

many times it has been unresponsive today. Not clear it is fully down, as a build a few minutes later will succeed.

Grahame Grieve (Jun 02 2021 at 23:50):

not sure.

Last updated: Apr 12 2022 at 19:14 UTC