search for: garst

...ror writing 4 bytes to client. -1. (Connection reset by peer) [2009/06/25 09:21:41, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client 10.1.13.184. Error = Connection reset by peer The Win2K DC logs the following (3221225578 = bad password?): The logon to account: cgarst by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: \\RAVAGE failed. The error code was: 3221225578 Perhaps Samba/Winbind are not passing the authentication packages to the DC correctly? Any suggestions? Thanks. -Corey Garst

Anyone, I''ve read this doc several times: http://docs.puppetlabs.com/guides/plugins_in_modules.html As a whole, it really doesn''t make sense. It seems pretty obvious it was written by someone with deep knowledge of the subject, but there is little context for someone like me. Is there better documentation somewhere? Doug -- You received this message because you are

I''ve been struggling with puppet variable scope all day, well, for several months actually. I think I have pretty simple requirements. For any given node, I want to be able to set a series of variables and include a set of classes, based on three different aspects of a node, being physical location, operating system, and function. If I try and do this with classes, I find that variables

Dear all, Is there any way to enable a particular yum-repo (like: yum -- enablerepo=<repo_name>), which is disabled as default, for a particular package installation? For our system, we need to "dag" for particular two packages but keeping it always enabled, clashes with other packages, which we don''t want to install for dag at all. What''s the option(s) I have to

Some days I wonder why I even bother with puppet. --- classes: - datacentre::new_york - role::appserver - elements::tfel0 environment: production: parameters: < set key/value pairs here > class ldap { < do some stuff that behaves slightly differently between different data centers > } class role::appserver { include ldap } So, I wanted to set some variables in the

Anyone know where I can find a good chrooted named module for centos? Named as chroot is ugly... soft and hard links everywhere... Doug -- 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, send email to

I have a freshly installed and updated CentOS 5.4 system running puppet 0.25.5. I followed the passenger docs here: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger Upon starting the client, the following appears in the apache error log. [Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end of script headers: production [ pid=6785 file=ext/apache2/Hooks.cpp:706

All, Can someone give me some ideas as to, or point me to where I can find documentation on the issues I may have upgrading puppet from 0.25.4 to the latest? Also, the server is using passenger, and I know there''s a whole lot of magic voodoo that has to happen to make sure that the version numbers of all the bits are compatible. Doug -- You received this message because you are

I''ve got a directory, /u01/app that is owned by oracle.oinstall. I have this in my manifest: # # Mount point for the Oracle database. # ''/u01/app'': device => ''/dev/xvdo'', atboot => true, ensure => mounted, fstype => ''ext4'',

I''m trying to wrap my head around these files... do both of them need to reside on the client and master? are there any docs that describe these files and what all the option/ sections are and what they do? Thanks all.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Does anyone know where I can get the latest puppet, 2.7.1 as RPM''s? The spec file that comes with the puppet 2.7.1 source is broken again, and only version 0.25.5 seems to be available via EPEL, which means that the website''s assertion that you can get puppet as an RPM from there is somewhat untrue. Douglas. -- You received this message because you are subscribed to the

So, I noticed that when adding a service to puppet, puppet is running a chkconfig <service>. However, as far as I can tell, puppet should be running a chkconfig --add <service>, otherwise the symlinks don''t get created from the service in /etc/rc.d/rc6.d back to the service in /etc/init.d. As as a result, the service is not stopped on shut down. I must be missing something