Error using HL7v2 Agent for first time
# support
j
I'm sure it's something I'm not doing right, but I would appreciate some guidance. Using the medplum-agent on linux. MLLP port is listening fine, and I even see the Agent receive the HL7 data from the sender, but the HL7 sender gets "Response Timed Out" and the Agent log shows "{"level":"ERROR","timestamp":"2024-09-27T14:29:12.585Z","msg":"WebSocket error on incoming message: Transmit response missing callback"} ". The Bot works fine if I hit it via the API, so I feel like it's something in the Agent setup or maybe a firewall issue? Any help would be appreciated!
r
are all applications running on localhost?
Or agent in environment X and server in cloud?
j
agent in our company AWS Cloud, with another server in that "local" network sending to it. The server is on AWS, but it's own network.
so sending over WSS
r
got it So you need to make sure that websockets are enabled on your Project on server
second, on the host your agent is on, can you check that it can access the server? Perhaps curl api.servername.com/healthcheck for sanity
sometimes the domains are blocked via firewall or cannot access the internet
j
checking
web sockets were not enabled
I feel like connectivity is okay... since we see the connection and even the HL7 in the logs
do I need to do anything else, restart or anything?
r
shouldn't need to
j
"websocket-subscriptions" right?
r
I need to phone a friend 🙂 cc: @Derrick
yup
websocket-subscriptions is right
j
that and bots are all that are enabled. same message
r
does the HL7V2 protocol work?
j
if I hit it via the API, yes
r
k, I have reached my depths 🙂 Let's see if we can track it down
j
haha understood. if anyone would like access, please just let me know
no PHI on it
r
if you could screencast your setup and post that sometimes helps.
j
like a video?
r
yeah repro video
j
ok. I have a call in a few mins, I will after that
r
tyty
d
Hi @jackwhaines , what version of Medplum Server are you running just to start off? And what version of the Agent?
It sounds like it's possible that it could be related to this bug that was patched in `3.2.10`: https://www.medplum.com/docs/agent/features#major-bug-fixes
j
I saw that too and upgraded just to see... we're on 3.2.15-b06c52c04
Screen caps of setup.

https://youtu.be/wjvvwZi07EY▾

If I missed anything, let me know.
Sorry @Derrick Agent version is 3.2.16-a2ededb30
d
Awesome, this video is very helpful. Just to confirm you're on
3.2.15
on your Medplum server?
j
that's here right?
d
Yes I believe that version should be the same as on the Medplum server but let me make sure
j
it's entirely possible I'm missing something... I'm still very, very new to MedPlum. I also don't mind giving you access if it would help.
d
Ok 1 more thing to check for me, I think Reshma may have asked about this but this will prove what version of
medplum server
we're on, I'm realizing client could theoretically be on a higher version on the server and that version we're seeing in the profile dropdown is the client version Can you navigate to
api.<your_domain>/healthcheck
and see what it reports?
j
ah
Copy code
{
  "ok": true,
  "version": "3.2.8-b2b7ed8c5",
  "platform": "linux",
  "runtime": "v20.17.0",
  "postgres": true,
  "redis": true
}
3.2.8
d
Ah yeah I think a server upgrade will probably fix your issue then
j
so, it IS the bug from above.
d
Yep! Funny enough I found the bug with the exact same Mirth setup you were showing
j
okay, so we have the AWS install... can you tell me how (or point me to the doc) to upgrade it?
we actually thought we did
yea I actually found that bug and thought oh that's it. then we (thought) we upgraded and it still happened, so Ithought it must be somethign else
we followed the aws cdk install exactly
j
we're getting a deprecation warning... trying to resolve that
healthcheck now says 3.2.16 but it's not quite done yet
ok, so. did the upgrade, still didn't work UNTIL the websocket reconnected. Once it did, we're good now!!
d
Great! Glad it's working Let us know if you run into anything else 👍
j
I will... but will do my best not to abuse it.
Thanks again.
d
Anytime!
177 Views