Puppet Community

okay thanks, can you recommend any module as referance from github or forge? I would like to follow good example

so on debian 10 ruby version is 2.5 <https://packages.debian.org/buster/ruby>

`Error 500 on SERVER` behavior depends on the _JRuby version_ that `puppetserver` is using. CRuby doesn’t have any influence there.

you can check the used jruby from your puppetserver like this:
```root@puppet ~ # puppetserver ruby --version
jruby 9.2.17.0 (2.5.8) 2021-03-29 84d363da97 OpenJDK 64-Bit Server VM 11.0.14.1+1-LTS on 11.0.14.1+1-LTS +jit [linux-x86_64]
root@puppet ~ #```

indeed. Thanks for the feedback :
```jruby 1.7.27```

but in this case this is not a debian package right ?

I guess you're using the puppetserver package from <http://apt.puppet.com|apt.puppet.com>

puppetserver:
  Installé : 5.3.16-1stretch

if that's actually a stretch box then it's really old

however, it has an option to switch to a newer jruby

<https://puppet.com/docs/puppetserver/5.3/configuration.html#enabling-jruby-9k>

however you should consider updating that server

The server is currently running buster (debian 10) it was debian 9 when first deployed

ah I think Puppetlabs never packaged puppetserver 5 for Debian 10

inplace upgrade to puppet 6 and 7 should be relative smooth

that is my main concern, I've never done a puppetserver upgrade, hence I don't know what I could face off. Like production incident ? I mean if the worst case scenario is the agent not compiling anymore I can deal with that until I found a fix. But I fear that upgrade might cuase configuratiion change I wouldn't notive this would be very bad

do you run foreman or similar to view reports? and how critical/big is the environment? there are tools to simulate such an upgrade, but implementing that takes some effort

my environment is currently 479 VM windows &amp; linux

ah that's not too much. do you have access to all boxes?
• disable puppet agent everywhere
• Upgrade puppetserver/puppetdb
• Upgrade puppet agent, run it in -noop, check for changes, run without --noop if no changes

I've got a module (on disk) in my modulepath, but it isn't showing up via "puppet module list".

Any ideas for finding out why "puppet module list" doesn't see it?

Do other modules in your modulepath show up via `puppet module list`?

Also, please share some output with us, or an error message or lack thereof, so we can better understand what exactly you’re seeing.
And what is your modulepath, and how do you know you have a module in it? What did you do to verify that?

root@puppet-5-5:~# puppet config print modulepath
/etc/puppet/code/environments/production/modules:/etc/puppet/code/environments/production/profiles:/etc/puppet/code/environments/production/roles:/etc/puppet/modules:/etc/puppet/profiles:/etc/puppet/roles:/usr/share/puppet/modules

the last directory in the modulepath is the one of concern...

root@puppet-5-5:~# ls -1 /usr/share/puppet/modules
apt
concat
hiera_mysql
hiera-mysql2
mysql
postgresql
staging
stdlib
translate
vcsrepo

The hiera-mysql2 does not show up in "puppet module list":

That’s an invalid name for a Puppet module. It can’t have `-` in it.

thanks for the hint. I've spent a lot of time trying to figure it out.

For reference: <https://puppet.com/docs/puppet/7/lang_reserved.html#module-names>

and $modulename often contains _, but - isn't allowed, because that's already used to distinguish $owner and $modulename

The module name (as referenced in `metadata.json`) will typically contain the author name and the module name (e.g. `puppetlabs-stdlib`).
But on disk, the folder name must not have the author name… it can only be the module name according to the rules I linked above.

See the `puppetlabs-stdlib` module at <https://forge.puppet.com/puppetlabs/stdlib?src=slack&amp;channel=puppet>

I think <https://github.com/rnelson0/puppet-generate-puppetfile/tree/master> supports that

generate-puppetfile: --fixtures-only -p Puppetfile :slightly_smiling_face:

:kermit_typing: _:teacher:PE Console_ is about to start up in <#CFD8Z9A4T|>