I’ve noticed the healthcheck is quite slow, it’s not specific for the 2019.1.7 version though.
What I see in the log is typically two incidents for each type access for each server ex:
2019-02-18 16:19:26.5499 4932 13 INFO https://:10933/ 13 Secure connection established. Server at [::ffff:.24]:10933 identified by thumbprint: xx, using protocol Tls12
2019-02-18 16:19:26.5499 4932 13 INFO https://:10933/ 13 Secure connection established. Server at [::ffff:.24]:10933 identified by thumbprint: xx, using protocol Tls12
2019-02-18 16:19:26.5499 4932 15 INFO https://:10933/ 15 Secure connection established. Server at [::ffff:.31]:10933 identified by thumbprint: xx, using protocol Tls12
2019-02-18 16:19:26.5499 4932 15 INFO https://:10933/ 15 Secure connection established. Server at [::ffff:.31]:10933 identified by thumbprint: xx, using protocol Tls12
Is the double reports intended? Why does the server need to do an operation twice per client?
Especially the connection seem to be a rather expensive operation.
Thanks for getting in touch! I’m sorry to hear you’re hitting these slow health checks. I’m currently unable to determine the exact reason for this behavior - would you be willing to provide that full log to provide some additional context?
Are you using a custom script in the machine policy this server is using, and if so are you willing to provide it?
Are you experiencing any slowness executing deployments to this server?
I look forward to hearing back and getting to the bottom of this one!
Thanks for following up and providing that additional information. I apologize about not providing a secure location to upload your logs. You can either mark this thread as a private message, or email them to us at support at octopus dot com and I’ll pick it up from there.
I look forward to hearing back and looking more in depth at what’s causing this.