Puppet agent log shows error "could not back up"

0 votes
Aug 2, 2019 in Puppet by Amy
80 views

1 answer to this question.

0 votes

If agents log errors like "could not back up," nodes are likely attempting to back up files to the wrong hostname, it means that agents can't reach the filebucket server.

On the master, edit /etc/puppetlabs/code/environments/production/manifests/site.pp so that filebucket server attribute points to the correct hostname:

# Define filebucket 'main': 
filebucket { 'main': 
server => '<PUPPET_MASTER_DNS_NAME>', 
path => false, 
}

Changing the filebucket server attribute on the master fixes the error on all agent nodes.

answered Aug 2, 2019 by Sirajul
• 50,330 points

Related Questions In Puppet

0 votes
1 answer

Error saying "Error: Could not parse for environment production" - Puppet

Hey @Nagya, You need to set the ...READ MORE

answered Feb 15, 2019 in Puppet by Kavya
269 views
0 votes
1 answer

Error saying "Error: Could not autoload puppet/provider/package/rpm: No child processes." While installing gcc through puppet

Hey @Laksha, check your internet connectivity. You usually ...READ MORE

answered Feb 15, 2019 in Puppet by Jugnu
116 views
0 votes
1 answer

Error: Could not find init script for 'puppet' - Puppet error

You need to be running your processes ...READ MORE

answered Mar 12, 2019 in Puppet by Haider
318 views
0 votes
1 answer

Puppet: Error: Could not parse for environment production: Syntax error at '='; expected '}'

This error occurs if puppet apply -e is used ...READ MORE

answered Aug 1, 2019 in Puppet by Sirajul
• 50,330 points
360 views
+13 votes
2 answers

Git management technique when there are multiple customers and need multiple customization?

Consider this - In 'extended' Git-Flow, (Git-Multi-Flow, ...READ MORE

answered Mar 26, 2018 in DevOps & Agile by DragonLord999
• 8,400 points
412 views
0 votes
1 answer