Skip to main content

Puppet Server "Error Reported" and Orchestrator Service "Unreachable" in the console in Puppet Enterprise 2017.2 to 2019.x: Port 8143 blocked

Adrian Parreiras Horta
  • Updated

In Puppet Enterprise versions before PE 2017.2, port 8143 is used for communication between workstation clients and the master (now called the primary server). In PE 2017.2 and later, port 8143 is used to accept connections to PCP brokers from the orchestrator and compilers. When port 8143 is blocked on the primary server, you get errors in the console.

Note: Our terminology changed. A primary server used to be called a master or master of masters, a compiler used to be called a compile master.

Error messages

In the upper right of the console, when I click on Puppet Services status, there’s a red icon next to Puppet Server with the error message Error Reported and a red icon next to Orchestrator Service with the error message Unreachable.

Screenshot of console showing the error described above

 

Version and installation information

PE version: 2017.2, 2017.3, 2018.1, 2019.x
OS: Any
Installation type:
Monolithic with compilers (2017.2 to 2019.x)
Split with compilers (2017.2 to 2019.0)

Solution

Open port 8143.

On the primary server:

  1. Check that port 8143 is open: netstat -an | grep 8143 | grep LISTEN
  2. Check that port 8143 isn’t blocked by the firewall: iptables -L -vn | grep 8143
  3. Resolve any network issues blocking port 8143.

For more information, see the list of ports that need to be open.

If after trying this solution, you still have errors, please use the steps here to resolve the issue. 

Did this solve your problem?
0 out of 6 found this helpful

How can we improve this article?

3 comments

Date Votes
  • Jensen Ellard

    My ports are open! I encountered this after doing backup/restore to a new master host. Everything appeared working except Orchestrator unreachable like picture above. The following fixed it for me. The error in my /var/log/puppetlabs/orchestration-services/orchestration-services.log were very similar (if not identical) to the gist link below. 

    • Stop pe-orchestration-services
    • Stop pxp-agent
    • rm /etc/puppetlabs/orchestration-services/ssl/*
    • Start pe-orchestration-services
    • Start pxp-agent
    puppet resource service pe-orchestration-services ensure=stopped

    puppet resource service pxp-agent ensure=stopped

    rm /etc/puppetlabs/orchestration-services/ssl/*

    # Run Puppet to regenerate

    puppet agent -t --verbose

    puppet resource service pe-orchestration-services ensure=running

    puppet resource service pxp-agent ensure=running

     

    I actually got an error when doing this but I think it was just related to puppet having to regenerate the orchestrator's certs. After restarting those 2 services everything was working. I was chasing this issue forever.

    Thanks Jesse Reynolds! This was the only link I found that resolved it:

    https://gist.github.com/jessereynolds/5082b82216989d9e0bba7c1ca1828963

     

    0
  • Suzie Baunsgard
    • Edited

    Hi Jensen, I'm the writer that works with the team here, I'm going to work with someone to either get this incorporated into the article, or get a new article up to help other people who run into this. Thanks so much for your comment!

    0
  • Suzie Baunsgard

    Jensen, can you let me know your version of PE and OS? That'll help the engineer working with me get a handle on it. If you feel like that might be too much info in a comment, let me know that as well, and I can contact you via other methods. 

    0

Please sign in to leave a comment.

Related articles