Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't appear to work with PE 3.7.0 #34

Closed
unxmaal opened this issue Dec 10, 2014 · 3 comments
Closed

Doesn't appear to work with PE 3.7.0 #34

unxmaal opened this issue Dec 10, 2014 · 3 comments

Comments

@unxmaal
Copy link

unxmaal commented Dec 10, 2014

Attempted to use oscar to provision latest PE, 3.7.0.

Provisioning failed.

==> master: Configuring proxy environment variables...
==> master: Configuring proxy for Yum...
==> master: Running provisioner: hosts...
==> master: Running provisioner: hosts...
==> master: Running provisioner: pe_bootstrap...
==> master: Puppet Enterprise is already installed, skipping installation.
==> master: Applying post-install configuration to Puppet Enterprise.
==> master: Notice: Compiled catalog for master in environment production in 0.19 seconds
==> master:
==> master: Error: Could not start Service[pe-httpd]: Execution of '/sbin/service pe-httpd start' returned 1: Starting pe-httpd: pe-httpd.worker: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3 for ServerName
==> master: no listening sockets available, shutting down
==> master: Unable to open logs
==> master: [FAILED]
==> master: Wrapped exception:
==> master: Execution of '/sbin/service pe-httpd start' returned 1: Starting pe-httpd: pe-httpd.worker: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3 for ServerName
==> master: no listening sockets available, shutting down
==> master: Unable to open logs
==> master: [FAILED]
==> master: Error: /Stage[main]/Main/Service[pe-httpd]/ensure: change from stopped to running failed: Could not start Service[pe-httpd]: Execution of '/sbin/service pe-httpd start' returned 1: Starting pe-httpd: pe-httpd.worker: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3 for ServerName
==> master: no listening sockets available, shutting down
==> master: Unable to open logs
==> master: [FAILED]
==> master: Notice: Finished catalog run in 2.21 seconds
==> master:

pe-httpd fails with the following error:

Starting pe-httpd: pe-httpd.worker: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3 for ServerName
no listening sockets available, shutting down

It seems that oscar should be starting [and looking for] pe-puppetserver, but I'm not certain.

@danieldreier
Copy link

for what it's worth, I was able to bring up a 3.7.2 master under Debian 7 exactly as expected; only change I had to make from stock defaults was to bump up the memory on the master, since 3.7 requires 4+ gb out of the box.

@pckls
Copy link

pckls commented Feb 13, 2015

I also had to bump up memory to 4GB using PE 3.7.2 and Ubuntu 14.04.

@Sharpie
Copy link
Member

Sharpie commented Sep 18, 2015

This issue occurs when the VM has no FQDN set. FQDNs can be supplied via the Vagrant hostname setting or a DNS service. However this is configured, PE components expect hostname -f to resolve to a FQDN in order to correctly set up networked services.

@Sharpie Sharpie closed this as completed Sep 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants