Package Details: puppetserver 6.7.2-1

Git Clone URL: (read-only, click to copy)
Package Base: puppetserver
Description: Server automation framework and application
Upstream URL:
Licenses: Apache
Submitter: aboe
Maintainer: lb.laboon (bastelfreak)
Last Packager: lb.laboon
Votes: 9
Popularity: 0.002321
First Submitted: 2014-09-26 19:48
Last Updated: 2020-01-13 16:47

Pinned Comments

jsteel commented on 2015-11-02 14:12

OK yes it looks like the default for ssldir is now $confdir/ssl. I would change the ssldir location in your puppet.conf, or create and give permissions on that directory if that's where you want to have it.

Latest Comments

1 2 3 4 Next › Last »

devzero commented on 2019-03-22 19:40

@lb.laboon, thanks a lot, that did the trick. I'm still getting errors in the puppet client logs, but I think it's more of a misconfiguration issue rather than a problem with the package

lb.laboon commented on 2019-03-22 14:33

Hey @devzero, thanks for pointing that out! I use an external CA with my setup, so I hadn't noticed that was broken. I just updated the package so could you try updating? Let me know if that fixes the issue for you.

devzero commented on 2019-03-22 08:01

@lb.laboon Ah yes, I see, sorry about that. I was keyed on looking for /etc/puppetlabs/puppet, not "$confdir", so my brain deemed the pinned comment to be irrelevant :)

I did encounter another (unrelated) problem. Hopefully you can point me in the right direction again.

The puppetserver service starts without any problems, status looks good. Then I start puppet agent services on a couple of other boxes, using the standard Arch Linux puppet package. I now want to sign their certs.

On puppet master, I run sudo puppetserver ca list and get such errors:

/usr/sbin/puppetserver: /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca: /opt/puppetlabs/puppet/bin/ruby: bad interpreter: No such file or directory
/usr/sbin/puppetserver: line 80: /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca: Success

That path to /opt/puppetlabs/puppet/bin/ruby is hard-coded by /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca, but no ruby is installed in the stated location.

I tried patching that script to use the system installation of ruby, but this only produced more errors:

Traceback (most recent call last):
        2: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in `<main>'
        1: from /usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- puppetserver/ca/cli (LoadError)

lb.laboon commented on 2019-03-22 05:05

@devzero As per the pinned comment, you will need to chown the /etc/puppetlabs/puppet/ssl directory after installation of the puppetserver package so that the service can write to that directory. Unfortunately, we can't set the ownership of that directory as part of this package (i.e. in a post-install script) because the administrator might choose to use a different location for the ssldir.

devzero commented on 2019-03-22 04:51

@lb.laboon: Thanks for clarifying about the version.

After installing puppetserver package, I get this:

$ sudo systemctl start puppetserver.service
Job for puppetserver.service failed because the control process exited with error code.
See "systemctl status puppetserver.service" and "journalctl -xe" for details.

Then in sudo journalctl -xe I get quite a long ruby error, but the first line seems most relevant:

Mar 22 15:46:51 <hostname> puppetserver[14542]: RuntimeError: Got 1 failure(s) while initializing: File[/etc/puppetlabs/puppet/ssl]: change from 'absent' to 'directory' failed: Could not set 'directory' on ensure: Permission denied - /etc/puppetlabs/puppet/ssl

If I explicitly create /etc/puppetlabls/puppet/ssl first (using sudo mkdir /etc/puppetlabs/puppet/ssl), now there is an error because the puppetserver service can't set the permissions it likes:

Mar 22 15:51:16 <hostname> puppetserver[18665]: RuntimeError: Got 1 failure(s) while initializing: File[/etc/puppetlabs/puppet/ssl]: change from '0700' to '0771' failed: failed to set mode 0700' to '0771' failed: failed to set mode 0700 on /etc/puppetlabs/puppet/ssl: Operation not permitted - No message available

lb.laboon commented on 2019-03-22 04:32

@devzero: 6.2.1 is the latest puppetserver release (as of this writing). 6.3 is just for the puppet agent. Also, the puppetserver package does not supply any of the files under /etc/puppetlabs/puppet, so it cannot control the ownership of those files (those files are all provided by the puppet agent package from the official repos). What errors were you seeing?

devzero commented on 2019-03-22 04:18

Also, the service runs as puppet user, but needs to make modifications under /etc/puppetlabs/puppet such as creating a directory for certs. This caused an error for me. Running chown puppet /etc/puppetlabs/puppet fixes the problem

devzero commented on 2019-03-22 03:05

Hi, thanks for maintaining this package.

It looks like there should be a version bump to 6.3?!topic/puppet-dev/GsFlH9eu-6Y

lb.laboon commented on 2019-03-18 16:07

Since the previous maintainer has been MIA, I have taken over maintaining this package. Bumped the version to 6.2.1 and locked the JRE requirement to version 8.

FrozenGeek commented on 2019-03-17 11:05

hey, I bumped the version to 6.2.1 and fixed the puppetca command so it works out of the box with the puppet package from the community repo. Feel free to pull that into here.