Displaying 6 results from an estimated 6 matches for "puppet_dashboard_url".
2012 Mar 19
1
dashboard as enc not working
I''m trying to setup dashboard as a node classifier w/puppet 2.6.14.
Not sure why this is not working...
In puppet.conf on the master I have:
node_terminus = exec
external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://
localhost /usr/share/puppet-dashboard/bin/external_node
The agent''s return:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find node ''myhost''; cannot compile
I can run the external node script as the puppet user just fine:
s...
2013 May 13
1
puppet does not see changes in /etc/puppet/puppet.conf
...keeper-commit-post
[master]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
storeconfigs = true
storeconfigs_backend = puppetdb
reports = store,puppetdb
reporturl = http://dashboard/reports/upload
node_terminus = exec
external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://dashboard
/usr/share/puppet-dashboard/bin/external_node
I have restarted/rebooted/reinstalled but still hit the same issue for
puppet-dashboard.
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group a...
2012 Jan 27
2
SSL Errors - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B
...per-secret
dbserver = localhost
dbsocket = /var/lib/mysql/mysql.sock
# For reports
reports = store, http
reporturl = http://host.pvt.domain.com/reports/upload
# For puppet dashboards external node classification.
node_terminus = exec
external_nodes = /usr/bin/env
PUPPET_DASHBOARD_URL=http://puppet:80
/usr/share/puppet-dashboard/bin/external_node
Thank you,
--
Romeo
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, sen...
2012 Oct 15
3
Puppet 3 and master cert error ...
Hey all,
after installing the 3.0.0 version of puppet (debian package from
puppetlabs), doing the initial config, doing an initial start of master to
generate the certs needed and then starting apache with passenger to
control puppetmaster. I can do:
puppet ca list --all
and get a listing of the certs in the system (initially only the master).
afterwards, on the client node, I run:
puppet
2013 Jan 08
4
puppetdb dashboard
...tage of some of the features of the puppetdb (automate nagios
configs etc).
My current master puppet.conf configs are as follows
[master]
autosign = /etc/puppet/autosign.conf
reports = store, http
reporturl = http://127.0.0.1:4000/reports/upload
node_terminus = exec
external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://127.0.0.1:4000/
/usr/share/puppet-dashboard/bin/external_node
storeconfigs = true
storeconfigs_backend = puppetdb
Please let me know what you think.
Thank you,
Luke
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this...
2013 Mar 11
12
Error: stack level too deep
I''m running a previously working set of modules with the Puppet master
version 3.1.0-rc2.
I''m getting the Error: stack level too deep
Here is a chunk of the debug
Debug: Scope(Class[Zabbix]): Retrieving template zabbix/zabbix.conf.php.erb
Debug:
template[/etc/puppet/environments/production/modules/zabbix/templates/zabbix.conf.php.erb]:
Bound template variables for