search for: puppetport

...at RPMs Note: If you remove auth.conf, you are vulnerable, regardless of install method. To determine if you are vulnerable you can execute the puppet resource command, like so: $ puppet resource -H attack.target.mydomain user puppet Secured (auth.conf present): (Attack against server requires puppetport specification, against client does not, assuming default ports. ) $ puppet resource -H attack.target.mydomain user puppet --puppetport 8140 /usr/lib/ruby/1.8/puppet/indirector/rest.rb:57:in `deserialize'': Error 403 on SERVER: Forbidden request: attack.host.mydomain (x.x.x.x) access to /re...

...39;$certname''. # node_name_value = # The server to which server puppet agent should connect # The default value is ''puppet''. server = <puppetmaster> # Which port puppet agent listens on. # The default value is ''8139''. puppetport = 8139 # Document all resources # document_all = false What am I missing? Regards, -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Zb5d1Z...

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

...ation_format = pson prerun_command = /etc/puppet/etckeeper-commit-pre privatedir = /var/lib/puppet/ssl/private privatekeydir = /var/lib/puppet/ssl/private_keys publickeydir = /var/lib/puppet/ssl/public_keys puppetdlockfile = /var/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 repor...

...to ''$logdir/masterhttp.log'' debug: puppetmasterd: Setting manifest to ''$manifestdir/site.pp'' debug: puppetmasterd: Setting masterport to ''8140'' debug: puppetmasterd: Setting bucketdir to ''$vardir/bucket'' debug: puppetd: Setting puppetport to ''8139'' debug: puppetd: Setting localconfig to ''$confdir/localconfig'' debug: puppetd: Setting classfile to ''$confdir/classes.txt'' debug: puppetd: Setting server to ''puppet1'' debug: puppetd: Setting puppetdlog to ''$lo...

Hi- Recently starting using puppet while migrating an existing messy group of systems to some nice new hardware. Things are going incredibly well, and puppet''s functioning great. Have a bit of a headache. I''d like to keep myself from duplicating lots of included classes. Lets say I have this (snippet of a) class: class dbserver { file { "/etc/my_${db}.cnf":

Hi all, I''m Benjamin Sonntag, I''m one of the AlternC project developpers. AlternC is an opensource mass-hosting control panel software suite based on debian. We are working on a new version of this control panel, and we want to make the less and the best work we can for this version. So, as usual, we are using as much free software as we can, and we started to use puppet for

...rces.txt # (Deprecated for ''report_server'') The server to which to send transaction reports. # The default value is ''$server''. reportserver = puppet # Which port puppet agent listens on. # The default value is ''8139''. # puppetport = 8139 # The server to send facts to. # The default value is ''$server''. inventory_server = puppet # The server to use for certificate # authority requests. It''s a separate server because it cannot # and does not need to horizontally scale. #...

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