Hi,
I gave this another attempt recently with 2.6.2rc1, nginx, and thin
via config.ru. (not nginx + mongrels like earlier)
Now I know a little more about the problem than I did a month ago:
I use a lot of variables such as $project in my file path array I set
for the source parameter for file type resources:
> source => [
> "puppet:///imapproxy/$project/imapproxy.conf.$hostname",
And in my site manifest, I tend to have
class foo {
$project = "blah"
include imapproxy
}
node bar {
include foo
}
I get the correct file served when I use the stock WEBrick/
puppetmasterd and I don't get the correct file served with nginx+thin
+config.ru unless I do:
node bar {
$project = "blah"
include imapproxy
}
FWIW, my server-side logs don't show me the $project part in the GETs
at all - the $hostname (and other facts are) is shown.
[2010-10-06 00:04:35] bar - - [06/Oct/2010:00:04:35 CDT] "GET /
production/file_metadata/users//sudoers.xen-3 HTTP/1.1" 404 48
[2010-10-06 00:04:35] bar - - [06/Oct/2010:00:04:35 CDT] "GET /
production/file_metadata/users//sudoers- HTTP/1.1" 404 43
[2010-10-06 00:04:35] bar - - [06/Oct/2010:00:04:35 CDT] "GET /
production/file_metadata/users//sudoers HTTP/1.1" 200 336
There should've been a "GET /production/file_metadata/users/blah/
sudoers.xen-3" etc.)
Thank you,
Naresh.
On Aug 25, 6:23 pm, "Naresh V." <nares...@gmail.com> wrote:
> Hi,
>
> My setup:
>
> gems:
> rack (1.0.1)
> rails (2.3.4)
> rake (0.8.7)
> activerecord (2.3.8, 2.3.4)
> activeresource (2.3.8, 2.3.4)
> activesupport (2.3.8, 2.3.4)
> mongrel (1.1.5)
>
> RPMs:
> puppet-server-2.6.0-0.7.el5 (tmz's)
>
> I patched the files installed via the RPM to test out nginx+mongrel as
> follows (taken fromhttp://projects.puppetlabs.com/issues/4319):
>
> http://pastie.org/1114966
>
> The problem I'm facing is:
> My modules have 'source' like:
>
> source => [
> "puppet:///imapproxy/$project/imapproxy.conf.
> $hostname",
> "puppet:///imapproxy/$project/imapproxy.conf-$class",
> "puppet:///imapproxy/imapproxy.conf.$hostname",
> "puppet:///imapproxy/imapproxy.conf",
> ],
>
> in my files directory, I have:
>
> /projectA/imapproxy.conf-webmail
> /projectA/imapproxy.conf
>
> In my site manifest, I have a few webmail servers which have $class =
> 'webmail' in them and a few which don't have any $class set to
> something else. Before I migrated to the nginx+mongrel setup (and
> after I reverted back from it), for the nodes that have a $class !=
> 'webmail', the default imapproxy.conf was being served, but now, I'm
> served an emtpy file instead.
>
> The hosts with $class = 'webmail' face no such problem - they receive
> the file they were supposed to receive.
>
> ($project is set to 'projectA' for all nodes in the manifest.)
>
> Is anybody else able to replicate this?
>
> -Naresh.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
