Quantcast
Channel: Ask Puppet: Puppet DevOps Q&A Community - RSS feed
Viewing all articles
Browse latest Browse all 6104

Questions regarding ReportUrl, StoreConfig, running Agent on master

$
0
0
I'm trying to fix these errors on a working Puppet Master and understand how its setup. 1) For reportURL to work, should there be a upload directory? I only see reports folder but no upload. Is that upload a request (for ruby?) or is it trying to upload it to that directory which doesn't exist. puppet.conf reporturl = http://puppet-server/reports/upload Syslog puppet-master[2230]: Compiled catalog for SERVER-01 in environment prod in 1.96 seconds puppet-master[6132]: Unable to submit report to http://puppet-server/reports/upload [504] Gateway Time-out Despite that error I see Yaml files gets created under a different filesystem/var/reports directory but I don't see that path linked anywhere? 2) How to setup StoreConfigs? I mean the DB part. I saw seeing this error, so I enabled store-config in puppet.conf and it threw more errors related to DB. I reverted the change. I think whatever database or tables it need doesn't exist or something. You cannot collect exported resources without StoreConfigs being set; the collection will be ignored on line It looks like current database is setup only for dashboard and it has the following tables; mysql> show tables; +--------------------------------+ | Tables_in_dashboard_production | +--------------------------------+ | delayed_job_failures | | delayed_jobs | | metrics | | node_class_memberships | | node_classes | | node_group_class_memberships | | node_group_edges | | node_group_memberships | | node_groups | | nodes | | old_reports | | parameters | | report_logs | | reports | | resource_events | | resource_statuses | | schema_migrations | | timeline_events | +--------------------------------+ 3) Puppet agent on puppet master. I get this error whenever puppet agent runs on the master server. Master, Agent, Dashboard are on the same host, Remote agents works fine. puppet agent -t --noop Notice: Ignoring --listen on onetime run Warning: Unable to fetch my node definition, but the agent run will continue: Warning: 403 "Forbidden" Info: Retrieving pluginfacts Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources using 'eval_generate': 403 "Forbidden" Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet://puppet-server/pluginfacts: 403 "Forbidden" Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': 403 "Forbidden" Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet://puppet-server/plugins: 403 "Forbidden" Info: Loading facts Error: Could not retrieve catalog from remote server: 403 "Forbidden" Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: 403 "Forbidden" puppet.conf file on the master/agent server. OS has a no_proxy env variable so localhost(http of puppet-server) request doesn't go through proxy. It was added few minutes ago just to see if it was causing any issue but its not that. [main] server=puppet-server http_proxy_host=proxy-server http_proxy_port=8787 disable_warnings = deprecations environmentpath = /etc/puppet/environments default_manifest = /etc/puppet/manifests/nodes.pp disable_per_environment_manifest = true [master] reports = store, http reporturl = http://proxy-server/reports/upload node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://puppet /usr/share/puppet-dashboard/bin/external_node dns_alt_names = puppet-server, puppet nodes.pp has entry for the localhost. node default inherits common { } node puppet-server inherits common { } node server-0x inherits common { include that include this }

Viewing all articles
Browse latest Browse all 6104

Trending Articles