Arch Linux User Repository

@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.

@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

@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?

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

Hi, thanks for maintaining this package.

It looks like there should be a version bump to 6.3? https://groups.google.com/forum/#!topic/puppet-dev/GsFlH9eu-6Y

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.

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. https://github.com/SimonPe/arch-puppetserver/compare/aur...master Feel free to pull that into here.

I tried some Java version tests today. I noticed that the following selection is available when installing puppetserver when no java is installed. Didn't notice this before when I had jdk8-openjdk package already installed:

" :: There are 4 providers available for java-runtime-headless: :: Repository extra 1) jre10-openjdk-headless 2) jre7-openjdk-headless 3) jre8-openjdk-headless 4) jre9-openjdk-headless

Enter a number (default=1): "

For me puppetserver starts only when I select 3 (jre8). Options 1 and 4 result in hanging startup of puppetserver (100% CPU usage, infinite loop?). I've not tried jre7. Just wanted to point this out as the default selection leads to inoperable system. Java 11 (LTS?) will be released soon but I'n not sure about the current status of LTS releases, however, are they still free or not.