Unable to access Puppet Enterprise Console 2017.1.1.0

asked 2018-03-13 00:57:42 -0600

newcomer gravatar image

Hi Guys,

Need some assistance to understand why I am unable to get into PE console ?

+ puppetserver --version
puppetserver version: 2017.1.1.0
+ puppet --version
4.9.4
+ systemctl status puppet.service
● puppet.service - Puppet agent
   Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-03-13 10:32:44 AEDT; 6h ago
 Main PID: 965 (puppet)
   Memory: 189.7M
   CGroup: /system.slice/puppet.service
           └─965 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize

Mar 13 10:33:54 master.puppetlabs.vm puppet-agent[2609]: (/Stage[main]/Puppet_enterprise::Profile::Orchestrator/Service[pe-orchestration-services]) Skipping b...endencies
Mar 13 10:33:54 master.puppetlabs.vm puppet-agent[2609]: (/Stage[main]/Puppet_enterprise::Profile::Mcollective::Peadmin/Puppet_enterprise::Mcollective::Client[peadmin]...
Mar 13 10:33:54 master.puppetlabs.vm puppet-agent[2609]: (/Stage[main]/Puppet_enterprise::Profile::Mcollective::Peadmin/Puppet_enterprise::Mcollective::Client[peadmin]...
Mar 13 10:33:55 master.puppetlabs.vm puppet-agent[2609]: Applied catalog in 51.85 seconds
Mar 13 10:33:55 master.puppetlabs.vm puppet-agent[2609]: Could not send report: Connection refused - connect(2) for "master.puppetlabs.vm" port 8140
Mar 13 11:03:13 master.puppetlabs.vm puppet-agent[4675]: (Puppet::Type::Package::ProviderYum) Could not check for updates, '/usr/bin/yum check-update' exited with 1
Mar 13 11:03:23 master.puppetlabs.vm puppet-agent[4675]: Applied catalog in 11.35 seconds
Mar 13 16:29:17 master.puppetlabs.vm puppet-agent[5470]: (Puppet::Type::Package::ProviderYum) Could not check for updates, '/usr/bin/yum check-update' exited with 1
Mar 13 16:29:19 master.puppetlabs.vm crontab[5744]: (root) LIST (root)
Mar 13 16:29:25 master.puppetlabs.vm puppet-agent[5470]: Applied catalog in 9.90 seconds
Hint: Some lines were ellipsized, use -l to show in full.
+ systemctl status pe-puppetserver.service
● pe-puppetserver.service - pe-puppetserver Service
   Loaded: loaded (/usr/lib/systemd/system/pe-puppetserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-03-13 10:33:59 AEDT; 6h ago
  Process: 972 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
 Main PID: 1572 (java)
   Memory: 1.3G
   CGroup: /system.slice/pe-puppetserver.service
           └─1572 /opt/puppetlabs/server/bin/java -Xms2048m -Xmx2048m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /opt/puppetlabs/server/app...

Mar 13 10:32:44 master.puppetlabs.vm systemd[1]: Starting pe-puppetserver Service...
Mar 13 10:33:59 master.puppetlabs.vm systemd[1]: Started pe-puppetserver Service.

Further logs as below:

+ wget https://master.puppetlabs.vm/
--2018-03-13 16:53:39--  https://master.puppetlabs.vm/
Resolving master.puppetlabs.vm (master.puppetlabs.vm)... 127.0.0.1, 192.168.1.51
Connecting to master.puppetlabs.vm (master.puppetlabs.vm)|127.0.0.1|:443... connected.
ERROR: cannot verify master.puppetlabs.vm's certificate, issued by ‘/CN=Puppet Enterprise CA generated on master.puppetlabs.vm at +2017-04-06 19:13:07 -0700’:
  Unable to locally verify the issuer's authority.
To connect to master.puppetlabs.vm insecurely, use `--no-check-certificate'.
+ wget https://master.puppetlabs.vm/ --no-check-certificate
--2018-03-13 16:53 ...
(more)
edit retag flag offensive close merge delete

Comments

Have you tried visiting your master's IP address in a web browser with https? Everything in those logs looks fine. Also, from your agent or wherever you're working from, can you resolve master.puppetlabs.vm correctly? What happens when you try to ping that?

natemccurdy gravatar imagenatemccurdy ( 2018-03-14 03:11:27 -0600 )edit