I’m struggling to deploy PE on AWS. I am using the recommended EC2 instance for the given version (t.xlarge, m.xlarge, etc) and I’ve tried a few previous releases as well. My issue is that check_status.sh always times out. Documentation suggests the PE configuration process should take ~8 minutes, yet after 18, it fails. The shell script is testing for the presence of a file which, as you see below, is never present.
[puppetadmin@ip-10-125-0-61 ~]$ test -f /var/run/puppetlabs/aws/pe-configured; echo $?
1
I know PE is not configured correctly because:
1. About 50% of the time, I cannot access the web interface. And sometimes when I do, I get a red screen saying puppetdb is unavailable.
2. I have never been able to register an agent, even with the most basic of settings.
I am not doing anything fancy with the AMI. The only modification I made was adding “permit icmp” to the security group for ping testing. PE is inside of a VPC and is bound to an elastic IP so reaching it isn’t the issue. It just isn’t self-configuring properly, or its taking a very long time and PE’s documentation is inaccurate.
I don’t want to continue messing with agent stuff until check_status.sh tells me things are working. I’ve tried (unsuccessful for about 8 hours so far) to get basic Linux boxes with agents to register, but I must assume that there is an issue with the initial installation. This is my sixth AMI deployment attempt. I initially tried multiple times on the newest version from May 2017, but rolled back to an April 2017 version for this attempt.
EDIT: Adding the error output for completeness.
[puppetadmin@ip-10-125-0-61 ~]$ /opt/puppetlabs/aws/bin/check_status.sh --wait
check_status.sh: Configuring Puppet Enterprise services..........................................................................................................................................................................................................................timeout
↧