Bug #121060 for Moose: Can't locate...

Mon Apr 10 07:43:29 2017 andy.newby [...] gmail.com - Ticket created

Subject:	Can't locate...
Date:	Mon, 10 Apr 2017 12:42:52 +0100
To:	bug-Moose [...] rt.cpan.org
From:	Andy Newby <andy.newby [...] gmail.com>

Hi, This has been bugging me for ages. My log files get clogged up with this all the time: [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) [Mon Apr 10 10:21:50 2017] -e: Apache2::Reload: Can't locate (set by Moose) About 30-50 times per request. What does it mean? And how can I get rid of it? As far as I can tell the script runs through without any issues, so I'm not even sure what it means! Cheers andy

Mon Apr 10 08:51:29 2017 DROLSKY [...] cpan.org - Correspondence added

I'm not really sure why this is happening either. Apache::Reload does some disturbing things, and those disturbing things may not play well with Moose. That said, I would very _strongly_ recommend that you not use Apache::Reload in production. It's much better practice to restart the apache w/ mod_perl every time you deploy new code.

Mon Apr 10 08:51:30 2017 The RT System itself - Status changed from 'new' to 'open'

Mon Apr 10 08:56:12 2017 andy.newby [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #121060] Can't locate...
Date:	Mon, 10 Apr 2017 13:54:34 +0100
To:	bug-Moose [...] rt.cpan.org
From:	Andy Newby <andy.newby [...] gmail.com>

Thanks for the quick reply. So how am I supposed to use mod_perl ? This is how I currently have it setup: PerlRequire /srv/www/steampunkjunkies.net/startup.pl PerlModule Apache2::Reload PerlInitHandler Apache2::Reload PerlModule Apache2::RequestRec <Location /cgi-bin> SetHandler perl-script AddHandler cgi-script .cgi PerlResponseHandler ModPerl::Registry PerlOptions +ParseHeaders Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch AllowOverride All Require all granted </Location> It's different to how I used to do it in Apache 2.2, but I assumed that was due to some internal changes. I'm open to suggestions :) Cheers Andy Newby *Email:* andy@ultranerds.co.uk *WWW: *http://www.ultranerds.co.uk *Mobile: * 07769 201 576 On 10 April 2017 at 13:51, Dave Rolsky via RT <bug-Moose@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=121060 > > > I'm not really sure why this is happening either. Apache::Reload does some > disturbing things, and those disturbing things may not play well with Moose. > > That said, I would very _strongly_ recommend that you not use > Apache::Reload in production. It's much better practice to restart the > apache w/ mod_perl every time you deploy new code. >

Mon Apr 10 13:13:59 2017 ether [...] cpan.org - Reference by ticket #121058 added

Wed Apr 12 20:28:32 2017 DROLSKY [...] cpan.org - Correspondence added

On 2017-04-10 07:56:12, andy.newby@gmail.com wrote: Show quoted text

> Thanks for the quick reply. So how am I supposed to use mod_perl ? > This is > how I currently have it setup: > > PerlRequire /srv/www/steampunkjunkies.net/startup.pl > PerlModule Apache2::Reload > PerlInitHandler Apache2::Reload

You'd have to remove the Apache2::Reload lines. I'm going to close this ticket since I strongly suspect the bug is with Apache2::Reload, not Moose.

Wed Apr 12 20:28:44 2017 DROLSKY [...] cpan.org - Status changed from 'open' to 'rejected'