https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • n
    hold up…. what operating system is this? And how are you installing the Puppet agent? These paths make me think it’s not the 
    puppet-agent
    package: /usr/lib/ruby/vendor_ruby
  • n
    hold up…. what operating system is this? And how are you installing the Puppet agent? These paths make me think it’s not the 
    puppet-agent
    package: /usr/lib/ruby/vendor_ruby
  • w
    The master or the node?
  • n
    The agent node… well, both actually.
  • w
    Master is Ubuntu as is the agent, although windows throws similar errors
  • w
    apt-get install puppet ?
  • w
    ah
  • n
    You should be using the official Puppet Inc. .deb packages then, from the Puppet Inc repo. Don’t use the default Ubuntu repos… it’ll save a lot of headache.
  • w
    looks like it's using a 5.5 repo
  • n
    Yeah… the default puppet package is really old. If this is a brand new install, I recommend starting with Puppet 7 for both the Puppetserver and all agents. https://puppet.com/docs/puppet/7/install_puppet.html#enable_the_puppet_platform_apt
  • w
    installed 7.19, trying with it
  • w
    server is latest
  • n
    Cool. So make sure you add the Puppet 7 repo for your version of Ubuntu, then install with 
    sudo apt-get install puppet-agent
    (not just 
    puppet
    ). You’ll want to remove whatever version you installed previously on that agent too.
  • n
    Cool. So make sure you add the Puppet 7 repo for your version of Ubuntu, then install with 
    sudo apt-get install puppet-agent
    (not just 
    puppet
    ). You’ll want to remove whatever version you installed previously on that agent too.
  • w
    yeah, I had previously added the repo but diddn't realize that it had installed an older version using the "puppet" package
  • w
    well, it got a little bit further which is progress.
    Copy code
    Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Failed to execute '/pdb/cmd/v1?checksum=88315732ecd420ea94396ba34612b842dfd0f418&version=5&certname=vmipam01.britanniahome.local&command=replace_facts&producer-timestamp=2022-10-04T21:59:46.103Z' on at least 1 of the following 'server_urls': <https://vmpuppetmaster01.britanniahome.net:8081>
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
  • n
    Yup. Progress! This looks like a problem between your Puppetserver and PuppetDB now. The puppetserver is trying to cache your agent’s facts into PuppetDB, but PuppetDB at 
    <https://vmpuppetmaster01.britanniahome.net:8081>
    isn’t responding.
  • n
    Yup. Progress! This looks like a problem between your Puppetserver and PuppetDB now. The puppetserver is trying to cache your agent’s facts into PuppetDB, but PuppetDB at 
    <https://vmpuppetmaster01.britanniahome.net:8081>
    isn’t responding.
  • n
    Backing up a bit here… Can your Puppetserver do a Puppet run against itself? From your Puppetserver, does 
    sudo puppet agent -t
    succeed?
  • w
    no, it fails on the master itself
    Copy code
    Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Failed to execute '/pdb/cmd/v1?checksum=dd739e2adf6343e9ab699d32bce52977de7ca692&version=5&certname=<http://vmpuppetmaster01.britanniahome.net|vmpuppetmaster01.britanniahome.net>&command=replace_facts&producer-timestamp=2022-10-04T22:23:20.172Z' on at least 1 of the following 'server_urls': <https://vmpuppetmaster01.britanniahome.net:8081>
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
  • w
    I did do the steps to refresh puppetdb mentioned in the cert guide.
  • w
    Copy code
    puppetdb ssl-setup
  • n
    Ok. That’s expected. Focus on fixing puppet runs on your master first. Then your agents should also work. Is the PuppetDB service running? What does this show 
    sudo puppet resource service puppetdb
  • s
    This message was deleted.
    n
    w
    • 3
    • 41
  • w
    tail
    Copy code
    2022-10-04T15:18:17.027-07:00 INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses
2022-10-04T15:18:17.141-07:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool: default - Shutdown initiated...
2022-10-04T15:18:17.273-07:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool: default - Shutdown completed.
2022-10-04T15:18:17.274-07:00 INFO  [c.z.h.HikariDataSource] PDBReadPool - Starting...
2022-10-04T15:18:17.280-07:00 INFO  [c.z.h.HikariDataSource] PDBReadPool - Start completed.
2022-10-04T15:18:17.946-07:00 INFO  [c.z.h.HikariDataSource] PDBWritePool - Starting...
2022-10-04T15:18:17.965-07:00 INFO  [c.z.h.HikariDataSource] PDBWritePool - Start completed.
2022-10-04T15:18:18.203-07:00 INFO  [p.p.dashboard] Redirecting / to the PuppetDB dashboard
2022-10-04T15:18:18.212-07:00 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@779e56d0{/,null,AVAILABLE}
2022-10-04T15:18:18.322-07:00 INFO  [p.p.pdb-routing] PuppetDB finished starting, disabling maintenance mode
  • w
    defaults,
    Copy code
    [main]
server_urls = <https://vmpuppetmaster01.britanniahome.net:8081/>
soft_write_failure = false
  • w
    it worked prior to regenerating the certs a short bit ago during troubleshooting.
  • w
    it worked locally on the master itself prior to regenerating the certs a short bit ago during troubleshooting.
  • n
    Copy code
    sudo puppet resource service puppetserver ensure=stopped
sudo puppet resource service puppetdb ensure=stopped
sudo rm /etc/puppetlabs/puppet/puppetdb.conf
sudo puppet config storeconfigs false --section master
sudo puppet resource package puppetdb ensure=absent
sudo puppet resource puppetserver ensure=running
  • w
    Applied without error on the master itself, shall I try another host now?
1...182183184...428Latest