Puppet Enterprise Installation Error on CentOS7

568 views
Skip to first unread message

Nikhil Rao

unread,
Dec 5, 2015, 11:58:58 AM12/5/15
to Puppet Users
I tried to install puppet enterprise from puppet master and while selecting monolithic installation and setting upto 500 nodes and setting up the DNS name and the alias name and encountered an error WARNING 1: set 2 CPU cores instead of 4 CPU cores WARNING 2: set at-least 100GB space in /Opt folder. And i ended up in the following error "Error: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details. Error: /Stage[main]/Puppetenterprise::Master::Puppetserver/Service[pe-puppetserver]/ensure: change from stopped to running failed: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details."

What should i change in my vmware settings???? Please advice



Martin Alfke

unread,
Dec 5, 2015, 12:24:23 PM12/5/15
to puppet...@googlegroups.com
Hi,

On 05 Dec 2015, at 04:16, Nikhil Rao <raoni...@gmail.com> wrote:

> I tried to install puppet enterprise from puppet master and while selecting monolithic installation and setting upto 500 nodes and setting up the DNS name and the alias name and encountered an error WARNING 1: set 2 CPU cores instead of 4 CPU cores WARNING 2: set at-least 100GB space in /Opt folder. And i ended up in the following error "Error: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details. Error: /Stage[main]/Puppetenterprise::Master::Puppetserver/Service[pe-puppetserver]/ensure: change from stopped to running failed: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details."
> What should i change in my vmware settings???? Please advice

Like the installer mentions: your PE Master should have 2-4 cores minimum.

First guess: RAM
PE has several java applications running:
- puppetserver
- puppetdb
- node classifier
A properly sized PE Master should have 6-8 GB RAM.

Second guess:
do you have selinux enabled?
Is a local firewall running?

You might want to check the PE puppet server log file (/var/log/puppetlabs/puppetserver/puppetserver.log)

Best,
Martin


>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d5eba3de-c3db-4b11-86db-62ba2c6cd3d7%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Nikhil Rao

unread,
Dec 5, 2015, 7:27:51 PM12/5/15
to Puppet Users


I have posted the log file and the error is as follows . But couldnt decode what the exact error is ... Please can you advice on what the issue is  exactly and i have changed the Cores and it didnt throw a warning. But still stuck at pe-puppetserver

 

Martin Alfke

unread,
Dec 7, 2015, 4:17:50 AM12/7/15
to puppet...@googlegroups.com
Hi Nikhil,

please paste the log file (/var/opt/puppetlabs/puppetserver/puppetserver.log) into gist (not a screenshot).
http://gist.github.com/

I assume that the error is at the end of the file.

Did you run the journalctl -xn command (like mentioned in the output)?
The error log snippet you have pasted indicates, that you can not reach official cents mirrors.
Has your VM access to the internet? Can you run ‘yum update’ successfully on the machine?

Best,
Martin


On 06 Dec 2015, at 00:27, Nikhil Rao <raoni...@gmail.com> wrote:

>
>
> On Saturday, 5 December 2015 11:58:58 UTC-5, Nikhil Rao wrote:
> I tried to install puppet enterprise from puppet master and while selecting monolithic installation and setting upto 500 nodes and setting up the DNS name and the alias name and encountered an error WARNING 1: set 2 CPU cores instead of 4 CPU cores WARNING 2: set at-least 100GB space in /Opt folder. And i ended up in the following error "Error: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details. Error: /Stage[main]/Puppetenterprise::Master::Puppetserver/Service[pe-puppetserver]/ensure: change from stopped to running failed: Could not start Service[pe-puppetserver]: Execution of '/bin/systemctl start pe-puppetserver' returned 1: Job for pe-puppetserver.service failed. See 'systemctl status pe-puppetserver.service' and 'journalctl -xn' for details."
> What should i change in my vmware settings???? Please advice
>
>
>
>
>
>
>
>
>
>
>
> I have posted the log file and the error is as follows . But couldnt decode what the exact error is ... Please can you advice on what the issue is exactly and i have changed the Cores and it didnt throw a warning. But still stuck at pe-puppetserver
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/649da43e-a615-41b6-bd35-bdf4e18d18f1%40googlegroups.com.

evan....@noaa.gov

unread,
Dec 10, 2015, 2:00:17 PM12/10/15
to Puppet Users
Rao-
  First thing you need to do is make your harddrive bigger. 10G is just not going to cut it. Second, looks like you have a network issue, so you probably need to fix that. I would just wipe the VM, start with new one that has working network, and atleast a configured to the puppet recommended minimums.
Reply all
Reply to author
Forward
0 new messages