search for: reportfrom

...manifestdir = $vardir/manifests 14 modulepath = $vardir/modules 15 16 [ca] 17 autosign = false 18 19 [puppetd] 20 listen = true 21 report = true 22 splay = false 23 24 [reporting] 25 reports = tagmail 26 27 [tagmail] 28 reportfrom = foo@host I can only get it to work as expected with: 1 $Id$ 2 3 [main] 4 confdir = <%= confdir %> 5 vardir = <%= vardir %> 6 7 rundir = /var/run 8 logdir = /var/log 9 10 ssldir = $vardir/ssl 11 12 [puppetmasterd] 13 manif...

...uctivelabs.com/cgi-bin/puppet.cgi/wiki/ReportsAndReporting, with tagmail defined as one of the report types - but I do not recieve any mail at all. I''ve configured a tagmail.conf file like this: all: root@localhost But the documentation mentions three options, namely sendmail, reportfrom, smtpserver. Should they also be set in tagmail.conf...? And should it be "ini" style...? -- Med venlig hilsen Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: 70 202 407 / Fax: 33 313 640 www.fab-it.dk / juri@fab-it.dk

Sorry if this is obvious, but how can I have reports emailed to me- I want to know what each puppetd update is changing Thanks --e Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

...r/lib/puppet/state/puppetdlock puppetdlog = /var/log/puppet/puppetd.log puppetport = 8139 queue_source = stomp://localhost:61613/ queue_type = stomp rails_loglevel = info railslog = /var/log/puppet/rails.log report = true report_port = 8140 report_server = puppet reportdir = /var/lib/puppet/reports reportfrom = report@vusion-production. reports = store reportserver = puppet reporturl = http://localhost:3000/reports/upload req_bits = 2048 requestdir = /var/lib/puppet/ssl/certificate_requests resourcefile = /var/lib/puppet/state/resources.txt rest_authconfig = /etc/puppet/auth.conf route_file = /etc/puppe...

...ge. No helpful information in the master log. I''m running the master with: /usr/sbin/puppetmasterd --no-daemonize --debug --logdest console --verbose --trace and some relevant puppet.conf portions on the master: storeconfigs = true thin_storeconfigs = true reports = log,puppet_dashboard reportfrom = root syslogfacility = user # Remote Inventory Service facts_terminus = rest inventory_server = tv-puppetma1.techtarget.com # fqdn of master inventory_port = 8140 The exact behavior I''m seeing is that when I run puppetd on the node, all works well up to seeing "debug: catalog supp...

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

...is ''$vardir/templates''. templatedir = /var/lib/puppet/templates # Document all resources # document_all = false # The ''from'' email address for the reports. # The default value is ''report@ip-10-36-11-244.ec2.internal''. # reportfrom = report@ip-10-36-11-244.ec2.internal # The mapping between reporting tags and email addresses. # The default value is ''$confdir/tagmail.conf''. tagmap = /etc/puppet/tagmail.conf # The server through which to send email reports. # The default value is '...

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction