On Wednesday, September 14, 2016 at 10:56:31 AM UTC-7, Mike Sanker wrote: > > Hi , > > Im running trac 1.0.9 on FreeBSD behind a cosign auth. > > I am getting lots and lots of 503 service unavailable errors. > > I notice when I get them it looks like the authentication is not happening > , the username field should have the authenticated username and is not > being populated (see below) > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/css/trac.css HTTP/1.1" 503 299 > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/css/wiki.css HTTP/1.1" 503 299 > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/jquery.js HTTP/1.1" 503 299 > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/trac.js HTTP/1.1" 503 299 > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/search.js HTTP/1.1" 503 299 > > 128.91.196.14 - username [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/folding.js HTTP/1.1" 304 - > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/babel.js HTTP/1.1" 503 299 > > 128.91.196.14 - username [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/trac_logo_mini.png HTTP/1.1" 304 - > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/trac.js HTTP/1.1" 503 299 > > 128.91.196.14 - username [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/site/penn_fulllogo.gif HTTP/1.1" 200 4431 > > 128.91.196.14 - - [14/Sep/2016:16:53:43 +0000] "GET > /trac/chrome/common/js/search.js HTTP/1.1" 503 299 > > 128.91.196.14 - username [14/Sep/2016:16:53:44 +0000] "GET > /trac/chrome/common/trac.ico HTTP/1.1" 200 3638 > > 128.91.196.14 - - [14/Sep/2016:16:54:18 +0000] "GET /trac/wiki HTTP/1.1" > 503 299 > > > I have attached my httpd.conf and vhost container wondereing if anything > is sticking out as being misconfigured > > > Mike >
I'm not familiar with the cosign auth, but I see a couple of things: * You are using a mix of Apache 2.2 and 2.4 access control directives (there's an "Allow from all") and they cannot be mixed. See https://httpd.apache.org/docs/2.4/upgrading.html#run-time. * You can map static resources using Alias directives, and you don't need Directory blocks for any directories under htdocs, or for htdocs itself: https://trac.edgewall.org//wiki/TracInstall#MappingStaticResources I think you probably just need one Location directive for path "/trac/login" (I'm inferring your base url is /trac), and one Directory directive for path "/var/www/trac/cgi-bin": https://trac.edgewall.org//wiki/TracModWSGI - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
