Stream: tx.fhir.org/notification
Topic: Prod Tx Server: FHIRServer - 7/15/2021 12:44:37 PM
Terminology Service Monitor Bot (Jul 15 2021 at 12:44):
7/15/2021 12:44:37 PM: Initializing the monitor service, service name: FHIRServer.
Terminology Service Monitor Bot (Jul 15 2021 at 12:45):
7/15/2021 12:45:10 PM: Waiting on service (FHIRServer) after start...
Terminology Service Monitor Bot (Jul 15 2021 at 12:51):
7/15/2021 12:51:37 PM: Service is up!
Terminology Service Monitor Bot (Jul 19 2021 at 19:55):
7/19/2021 7:55:18 PM: Issued stop request, service: FHIRServer
Terminology Service Monitor Bot (Jul 19 2021 at 19:55):
7/19/2021 7:55:18 PM: Service is down! Will restart...
Terminology Service Monitor Bot (Jul 19 2021 at 19:55):
7/19/2021 7:55:47 PM: Waiting on service (FHIRServer) after start...
Terminology Service Monitor Bot (Jul 19 2021 at 19:56):
7/19/2021 7:56:07 PM: Issued stop request, service: FHIRServer
Terminology Service Monitor Bot (Jul 19 2021 at 19:56):
7/19/2021 7:56:17 PM: Waiting on service (FHIRServer) after start...
Terminology Service Monitor Bot (Jul 19 2021 at 19:56):
7/19/2021 7:56:37 PM: Issued stop request, service: FHIRServer
Terminology Service Monitor Bot (Jul 19 2021 at 19:56):
7/19/2021 7:56:47 PM: Waiting on service (FHIRServer) after start...
Terminology Service Monitor Bot (Jul 19 2021 at 19:57):
7/19/2021 7:57:07 PM: Issued stop request, service: FHIRServer
Josh Mandel (Jul 19 2021 at 19:59):
Yikes!
Gino Canessa (Jul 19 2021 at 20:57):
Josh Mandel said:
Yikes!
Yeah, I think I figured out on the other thread. Sequence is: Issue Service Start -> Starting -> Tx Service Reports failure to start, but start is actually pending -> repeat until it's been long enough that the service is actually up and running.
Annoying, but straightforward enough to work around.
Gino Canessa (Jul 19 2021 at 21:06):
:face_palm: Actually simpler than that... poor wording in the notification message. The Message "Issued stop request" was just the message in from the service is in the "Stop Pending" state. The two messages alternated because one represents the service state (stop pending) and the other represents the http check state (waiting for a success before enabling). Will fix to reduce noise and update.
Last updated: Apr 12 2022 at 19:14 UTC
