This message was deleted.

You could perhaps talk to v1/inventory on the orchestration service (port 8143) on the primary to verify that the compilers are connected via PXP agent to the PCP broker on the primary

Yeah, but you cant check another servers status with an AWS health check. You can only check the instances in which you are load balancing

I thought that was the right path so you might submit a support ticket to check on the recommendation. I don’t see it in the puppetserver docs here: https://puppet.com/docs/puppet/7/server/http_api_index.html but I do see status/v1/services here https://puppet.com/docs/puppet/7/server/status-api/v1/services.html

thanks. Yeah that path doesnt seem to work on the compilers or the primary on 8142. only 8140 works

I have a note from long time ago

Master

Health check for port 8140: curl -k <https://localhost:8140/status/v1/simple>
Health check for port 8142: curl -k <https://localhost:8143/status/v1/simple>

Compiler

Health check for port 8140: curl -k <https://localhost:8140/status/v1/simple/master>
Health check for port 8142: curl -k <https://localhost:8140/status/v1/simple/pcp-broker>

@vchepkov did you know your healthcheck for the compiler on 8142 is curling port 8140?

I never tried to use it, it was in one of the slacks and I wrote it down 🙂

ah ok. Gotcha. Well thank you though

Wouldn’t the code for

puppet infra status

self-document the url?

I think those URLs require authentication

Yeah, I don’t have access to that code to check, though I contributed a few PRs in the past. But that’s where I would look.

likewise!

pecdm has the follow terraform https://github.com/puppetlabs/terraform-aws-pe_arch/blob/main/modules/loadbalancer/main.tf to set up its network load balancer with health check for compiler and just uses 8140 for both Also note https://puppet.com/docs/pe/2019.8/installing_compilers.html#how-compilers-work directts similar to do healthcheck to 8140 for both 8140 and 8142