Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jan 2016 17:00:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 206135] puppet with passenger does not work with rubygem-rack 1.6
Message-ID:  <bug-206135-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206135

            Bug ID: 206135
           Summary: puppet with passenger does not work with rubygem-rack
                    1.6
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: demon@FreeBSD.org

Hello,=20

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=3Dmanage&source_permissions=3Du=
se
HTTP/1.1" 403 109 "-" "Ruby" "-"


I tried to downgrade different packages and tracked this down to rubygem-ra=
ck:
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.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206135-13>