Stream: IG creation
Topic: Unable to solve the error Error sending Http Request
Lakshmi Thrivarna (Apr 02 2018 at 04:46):
Hi All,
I am getting the read time out error while publishing the IG . Please help me to resolve this issue
1234.png
Thank You.
Lloyd McKenzie (Apr 02 2018 at 04:50):
We're having issues with the stability of the terminology server right now. Working to get it better, but at the moment all attention is on getting the ballot out. You can force the build to run by passing "-tx n/a" as an argument to the igpublisher. It means you won't get proper terminology validation or get value sets properly expanded, but at least it'll let you build.
Lakshmi Thrivarna (Apr 02 2018 at 04:51):
@Lloyd McKenzie Thank You
Rob Hausam (Apr 02 2018 at 04:52):
yes, that helps - thanks
Eric Haas (Apr 02 2018 at 19:48):
another reason I use "-tx n/a" (actually "-tx N/A" works too) is to speed up the build. shaves off a few seconds.
Eric Haas (Apr 02 2018 at 19:49):
... for those cases when -watch option doesn't apply
Satyaki Bhargava (Apr 04 2018 at 15:34):
I am getting another error when I ran the command using "-tx n/a":
C:\Users\320008152\Downloads\igpub>java -jar org.hl7.fhir.igpublisher.jar -ig ig.json -tx n/a
FHIR Implementation Guide Publisher (3.0.1-11916) @ Wednesday, April 4, 2018, 7:31:20 PM
Detected Java version: 9.0.4 from C:\Program Files\Java\jre-9.0.4 on amd64 (64bit). 2020MB available
Load Configuration from C:\Users\320008152\Downloads\igpub\ig.json (00.0000sec)
File log: C:\Users\320008~1\AppData\Local\Temp\fhir-ig-publisher-tmp.log
Root directory: C:\Users\320008152\Downloads\igpub (00.0066sec)
Terminology Cache is at C:\Users\320008152\fhircache. 1 files in cache (00.0088sec)
Load Validation Pack (internal) (00.0092sec)
Definitions 3.0.1-11917 (12.0594sec)
Connect to Terminology Server at n/a (12.0599sec)
WARNING: Running without terminology server - terminology content will likely not publish correctly (12.0608sec)
Initialization complete (13.0437sec)
Load Content (13.0445sec)
Processing Conformance Resources (13.0899sec)
Generating Narratives (13.0928sec)
Validating Resources (14.0063sec)
Generating Outputs in C:\Users\320008152\Downloads\igpub\output (14.0337sec)
Generating Summary Outputs (14.0470sec)
Jekyll: 'jekyll' is not recognized as an internal or external command, (14.0711sec)
Jekyll: operable program or batch file. (14.0714sec)
Complete output from Jekyll: operable program or batch file.
internal or external command,
(14.0718sec)
Publishing Content Failed: Process exited with an error: 1 (Exit value: 1) (14.0723sec)
(14.0727sec)
Use -? to get command line help (14.0729sec)
(14.0736sec)
Stack Dump (for debugging): (14.0741sec)
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153)
at org.hl7.fhir.igtools.publisher.Publisher.runJekyll(Publisher.java:2305)
at org.hl7.fhir.igtools.publisher.Publisher.runTool(Publisher.java:2229)
at org.hl7.fhir.igtools.publisher.Publisher.generate(Publisher.java:1977)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:316)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:3589)
Lloyd McKenzie (Apr 04 2018 at 15:37):
Answered the question in another thread. (And a reminder that issues should only be raised in one thread at a time. Don't post to a different thread unless someone suggests that you should or you haven't received any responses for a day or two :))
Satyaki Bhargava (Apr 04 2018 at 15:42):
Answered the question in another thread. (And a reminder that issues should only be raised in one thread at a time. Don't post to a different thread unless someone suggests that you should or you haven't received any responses for a day or two :))
I am really sorry, I am new to Zulip group, initially I posted my query in implementers stream, then I came to know that there is separate IG Creation stream. My apologies for duplicity.
Lloyd McKenzie (Apr 04 2018 at 17:25):
No worries. It's not critical, just a best practice.
Last updated: Apr 12 2022 at 19:14 UTC
