I''m trying to setup a module to deploy custom facts, and I''m running into some issues. I''ve created a directory called "custom" in my modules directory, and created sub-directories there so I have custom/lib/facter (as is described in the documentation). On my puppetmaster, I''ve added this to fileserver.conf: [plugins] allow * In puppet.conf for the client I''ve added this to the [main] section, also per the docs: pluginsync = true factpath = $vardir/lib/facter However, when I run puppetd, I get the following error: err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': Error 400 on SERVER: private method `gsub'' called for nil:NilClass The only way to get rid of this error is to set the libdir variable, which I don''t think is right. Can anyone point out what I''m doing wrong here? The documentation on custom facts is pretty horrible, and is too much a mish-mash of old vs new methods. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Sep 7, 2010 at 1:59 PM, James Cammarata <jimi@sngx.net> wrote:> > I''m trying to setup a module to deploy custom facts, and I''m running into > some issues. > > I''ve created a directory called "custom" in my modules directory, and > created sub-directories there so I have custom/lib/facter (as is described > in the documentation). > > On my puppetmaster, I''ve added this to fileserver.conf: > > [plugins] > allow * > > In puppet.conf for the client I''ve added this to the [main] section, also > per the docs: > > pluginsync = true > factpath = $vardir/lib/facter > > However, when I run puppetd, I get the following error: > > err: /File[/var/lib/puppet/lib]: Failed to generate additional resources > using ''eval_generate'': Error 400 on SERVER: private method `gsub'' called > for nil:NilClass > > > The only way to get rid of this error is to set the libdir variable, which > I don''t think is right. Can anyone point out what I''m doing wrong here? > The documentation on custom facts is pretty horrible, and is too much a > mish-mash of old vs new methods. >So setting the factpath isn''t enough? You''re finding you need to set the libdir as well? What is the libdir set to with the above settings? (sudo puppetd --configprint libdir) What puppet versions are you running? I don''t believe you need a [plugins] mountpoint defined. With 0.25.x I don''t have one, and modules/*/lib/facter syncs quite happily.> -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> The only way to get rid of this error is to set the libdir variable, >> which >> I don''t think is right. Can anyone point out what I''m doing wronghere?>> The documentation on custom facts is pretty horrible, and is too much a >> mish-mash of old vs new methods. >> > > So setting the factpath isn''t enough? You''re finding you need to set > the libdir as well? What is the libdir set to with the above settings? > (sudo puppetd --configprint libdir)Setting libdir on the client just causes a different error to be generated, it doesn''t really work still.> What puppet versions are you running?0.25.4, installed from EPEL RPMs.> I don''t believe you need a [plugins] mountpoint defined. > > With 0.25.x I don''t have one, and modules/*/lib/facter syncs quitehappily. It appears to be optional, it creates a default if you don''t based on puppetmasterd --debug output -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, 08 Sep 2010 11:25:39 -0500, James Cammarata <jimi@sngx.net> wrote:>>> The only way to get rid of this error is to set the libdir variable, >>> which >>> I don''t think is right. Can anyone point out what I''m doing wrong > here? >>> The documentation on custom facts is pretty horrible, and is too much a >>> mish-mash of old vs new methods. >>> >> >> So setting the factpath isn''t enough? You''re finding you need to set >> the libdir as well? What is the libdir set to with the above settings? >> (sudo puppetd --configprint libdir) > > Setting libdir on the client just causes a different error to begenerated,> it doesn''t really work still. > > >> What puppet versions are you running? > > 0.25.4, installed from EPEL RPMs. > > >> I don''t believe you need a [plugins] mountpoint defined. >> >> With 0.25.x I don''t have one, and modules/*/lib/facter syncs quite > happily. > > It appears to be optional, it creates a default if you don''t based on > puppetmasterd --debug outputAfter some discussion in IRC, it appears the issue may be related to this: http://www.mail-archive.com/puppet-users@googlegroups.com/msg08955.html I have had issues with deploying directories recursively in the past, so this must be what is happening. I''m unclear what the resolution finally was on that thread, so if anyone has seen that issue I''d appreciate any help. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata <jimi@sngx.net> wrote:> >>> The only way to get rid of this error is to set the libdir variable, >>> which >>> I don''t think is right. Can anyone point out what I''m doing wrong > here? >>> The documentation on custom facts is pretty horrible, and is too much a >>> mish-mash of old vs new methods. >>> >> >> So setting the factpath isn''t enough? You''re finding you need to set >> the libdir as well? What is the libdir set to with the above settings? >> (sudo puppetd --configprint libdir) > > Setting libdir on the client just causes a different error to be generated, > it doesn''t really work still.How does the error differ? So lets step back and make sure all the right bits are set up. Are you using environments? Is the server definitely serving the modulepath that you think it is to this client? Can you confirm that with a manifest in that modulepath and running with --no-pluginsync on the client? I believe I''ve seen your error in the past when you try to pluginsync and the server is serving an empty directory for the plugin source.> > >> What puppet versions are you running? > > 0.25.4, installed from EPEL RPMs. > > >> I don''t believe you need a [plugins] mountpoint defined. >> >> With 0.25.x I don''t have one, and modules/*/lib/facter syncs quite > happily. > > It appears to be optional, it creates a default if you don''t based on > puppetmasterd --debug output > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, 8 Sep 2010 09:46:15 -0700, Nigel Kersten <nigel@explanatorygap.net> wrote:> On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata <jimi@sngx.net> wrote: >> >>>> The only way to get rid of this error is to set the libdir variable, >>>> which >>>> I don''t think is right. Can anyone point out what I''m doing wrong >> here? >>>> The documentation on custom facts is pretty horrible, and is too mucha>>>> mish-mash of old vs new methods. >>>> >>> >>> So setting the factpath isn''t enough? You''re finding you need to set >>> the libdir as well? What is the libdir set to with the above settings? >>> (sudo puppetd --configprint libdir) >> >> Setting libdir on the client just causes a different error to be >> generated, >> it doesn''t really work still. > > How does the error differ? > > So lets step back and make sure all the right bits are set up. > > Are you using environments? > > Is the server definitely serving the modulepath that you think it is > to this client? Can you confirm that with a manifest in that > modulepath and running with --no-pluginsync on the client? > > I believe I''ve seen your error in the past when you try to pluginsync > and the server is serving an empty directory for the plugin source.We''ve run through it in IRC, everything seems to be setup correctly. I also found this: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg09720.html Which states an invalid url is generated sometimes for 0.25.4-1 (my same version) when recursive directories are deployed. I checked the master http log and see this: [07/Sep/2010:17:14:37 EDT] "GET /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A-+.svn%0A-+CVS%0A-+.git%0A&links=manage HTTP/1.1" 400 45 See the double && in there after recurse=true - that may be the issue. Interesting if you''ve seen the same issue with empty plugin directories, I''ll try and touch a file in them to make sure at least something is there. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Sep 8, 2010 at 9:53 AM, James Cammarata <jimi@sngx.net> wrote:> > On Wed, 8 Sep 2010 09:46:15 -0700, Nigel Kersten <nigel@explanatorygap.net> > wrote: >> On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata <jimi@sngx.net> wrote: >>> >>>>> The only way to get rid of this error is to set the libdir variable, >>>>> which >>>>> I don''t think is right. Can anyone point out what I''m doing wrong >>> here? >>>>> The documentation on custom facts is pretty horrible, and is too much > a >>>>> mish-mash of old vs new methods. >>>>> >>>> >>>> So setting the factpath isn''t enough? You''re finding you need to set >>>> the libdir as well? What is the libdir set to with the above settings? >>>> (sudo puppetd --configprint libdir) >>> >>> Setting libdir on the client just causes a different error to be >>> generated, >>> it doesn''t really work still. >> >> How does the error differ? >> >> So lets step back and make sure all the right bits are set up. >> >> Are you using environments? >> >> Is the server definitely serving the modulepath that you think it is >> to this client? Can you confirm that with a manifest in that >> modulepath and running with --no-pluginsync on the client? >> >> I believe I''ve seen your error in the past when you try to pluginsync >> and the server is serving an empty directory for the plugin source. > > We''ve run through it in IRC, everything seems to be setup correctly. I > also found this: > > http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg09720.html > > Which states an invalid url is generated sometimes for 0.25.4-1 (my same > version) when recursive directories are deployed. I checked the master > http log and see this:Just for the record, I have many tens of thousands of 0.25.4-1 clients, and I''ve never ever seen this problem with pluginsync.> > [07/Sep/2010:17:14:37 EDT] "GET > /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A-+.svn%0A-+CVS%0A-+.git%0A&links=manage > HTTP/1.1" 400 45Interesting. Mine always show up like: "GET /ubuntu_desktop_lucid_stable/file_metadatas/plugins?&ignore=---+%0A-+.svn%0A-+CVS%0A-+.git%0A&links=manage&recurse=true HTTP/1.1" 200 13239 "-" "-"> > See the double && in there after recurse=true - that may be the issue. > > Interesting if you''ve seen the same issue with empty plugin directories, > I''ll try and touch a file in them to make sure at least something is > there. > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> Just for the record, I have many tens of thousands of 0.25.4-1 > clients, and I''ve never ever seen this problem with pluginsync.Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same: [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage HTTP/1.1" 400 45 [2010-09-08 14:34:51] - -> /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage The odd thing is, I''m not using environments, but the production entry is in that url... I wonder if it''s secretly using them somehow, but frankly I''m out of ideas at this point. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, 08 Sep 2010 13:39:34 -0500, James Cammarata <jimi@sngx.net> wrote:>> Just for the record, I have many tens of thousands of 0.25.4-1 >> clients, and I''ve never ever seen this problem with pluginsync. > > Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same: > > [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET >/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage> HTTP/1.1" 400 45 > [2010-09-08 14:34:51] - -> >/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage> > > The odd thing is, I''m not using environments, but the production entry is > in that url... I wonder if it''s secretly using them somehow, but frankly > I''m out of ideas at this point.Ok, it is 100% sure that URL causing the issue... I can test it with wget: # wget -O- --no-check-certificate ''https://myserver:8140/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage'' 2010-09-08 14:56:01 ERROR 400: private method `gsub'' called for nil:NilClass. # wget -O- --no-check-certificate ''https://myserver:8140/production/file_metadatas/plugins?recurse=true&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage'' 2010-09-08 14:57:04 ERROR 403: Forbidden request: myserver(myip) access to /file_metadata/plugins [search] at line 93 That 403 is because I''m not using a proper SSL cert to connect to the system. Removing the extra & from the URL makes the error go away. This would seem to be a bug related to the way puppetmasterd parses the URL - it doesn''t check for null arguments. Copying -dev on this as well... -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata <jimi@sngx.net> wrote:> >> Just for the record, I have many tens of thousands of 0.25.4-1 >> clients, and I''ve never ever seen this problem with pluginsync. > > Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same: > > [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET > /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage > HTTP/1.1" 400 45 > [2010-09-08 14:34:51] - -> > /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage > > > The odd thing is, I''m not using environments, but the production entry is > in that url... I wonder if it''s secretly using them somehow, but frankly > I''m out of ideas at this point.production is the default environment, so that does make some sense. So I take it you''ve defined a default modulepath underneath [puppetmasterd] but haven''t defined any environments? Are you sure your client is connecting to the modulepath that you''re adding facts to? Have you confirmed that with a manifest and --no-pluginsync ?> > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- nigel -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten <nigelk@google.com> wrote:> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata <jimi@sngx.net> wrote: >> >>> Just for the record, I have many tens of thousands of 0.25.4-1 >>> clients, and I''ve never ever seen this problem with pluginsync. >> >> Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same: >> >> [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET >>/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage>> HTTP/1.1" 400 45 >> [2010-09-08 14:34:51] - -> >>/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage>> >> >> The odd thing is, I''m not using environments, but the production entryis>> in that url... I wonder if it''s secretly using them somehow, but frankly >> I''m out of ideas at this point. > > production is the default environment, so that does make some sense. > > So I take it you''ve defined a default modulepath underneath > [puppetmasterd] but haven''t defined any environments? > > Are you sure your client is connecting to the modulepath that you''re > adding facts to? Have you confirmed that with a manifest and > --no-pluginsync ?Yes, that is how I have things setup. Even with the gsub error, the client continues to parse the manifest and apply it correctly, it just doesn''t pull down the custom facts. We''ve had a working puppet setup for months, it was only yesterday that I started trying out custom facts, so I know everything was working up until then. I had noticed issues in the past with recursive directories though, and had just ignored it and not used them (not much need for it), but it seems that this would be the underlying issue. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Sep 8, 2010 at 12:05 PM, James Cammarata <jimi@sngx.net> wrote:> > On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten <nigelk@google.com> wrote: >> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata <jimi@sngx.net> wrote: >>> >>>> Just for the record, I have many tens of thousands of 0.25.4-1 >>>> clients, and I''ve never ever seen this problem with pluginsync. >>> >>> Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same: >>> >>> [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET >>> > /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage >>> HTTP/1.1" 400 45 >>> [2010-09-08 14:34:51] - -> >>> > /production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage >>> >>> >>> The odd thing is, I''m not using environments, but the production entry > is >>> in that url... I wonder if it''s secretly using them somehow, but frankly >>> I''m out of ideas at this point. >> >> production is the default environment, so that does make some sense. >> >> So I take it you''ve defined a default modulepath underneath >> [puppetmasterd] but haven''t defined any environments? >> >> Are you sure your client is connecting to the modulepath that you''re >> adding facts to? Have you confirmed that with a manifest and >> --no-pluginsync ? > > Yes, that is how I have things setup. Even with the gsub error, the client > continues to parse the manifest and apply it correctly, it just doesn''t > pull down the custom facts. We''ve had a working puppet setup for months, > it was only yesterday that I started trying out custom facts, so I know > everything was working up until then. I had noticed issues in the past > with recursive directories though, and had just ignored it and not used > them (not much need for it), but it seems that this would be the underlying > issue.I wonder if things start working for you if you define a [production] environment with the same modulepath? -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, 8 Sep 2010 12:13:04 -0700, Nigel Kersten <nigelk@google.com> wrote:> On Wed, Sep 8, 2010 at 12:05 PM, James Cammarata <jimi@sngx.net> wrote: >> >> On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten <nigelk@google.com> >> wrote: >>> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata <jimi@sngx.net> wrote: >>>> >>>>> Just for the record, I have many tens of thousands of 0.25.4-1 >>>>> clients, and I''ve never ever seen this problem with pluginsync. >>>> >>>> Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is thesame:>>>> >>>> [2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET >>>> >>/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage>>>> HTTP/1.1" 400 45 >>>> [2010-09-08 14:34:51] - -> >>>> >>/production/file_metadatas/plugins?recurse=true&&ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage>>>> >>>> >>>> The odd thing is, I''m not using environments, but the production entry >> is >>>> in that url... I wonder if it''s secretly using them somehow, but >>>> frankly >>>> I''m out of ideas at this point. >>> >>> production is the default environment, so that does make some sense. >>> >>> So I take it you''ve defined a default modulepath underneath >>> [puppetmasterd] but haven''t defined any environments? >>> >>> Are you sure your client is connecting to the modulepath that you''re >>> adding facts to? Have you confirmed that with a manifest and >>> --no-pluginsync ? >> >> Yes, that is how I have things setup. Even with the gsub error, the >> client >> continues to parse the manifest and apply it correctly, it just doesn''t >> pull down the custom facts. We''ve had a working puppet setup for >> months, >> it was only yesterday that I started trying out custom facts, so I know >> everything was working up until then. I had noticed issues in the past >> with recursive directories though, and had just ignored it and not used >> them (not much need for it), but it seems that this would be the >> underlying >> issue. > > I wonder if things start working for you if you define a [production] > environment with the same modulepath?Definitely ruby''s fault on this one, apparently. The original system I was testing on is RHEL4, with ruby 1.8.1-7. I just tested the exact same configs on a RHEL5 box with ruby 1.8.5-5 and it worked flawlessly: # /usr/sbin/puppetd --no-daemonize --onetime --ignoreschedules --color=false --reports=false --verbose --no-usecacheonfailure --noop info: Retrieving plugin info: Caching certificate_revocation_list for ca notice: /File[/var/lib/puppet/lib/facter]/ensure: created notice: /File[/var/lib/puppet/lib/facter/hw_type.rb]/ensure: content changed ''{md5}02adcd0c46df8d655b52b57d40f24e2c'' to ''{md5}02adcd0c46df8d655b52b57d40f24e2c'' So, the question is, obviously it''s a problem with an older ruby version, but should puppet be more careful about the URLs it crafts and sends so that this problem doesn''t come up? RHEL4 is still supported, isn''t it? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sep 8, 2010, at 9:45 PM, James Cammarata wrote:> Definitely ruby''s fault on this one, apparently. The original system I was > testing on is RHEL4, with ruby 1.8.1-7. I just tested the exact same > configs on a RHEL5 box with ruby 1.8.5-5 and it worked flawlessly:I guess ruby 1.8.1 is the fault: http://projects.reductivelabs.com/projects/puppet/wiki/Frequently_Asked_Questions#What+Is+The+Minimum+Version+of+Ruby? All the best, Sandor Szücs -- -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, 9 Sep 2010 11:43:44 +0200, Sandor Szuecs <sandor.szuecs@fu-berlin.de> wrote:> On Sep 8, 2010, at 9:45 PM, James Cammarata wrote: > >> Definitely ruby''s fault on this one, apparently. The original system I >> was >> testing on is RHEL4, with ruby 1.8.1-7. I just tested the exact same >> configs on a RHEL5 box with ruby 1.8.5-5 and it worked flawlessly: > > I guess ruby 1.8.1 is the fault: >http://projects.reductivelabs.com/projects/puppet/wiki/Frequently_Asked_Questions#What+Is+The+Minimum+Version+of+Ruby?> > All the best, Sandor SzücsInteresting, considering it''s released with EPEL for RHEL4, but the highest version of ruby available on RHEL4 systems appears to be the 1.8.1-7 version. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.