vchepkov
10/11/2023, 3:01 PMJan Fickler
10/11/2023, 3:02 PMCVQuesty
10/11/2023, 3:02 PMvchepkov
10/11/2023, 3:03 PMvchepkov
10/11/2023, 3:03 PMvchepkov
10/11/2023, 3:03 PMJan Fickler
10/11/2023, 3:03 PMrusty
10/11/2023, 3:21 PMJan Fickler
10/11/2023, 3:22 PMrusty
10/11/2023, 3:28 PMchadh
10/11/2023, 3:39 PMMichael Hashizume
10/11/2023, 3:53 PMJan Fickler
10/11/2023, 3:54 PMMichael Hashizume
10/11/2023, 4:01 PMrheign07
10/11/2023, 7:05 PMGood day, i just want to ask if pupperserver 7.x is working on Amazon Linux 2023?
Adam Retter
10/11/2023, 7:35 PMpuppet-agent[22789]: (Exec[letsencrypt certonly <http://www.catalogue.nationalarchives.gov.uk|www.catalogue.nationalarchives.gov.uk>] => Letsencrypt::Certonly[<http://www.catalogue.nationalarchives.gov.uk|www.catalogue.nationalarchives.gov.uk>] => Class[Letsencrypt] => Class[Letsencrypt::Plugin::Nginx] => Package[python3-certbot-nginx] => Class[Letsencrypt::Plugin::Nginx] => Letsencrypt::Certonly[<http://www.catalogue.nationalarchives.gov.uk|www.catalogue.nationalarchives.gov.uk>] => Exec[letsencrypt certonly <http://www.catalogue.nationalarchives.gov.uk|www.catalogue.nationalarchives.gov.uk>])
However, I have now updated the config to remove the cycle, but the Agent doesn’t seem to see the new config from the Server even when I restart it - any ideas?Jan Fickler
10/11/2023, 7:44 PMAdam Retter
10/11/2023, 7:51 PMsudo /opt/puppetlabs/bin/r10k deploy environment production -pv
INFO -> Deploying environment /etc/puppetlabs/code/environments/production
INFO -> Environment production is now at e14d34b3250d62b0ed7607a5607845357f38c5ab
...
You can see in revision `e14d34b3`… that I have commented out the letsencrypt
aspect here:
https://github.com/nationalarchives/ctd-omega-puppet/commit/e14d34b3250d62b0ed7607a5607845357f38c5ab
So I can’t understand where the cycle which involves letsencrypt is coming from as I have removed that from my config.
Are there caches somewhere that I need to clear?Adam Retter
10/11/2023, 8:21 PMrm -rf /opt/puppetlabs/puppet/cache/*
before restarting it seems to have solved the problem… Seems a bit worrying to me!nate
10/11/2023, 8:38 PMDebug: Resolving service 'fileserver' using Puppet::HTTP::Resolver::SRV
Debug: Searching for SRV records for domain: <http://domain.edu|domain.edu>
Debug: Found 0 SRV records for: <http://_x-puppet-fileserver._tcp.domain.edu|_x-puppet-fileserver._tcp.domain.edu>
we don’t have a SRV record added to dns for _x-puppet-fileserver
, but it hasn’t caused failures before. the agent version is 7.26.0 on rocky 8.7. is this SRV record a recent addition? i didn’t see it in docs, which is why we don’t have it in dns. we’re trying to determine if this issue is some weird networking issue on our side or what. when popping into puppet’s embedded ruby via irb
, the host also can’t resolve SRV records but can resolve regular A records and such. any ideas?josh
10/11/2023, 9:54 PMfileserver
specific SRV lookupMike Weilgart
10/11/2023, 10:00 PMMike Weilgart
10/11/2023, 10:01 PMbastelfreak
10/11/2023, 10:01 PMbastelfreak
10/11/2023, 10:01 PMMike Weilgart
10/11/2023, 10:02 PMbastelfreak
10/11/2023, 10:02 PMbastelfreak
10/11/2023, 10:02 PMbastelfreak
10/11/2023, 10:02 PMvchepkov
10/11/2023, 10:02 PM