Package Details: puppetserver 7.7.0-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: 10
Popularity: 0.000000
First Submitted: 2014-09-26 19:48 (UTC)
Last Updated: 2022-05-17 19:34 (UTC)

Dependencies (7)

Required by (0)

Sources (3)

Pinned Comments

jsteel commented on 2015-11-02 14:12 (UTC)

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

lb.laboon commented on 2020-05-11 14:34 (UTC)

@scarleo What is your locale set to? You might need to switch to a UTF-8 based locale.

scarleo commented on 2020-05-11 10:13 (UTC) (edited on 2020-05-11 12:24 (UTC) by scarleo)

What is up with that filename? EDIT: Ok, I get it, it's a check by filename, classy stuff :). Well turns out I didn't have UTF-8 locale in /etc/locale.conf, it's installing now, case closed.

Fetching hocon-1.2.5.gem
ERROR:  While executing gem ... (Java::JavaNioFile::InvalidPathException)
    Malformed input or input contains unmappable characters: /home/oscar/.cache/pikaur/build/puppetserver/pkg/puppetserver/opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems/gems/hocon-1.2.5/spec/fixtures/test_utils/resources/ᚠᛇᚻ.conf
==> ERROR: A failure occurred in package().

Command 'makepkg --force' failed to execute.

lb.laboon commented on 2020-04-25 21:52 (UTC)

@julius.tzm Actually facter is not bundled with this package at all. The gemspec file that this package now installs is basically just a "shim" to trick ruby into thinking that the facter dependency is satisfied. I agree that it seems really janky, but this actually how Puppetserver gets packaged for the official releases (I copied the gemspec file directly from the official RHEL 8 rpm).

julius.tzm commented on 2020-04-25 20:30 (UTC)

@lb.laboon, yes it works, however I would keep the facter version in sync with the main repo, but that is just a fancy thing.

Many thanks!

lb.laboon commented on 2020-04-25 18:51 (UTC)

@julius.tzm This should be fixed in the latest version. Please try upgrading

julius.tzm commented on 2020-04-25 12:09 (UTC)

Hi @ll,

puppetserver ca setup (04-25 13:59)

Traceback (most recent call last): 2: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in <main>' 1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:inrequire' /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in require': cannot load such file -- puppetserver/ca/cli (LoadError) 8: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in<main>' 7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:in require' 6: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:161:inrescue in require' 5: from /usr/lib/ruby/2.7.0/rubygems.rb:209:in try_activate' 4: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:inactivate' 3: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in activate_dependencies' 2: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:ineach' 1: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in block in activate_dependencies' /usr/lib/ruby/2.7.0/rubygems/dependency.rb:311:into_specs': Could not find 'facter' (>= 2.0.1, < 4) among 58 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/root/.gem/ruby/2.7.0:/usr/lib/ruby/gems/2.7.0', execute gem env for more information 9: from /opt/puppetlabs/server/apps/puppetserver/cli/apps/ca:3:in <main>' 8: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:inrequire' 7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:161:in rescue in require' 6: from /usr/lib/ruby/2.7.0/rubygems.rb:208:intry_activate' 5: from /usr/lib/ruby/2.7.0/rubygems.rb:215:in rescue in try_activate' 4: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:inactivate' 3: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in activate_dependencies' 2: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:ineach' 1: from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in block in activate_dependencies' /usr/lib/ruby/2.7.0/rubygems/dependency.rb:311:into_specs': Could not find 'facter' (>= 2.0.1, < 4) among 58 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/root/.gem/ruby/2.7.0:/usr/lib/ruby/gems/2.7.0', execute gem env for more information

Does anybody has a clue how to solve this? After a fresh arch install, the facter 3.14.6-2 package is installed by default.

Thanks in advance!

devzero commented on 2019-03-22 19:40 (UTC)

@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 (UTC)

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 (UTC) (edited on 2019-03-22 08:10 (UTC) by devzero)

@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 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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.

beoldhin commented on 2018-07-03 12:21 (UTC)

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.

beoldhin commented on 2017-11-07 11:07 (UTC)

Problem solved. Updating gem gettext-setup to 0.28 fixed the error with translation_repositories.

beoldhin commented on 2017-11-06 20:49 (UTC)

Today I received the following updates: facter-3.9.2-1 hiera-3.4.2-1 puppet-5.3.2-1 After this I started to get the following error from server: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: undefined method `translation_repositories' for GettextSetup:Module on node Ideas?

beoldhin commented on 2016-12-28 15:18 (UTC)

"Not able to start puppetserver after reboot" was my error (/var/log on tmpfs). Puppetserver will hang without errors if it doesn't find its directory from /var/log. However being now a known issue this is now quite minor at least for me.

beoldhin commented on 2016-12-25 08:20 (UTC)

When installing puppetserver-2.7.2.tar.gz with "yaourt -S puppetserver": - Puppet server has to be reinstalled (yaourt -R puppetserver, yaourt -S puppetserver) every time puppetserver service is stopped by systemctl. - If the service is not reinstalled, java processes are trying to start but never finish (100% usage in every CPU core), if it is reinstalled, everything works fine - "WARNING: backup entry file not in package : etc/puppetlabs/puppetserver/bootstrap.cfg" - "Can't translate pathname 'opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems/gems/hocon-1.1.3/spec/fixtures/test_utils/resources/ᚠᛇᚻ.conf' to UTF-8" - "warning: directory permissions differ on /opt/puppetlabs/server/data/puppetserver/jruby-gems/ filesystem: 770 package: 755" Which one of these you think belong to Puppetlabs and which one to AUR maintainers?

beoldhin commented on 2016-12-24 07:25 (UTC)

It seems there are serious glitches when running this package. Do you think these belong to AUR maintainers or to Puppetlabs?

jsteel commented on 2016-07-28 11:23 (UTC)

I'm not using this any more, disowning

jsteel commented on 2016-03-03 13:11 (UTC)

Just had a bit of time to re-think your suggestion and test it. java-runtime-headless is now the dependency.

jsteel commented on 2016-02-24 15:58 (UTC)

Oh wait, there is one "xorg-xset". Well only "java-environment" is required, so you are free to pick what you want.

jsteel commented on 2016-02-24 15:51 (UTC)

It is assumed (well, documented on the wiki) that you have base and base-devel installed. Also I see no xorg packages pulled in with jdk8-openjdk.

simonsd commented on 2016-02-24 15:13 (UTC)

missing makedepends=("binutils" "fakeroot") Also, using jd8-openjdk-headless is enough, no need for all the xorg pkgs this way. I guess that's also what java-environment-fake is for.

jsteel commented on 2016-01-09 10:04 (UTC)

OK thanks, fixed.

nguillaumin commented on 2016-01-09 02:52 (UTC)

It seems the unit file is executable where it shouldn't be. I'm getting this warning in my journal after install: Jan 09 13:49:17 localhost systemd[1]: Configuration file /usr/lib/systemd/system/puppetserver.service is marked executable. Please remove executable permission bits. Proceeding anyway.

jsteel commented on 2015-11-02 14:12 (UTC)

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.

sebastianrakel commented on 2015-11-02 13:13 (UTC)

no, i didn't change anything after install

jsteel commented on 2015-11-02 12:49 (UTC)

I thought the default was /opt/puppetlabs or /var/lib/puppet and puppet has permissions there. Are you specifying a different directory in your config? Seems a bit strange to store that information in /etc/.

sebastianrakel commented on 2015-11-02 11:48 (UTC)

After install i wan't to start the service with systemctl start puppetserver and got: Permission denied - /etc/puppetlabs/puppet/ssl the service starts as user puppet, but the owner of /etc/puppetlabs is root and no write permissions for other groups/user.

timdiels commented on 2015-09-19 20:49 (UTC)

Thanks jsteel, I assumed the newest server would require the newest facter. So, I used facter instead of facter2, which gave me those errors. It indeed works with facter2.

jsteel commented on 2015-09-19 19:41 (UTC)

Just looking at your error a little closer "LoadError: no such file to load -- facter" have you got facter2 installed?

timdiels commented on 2015-09-19 18:33 (UTC)

Having issues with ruby gems it appears!topic/puppet-razor/Z_h3xffwapk

timdiels commented on 2015-09-19 18:17 (UTC)

puppet package requires facter, so shouldn't the facter2 dependency be changed to facter?