The error comme when is loads the reports termini

just set

reports = puppetdb

and it should be fine

the puppetdb termini might need extra config to reach puppetdb if it is running on another node but this takes place in

puppet/puppetdb.conf

(note the

db

)

message has been deleted

OK, i rename all too puppetdb. i have a "new" error. maybe a certificate error.

2022-10-16T22:45:51.636+02:00 WARN  [qtp1161355795-58] [c.p.h.c.i.PersistentSyncHttpClient] Error executing http request
javax.net.ssl.SSLPeerUnverifiedException: Host name 'puppetdb' does not match the certificate subject provided by the peer (CN=testpuppetserver1)

|

2022-10-16T22:45:51.642+02:00 WARN  [qtp1161355795-58] [puppetserver] Puppet Error connecting to puppetdb on 8081 at route <https://puppetdb:8081/pdb/cmd/v1?checksum=fdd42975a3eb239a>
c62f82646f09ddfb424c6e96&version=8&certname=testpuppetserver1&command=store_report&producer-timestamp=2022-10-16T20:45:51.586Z, error message received was 'Error executing http requ
est'. Failing over to the next PuppetDB server_url in the 'server_urls' list

message has been deleted

This message was deleted.

what happens if you restart the service?

Hello, Any idea or suggestions on configuring puppet master on the cloudflare over a reverse proxy?

like if you wait 1.5* run_interval is it still running?

ill try and reproduce, thinking of possibilities out loud: Is it possible the User the daemon initially was running as , is different than the user you ran the --disable with, and the subsequent service restart?

try sudo

/opt/puppetlabs/puppet/bin/puppet agent --disable

what ever the user context of the daemon the lock would need to end up here: /opt/puppetlabs/puppet/cache/state/agent_disabled.lock

what ever the user context of the daemon the lock would need to end up here: /opt/puppetlabs/puppet/cache/state/agent_disabled.lock and not /home/user/.puppetlabs/opt/puppet/cache/state/agent_disabled.lock

if the user context of the daemon is root the lock would need to end up here: /opt/puppetlabs/puppet/cache/state/agent_disabled.lock and not /home/user/.puppetlabs/opt/puppet/cache/state/agent_disabled.lock

quick question. can I put templates in subfolders of the template folder? Like

templates/projectX/template.epp

and then call in the puppet code

epp('module/projectX/template.epp')

?

This message was deleted.

This message was deleted.

message has been deleted

message has been deleted

This message was deleted.

I'm looking for ideas on how to put a .bash_profile file resource in the $HOME directory of a user on Linux. /home/${user} will work most times but I do have some special-needs user accounts that have a home directory located elsewhere on the file system. I could write a custom fact that parses the /etc/passwd file but that would work only for existing users. My puppet manifest will create a new user in a non-standard home directory location and then the .bash_profile file needs to be managed. Any suggestions welcome.

I'm looking for ideas on how to put a .bash_profile file resource in the $HOME directory of a user on Linux. /home/${user} will work most times but I do have some special-needs user accounts that have a home directory located elsewhere on the file system. I could write a custom fact that parses the /etc/passwd file but that would work only for existing users. My puppet manifest will create a new user in a non-standard home directory location and then the .bash_profile file needs to be managed. Any suggestions welcome. I found this but I'm not yet sure how to implement it.

I'm looking for ideas on how to put a .bash_profile file resource in the $HOME directory of a user on Linux. /home/${user} will work most times but I do have some special-needs user accounts that have a home directory located elsewhere on the file system. I could write a custom fact that parses the /etc/passwd file but that would work only for existing users. My puppet manifest will create a new user in a non-standard home directory location and then the .bash_profile file needs to be managed. Any suggestions welcome. I found this but I'm not yet sure how to implement it.

I'm looking for ideas on how to put a .bash_profile file resource in the $HOME directory of a user on Linux. /home/${user} will work most times but I do have some special-needs user accounts that have a home directory located elsewhere on the file system. I could write a custom fact that parses the /etc/passwd file but that would work only for existing users. My puppet manifest will create a new user in a non-standard home directory location and then the .bash_profile file needs to be managed. Any suggestions welcome. I found this but I'm not yet sure how to implement it. I think a downside to the user_home_directory fact is that the user must exist at the time of compilation.

and

function mymodule::homedir(Hash $userdata) String {
  if $userdata['specialhome'] {
    $userdata['specialhome']
  else {
     "/home/${userdata['user']"
  }
}

and

function mymodule::homedir(Hash $userdata) String {
  if $userdata['specialhome'] {
    $userdata['specialhome']
  else {
     "/home/${userdata['user']}"
  }
}

but before you go writing your own, you should take a look at this and see how much of it is already covered. https://github.com/puppetlabs/puppetlabs-accounts/blob/main/manifests/user.pp

This message was deleted.