Hey all. When using Puppet compilers, is there a specific http health check that will return if health for port 8142? https://puppet.com/docs/pe/2019.8/installing_compilers.html says to use

/status/v1/simple/

, but that path returns a 404 for me. Port 8140 works fine for this path perfectly fine.

Hey all. When using Puppet compilers, is there a specific http health check that will return if health for port 8142? https://puppet.com/docs/pe/2019.8/installing_compilers.html says to use

/status/v1/simple/

, but that path returns a 404 for me. Port 8140 works fine for this path perfectly fine. Trying to set up an AWS load balancer and cant find the right health check to use for this. I'd prefer an HTTP check, but if I have to resort to TCP, that would work - I just can't use round robin / random load balancing as mentioned in the docs since AWS doesnt seem to have that for network load balancers

Hey all. When using Puppet compilers, is there a specific http health check that will return if health for port 8142? https://puppet.com/docs/pe/2019.8/installing_compilers.html says to use

/status/v1/simple/

, but that path returns a 404 for me. Port 8140 works fine for this path perfectly fine. Trying to set up an AWS load balancer and cant find the right health check to use for this. I'd prefer an HTTP check, but if I have to resort to TCP, that would work - I just can't use round robin / random load balancing as mentioned in the docs since AWS doesnt seem to have those options for network load balancers

Hey all. When using Puppet compilers, is there a specific http health check that will return 200 if health is for port 8142? https://puppet.com/docs/pe/2019.8/installing_compilers.html says to use

/status/v1/simple/

, but that path returns a 404 for me. Port 8140 works fine for this path perfectly fine. Trying to set up an AWS load balancer and cant find the right health check to use for this. I'd prefer an HTTP check, but if I have to resort to TCP, that would work - I just can't use round robin / random load balancing as mentioned in the docs since AWS doesnt seem to have those options for network load balancers

message has been deleted

message has been deleted

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

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

thanks. Yeah that path doesnt seem to work on the compilers at least on 8142. The primary server, sure.

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

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

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

This message was deleted.

This message was deleted.

I am following this documentation on how to configure compilers

<https://puppet.com/docs/pe/2019.8/installing_compilers.html>

and I have configured

pe_repo::compile_master_pool_address

in the console using the compiler's FQDN. I run puppet on the primary server and compiler (didn't see any changes processed). When I try to install puppet agent on a server, in the

puppet.conf

it points it to the primary server instead of the compiler. I'm I missing anything or what I need to check to resolve this issue?

I am following this documentation on how to configure compilers

<https://puppet.com/docs/pe/2019.8/installing_compilers.html>

and I have configured

pe_repo::compile_master_pool_address

in the console using the compiler's FQDN. I run puppet on the primary server and compiler (didn't see any changes processed). When I try to install puppet agent on a server, in the

puppet.conf

it points it to the primary server instead of the compiler. I'm I missing anything or what I need to check to resolve this issue?

I think that only changes your puppet install script, next time you install something you will see the change

Yeah, when I try to run the script to install an agent, it still points it to the primary server and not the compiler

and that change applied to what group?

is compiler part of it?

What do mean?

you said

configured in the console

some particular node group, I assume

This message was deleted.

This message was deleted.

I've used haproxy in tcp passthrough mode (no ssl termination or proxy) in the past. IIRC we did leastconn to the backend servers. Connections are long lived so tendency of traffic clump after server side restarts. further haproxy notes. • Send logs to /dev/log instead of that local0 nonsense. You'll need to add the socket via this in rsyslog ``$AddUnixListenSocket /var/lib/haproxy/dev/log`` • enable seamless reloads. watchdog of 3-600s should be fine. • haproxy::listen won't work. Use haproxy::frontend and haproxy::backend

Hey all, Im trying to decom a compiler, its been unpinned from pe_compiler and pe_master and is not in that list but those are still showing up in the nodes details groups tab

how do I decom a compiler?

it would be real nice if there was a

puppet infrustructure forget compiler

command but I guess thats only for replicase

it would be real nice if there was a

puppet infrustructure forget compiler

command but I guess thats only for replicase