Bug 206135

Summary:	sysutils/puppet with passenger does not work with www/rubygem-rack 1.6
Product:	Ports & Packages	Reporter:	Dmitry Sivachenko <demon>
Component:	Individual Port(s)	Assignee:	freebsd-ruby (Nobody) <ruby>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	mmoll, osa, ruby, swills
Priority:	---	Keywords:	needs-qa, regression
Version:	Latest	Flags:	koobs: maintainer-feedback? (ruby)
Hardware:	Any
OS:	Any

Description Dmitry Sivachenko freebsd_committer

2016-01-11 17:00:49 UTC

Hello, 

I have a working installation of puppet-3.7.4.  Server is working with passenger-5.0.4 and rubygem-rack-1.4.5.

I performed an upgrade of puppet and everything rubygem* using fresh ports tree.

I found that puppet stopped to work: every request to puppet server returned 403:
5.255.231.233 - - [11/Jan/2016:18:34:18 +0300] "GET /production/file_metadata/pluginfacts?links=manage&source_permissions=use HTTP/1.1" 403 109 "-" "Ruby" "-"


I tried to downgrade different packages and tracked this down to rubygem-rack:
with 1.4.5 it works fine, with 1.6.4 it does not work.

Can this be an incompatibility with passenger+rack? Or is this a puppet problem?

Recent versions of passenger explicitly depend on rubygem-rack16.

Comment 1 Dmitry Sivachenko freebsd_committer

2016-01-11 17:01:54 UTC

I am adding maintainers of puppet and passenger to CC.

Comment 2 Dmitry Sivachenko freebsd_committer

2016-01-11 17:02:36 UTC

I forgot to mention that server is running *inside nginx* with passenger module.

Comment 3 Dmitry Sivachenko freebsd_committer

2016-01-17 08:23:51 UTC

knock-knock!

Guys, do you have success stories running puppet server with nginx and passender and
with rubygem-rack version 1.6?

Comment 4 Steve Wills freebsd_committer

2017-01-04 19:51:57 UTC

Sorry that no one looked at this. A lot has changed in ports since this was opened, I'm hoping it's not still an issue. So, closing for now, reopen if needed.