Description
The customer reports that starting the services in the following order causes 503 errors because the pe-puppetserver service is trying to launch pe-puppet-dashboard-workers. As follows:
pe-console-services
pe-puppetdb
pe-puppetserver
pe-activemq
pe-mcollective
pe-memcached
pe-postgresql
pe-httpd
pe-puppet-dashboard-workers
pe-puppet
I was not able to duplicate this specific behavior, but I was able to generate the 503 error in a different scenario. It may not be related... As follows:
With the PE Console running, stop the dashboard service. The console continues to run without problems. Stop and then start the console service. You get the 503 errors until you start the dashboard service.
Attachments
Issue Links
- relates to
-
ENTERPRISE-517 If pe-puppetserver starts before pe-puppet then it fails to start because /var/run/pe-puppet doesn't exist
-
- Resolved
-
-
EZ-32 Create vardir before service start on Debian systems
-
- Closed
-
-
SERVER-336 Puppetserver on EL7 or Ubuntu 14.04 does not always work after a reboot
-
- Closed
-
-
ENTERPRISE-502 pe-puppetserver and pe-console-services not starting after reboot on new PE install on Ubuntu 14.04
-
- Resolved
-
-
ENTERPRISE-483 PE PostgreSQL is started after services which depend on it on EL 6
-
- Closed
-