search for: masterport

...e HOWTO step-by-step and I'm not sure what I missed. Thanks, Misty smbldap_conf.pm: use strict; package smbldap_conf; use vars qw($VERSION @ISA @EXPORT @EXPORT_OK %EXPORT_TAGS $UID_START $GID_START $smbpasswd $slaveLDAP $masterLDAP $slavePort $masterPort $ldapSSL $slaveURI $masterURI $with_smbpasswd $mk_ntpasswd $ldap_path $ldap_opts $ldapmodify $suffix $usersdn $computersdn $groupsdn $scope $binddn $bindpasswd $slaveDN $slavePw $masterDN $masterPw $_u...

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted: certificate verify failed If anyone could explain what''s happening with the certificates here, I''d really appreciate...

I've written a Smalltalk application which starts R on another machine and then communicates with it via sockets. The functions involved are: slaveStart <- function(masterHost, masterPort){ inPort <- availablePort() sendSocket(as.character(inPort), masterHost, masterPort) socketSlave(inPort) } socketSlave <- function(inPort){ ## listens on inPort. on.exit(closeAllConnections(), add = T) repeat { inConn <- socketConnection(port = inPort, server = T, bloc...

...few snags. I''ve set up an alternate directory for the testing branch config files, and have created a copy of everything stored under /var/lib/puppet and pointed the test server to that stuff. However, when I try to connect to the test server from a client (puppetd --test --noop --masterport 8141), i get an openssl error: /usr/lib/ruby/1.8/net/http.rb:586:in `connect'': certificate verify failed (OpenSSL::SSL::SSLError) I''ve checked with openssl s_client and both the servers are passing the same info. Is there something I''m overlooking?

...to apply a manifest root@nscbose:/home/bala/puppet# puppet -V 2.7.11 root@nscbose:/home/bala/puppet# cat /etc/debian_version wheezy/sid root@nscbose:/home/bala/puppet# ps aux | grep -i puppet puppet 4938 3.7 4.9 37764 25288 ? Ssl 03:01 0:40 /usr/bin/ruby1.8 /usr/bin/puppet master --masterport=8140 root 4945 4.1 3.8 31396 19508 pts/0 Sl+ 03:03 0:37 /usr/bin/ruby1.8 /usr/bin/puppet apply 3.file.pp root 5020 0.0 0.1 4364 848 pts/1 S+ 03:19 0:00 grep --color=auto -i puppet root@nscbose:/home/bala/puppet# cat 3.file.pp notify {''bignotify'':...

...the wiki, and will submit some puppet patches against 0.23.2 next week, but here''s what I''ve done that has made a big difference to stability here. in puppetmasterd at line 261, I''ve modified the Mongrel instantiation from: server = Mongrel::HttpServer.new(addr, Puppet[:masterport]) to webserver = Mongrel::HttpServer.new(addr, Puppet[:masterport], timeout=4) timeout is a throttling parameter for Mongrel in hundredths of a second between socket.accept() calls. I''m planning to submit some patches that let you configure more mongrel parameters as puppetmasterd conf...

...eable = No [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon guest ok = Yes share modes = No smbldap.conf ************ sambaDomain="MYDOMAIN" slaveLDAP="127.0.0.1" slavePort="389" masterLDAP="127.0.0.1" masterPort="389" ldapTLS="0" suffix="dc=example,dc=org" usersdn="ou=people,${suffix}" computersdn="ou=machines,${suffix}" groupsdn="ou=groups,${suffix}" sambaUnixIdPooldn="sambaDomainName=MYDOMAIN,${suffix}" scope="one" hash_encry...

...A_OPTS="--servertype=mongrel" And puppet is running as: puppet 2848 12.8 3.1 147100 131852 ? Rsl 11:52 1:56 /usr/bin/ruby /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp --servertype=mongrel --logdest=/var/log/puppet/puppetmaster.log --servertype=mongrel --masterport=18140 --pidfile=/var/run/puppet/puppetmaster.18140.pid puppet 2866 0.0 0.5 37204 21260 ? Ssl 11:52 0:00 /usr/bin/ruby /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp --servertype=mongrel --logdest=/var/log/puppet/puppetmaster.log --servertype=mongrel --masterport=18...

Is there a way of specifying the server on a different port? I want to be able to change between two different puppetmasterd''s on the same box, and I want to pick between them by using selecting the port. There seems to be lots of :port* symbols floating around, and a --port in puppetd, but it''s not looking consistent. Is this something on the TODO path, or is there a

I work at a large financial institution (AXA) and we have a large number of DMZs for our partner and internet-facing servers. The only access to the various DMZs is via SSH and no DMZ-initiated connections are allowed back to the internal network. I''d consider putting a Puppet server in the DMZ but no communication is allowed between DMZs either. Has anyone tried tunnelling Puppet

...ot;%g" set primary group script = /usr/local/sbin/smbldap-usermod -g "%g" "%u" ### smbldap.conf without comments ### SID="S-1-5-21-725326080-1709766072-2910717368" slaveLDAP="127.0.0.1" slavePort="389" masterLDAP="127.0.0.1" masterPort="389" ldapTLS="0" verify="optional" cafile="/etc/openldap/slapd-cert.pem" clientcert="/etc/smbldap-tools/smbldap-tools.pem" clientkey="/etc/smbldap-tools/smbldap-tools.key" suffix="dc=borkholder,dc=com" usersdn="ou=People,${...

...ee Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, # USA. # Purpose : # . be the configuration file for all smbldap-tools scripts use vars qw($VERSION @ISA @EXPORT @EXPORT_OK %EXPORT_TAGS $UID_START $GID_START $smbpasswd $slaveLDAP $masterLDAP $slavePort $masterPort $ldapSSL $slaveURI $masterURI $with_smbpasswd $mk_ntpasswd $ldap_path $ldap_opts $ldapmodify $suffix $usersdn $computersdn $groupsdn $scope $binddn $bindpasswd $slaveDN $slavePw $masterDN $masterPw $_userLoginShell $_userHomePrefix $_userGecos $_defaultUserGid $_defaultComputerGid $_skeletonDir $_u...

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

...ss_base_passwd ou=computers,dc=example,dc=com?sub nss_base_group ou=groups,dc=example,dc=com?sub And the smbldap.conf: SID="S-1-5-21-158730468-2379596502-3695168017" sambaDomain="REALM" slaveLDAP="127.0.0.1" slavePort="389" masterLDAP="127.0.0.1" masterPort="389" ldapTLS="0" verify="require" cafile="" clientcert="" clientkey="" suffix="dc=example,dc=com" usersdn="ou=people,${suffix}" computersdn="ou=computers,${suffix}" groupsdn="ou=groups,${suffix}" sa...

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

...700 directory mask = 0700 browsable = no --- end of smb.conf --- smbldap_conf.pm $UID_START = 2000; $GID_START = 2000; $SID='S-1-5-21-4276031234-832571036-2739979074'; $slaveLDAP = "127.0.0.1"; $slavePort = "389"; $masterLDAP = "127.0.0.1"; $masterPort = "389"; $ldapSSL = "1"; $suffix = "dc=myhost,dc=com"; $usersou = q(People); $usersdn = "ou=$usersou,$suffix"; $computersou = q(People); $computersdn = "ou=$computersou,$suffix"; $groupsou = q(Groups); $groupsdn = "ou=$groupsou,$suffix&quo...

I came in this morning to find all the servers all locked up solid: # passenger-status ----------- General information ----------- max = 20 count = 20 active = 20 inactive = 0 Waiting on global queue: 236 ----------- Domains ----------- /etc/puppet/rack: PID: 2720 Sessions: 1 Processed: 939 Uptime: 9h 22m 18s PID: 1615 Sessions: 1 Processed: 947 Uptime: 9h 23m

We have often the Problem that some files need to be checked for updates faster than the cycle of the puppet agent. I try to solve this with a script which tries to download the files directly from the fileserver of the puppetmaster. So far i couldn''t get it to work. I don''t know if i got the URL right, i did not find any examples on the REST API documentation for the

...r is set to "389" slavePort="389" # Master LDAP server: needed for write operations # Ex: masterLDAP=127.0.0.1 # If not defined, parameter is set to "127.0.0.1" masterLDAP="127.0.0.1" # Master LDAP port # If not defined, parameter is set to "389" #masterPort="389" masterPort="389" # Use TLS for LDAP # If set to 1, this option will use start_tls for connection # (you should also used the port 389) # If not defined, parameter is set to "0" ldapTLS="0" # Use SSL for LDAP # If set to 1, this option will use SSL for...