Mailing List Archive

H Darren,

Did you ever get this figured out?

On Dec 14, 2012, at 12:11 PM, Darren Embry <dse@webonastick.com> wrote:

> Hi, I've installed Bricolage 2.0.1 on Ubuntu Precise and after login
> accepts my credentials I get this error:
>
> Fault ClassParams::Callback::Exception::InvalidKeyDescriptionNo
> callback found for callback keyTimestamp2012-12-14
> 12:10:45.000000PackageParams::CallbackRequestFilename/usr/share/perl5/Params/CallbackRequest.pmLine249

That doesn't look right. There is no callback key with that name. And furthermore, the error should look like this:

"No callback found for callback key '$somekey'"

Where is the single-quoted key name? Could something have got lost pasting the error into email?

Best,

David

On Wed, Dec 26, 2012 at 12:31 PM, David E. Wheeler
<david@justatheory.com> wrote:
> Did you ever get this figured out?

Unfortunately, no.

>> Hi, I've installed Bricolage 2.0.1 on Ubuntu Precise and after login
>> accepts my credentials I get this error:
>
> That doesn't look right. There is no callback key with that name. And furthermore, the error should look like this:
>
> "No callback found for callback key '$somekey'"
>
> Where is the single-quoted key name? Could something have got lost pasting the error into email?

Oh good lord apparently a *lot* got lost. Sorry. God forbid I try to
paste a table from Google Chrome...

No callback found for callback key 'login|login_cb'

Fault Class: Params::Callback::Exception::InvalidKey
Description: No callback found for callback key
Timestamp: 2012-12-26 17:31:13.000000
Package: Params::CallbackRequest
Filename: /usr/share/perl5/Params/CallbackRequest.pm
Line: 249

Trace begun at /usr/share/perl5/Params/CallbackRequest.pm line 249

Params::CallbackRequest::request('Params::CallbackRequest=HASH(0x7fcd1d5ac038)',
'HASH(0x7fcd1d4c8050)', 'requester',
'MasonX::Interp::WithCallbacks=HASH(0x7fcd1d5a6c80)', 'apache_req',
'Apache2::Request=SCALAR(0x7fccd402c520)') called at
/usr/share/perl5/MasonX/Interp/WithCallbacks.pm line 119

MasonX::Interp::WithCallbacks::make_request('MasonX::Interp::WithCallbacks=HASH(0x7fcd1d5a6c80)',
'comp', '/login', 'args', 'ARRAY(0x7fccec0169d0)', 'ah',
'HTML::Mason::ApacheHandler=HASH(0x7fcd1d5a6c50)', 'apache_req',
'Apache2::Request=SCALAR(0x7fccd402c520)') called at
/usr/share/perl5/HTML/Mason/ApacheHandler.pm line 874

eval {...} at /usr/share/perl5/HTML/Mason/ApacheHandler.pm line 873

HTML::Mason::ApacheHandler::prepare_request('HTML::Mason::ApacheHandler=HASH(0x7fcd1d5a6c50)',
'Apache2::RequestRec=SCALAR(0x7fccec016af0)') called at
/usr/share/perl5/HTML/Mason/ApacheHandler.pm line 828

HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x7fcd1d5a6c50)',
'Apache2::RequestRec=SCALAR(0x7fccec016af0)') called at
/usr/local/bricolage/lib/Bric/App/Handler.pm line 308

eval {...} at /usr/local/bricolage/lib/Bric/App/Handler.pm line 297

Bric::App::Handler::handler('Apache2::RequestRec=SCALAR(0x7fccec016af0)')
called at -e line 0

eval {...} at -e line 0

On Dec 26, 2012, at 5:34 PM, Darren Embry <dse@webonastick.com> wrote:

> Oh good lord apparently a *lot* got lost. Sorry. God forbid I try to
> paste a table from Google Chrome...
>
> No callback found for callback key 'login|login_cb'

So Bric::App::Callback::Login isn’t getting loaded, or its callbacks aren’t getting registered. Can you send the contents of your httpd.conf and bricolage.conf? Also, what version of Apache, Perl, and mod_perl are you using?

Best,

David

On Dec 28, 2012, at 9:52 AM, Darren Embry <dse@webonastick.com> wrote:

> root@newcms:~# /usr/sbin/apache2 -v
> Server version: Apache/2.2.22 (Ubuntu)
> Server built: Nov 8 2012 21:37:37
>
> root@newcms:~# perl -v
> This is perl 5, version 14, subversion 2 (v5.14.2) built for
> x86_64-linux-gnu-thread-multi
> (with 55 registered patches, see perl -V for more detail)
> *licensing/copyright info removed*

This makes me crazy. Packagers have a habit of borking Perl. I tend to see weird issues like this when using system-provided Perl and mod_perl, but never when I’ve built from source (which is my preferred method of running mod_perl apps, anyway).

> root@newcms:~# dpkg -l | grep -i mod.perl
> ii libapache2-mod-perl2 2.0.5-5ubuntu1 Integration of perl with the
> Apache2 web server

All looks okay to me, at a glance. Anyone else got experience getting Bricolage working with the stock Ubuntu Apache, mod_perl, and Perl installs?

But you might want to try compiling Apache and mod_perl from source, and maybe Perl, too. I suspect that will solve your problems.

Wish I knew what, exactly, caused the error you’re seeing, because it has come up over the years, but I have never seen a satisfactory explanation for it.

Sorry not to be more help.

Best,

David

On Mon, Dec 31, 2012 at 1:06 PM, David E. Wheeler <david@justatheory.com> wrote:
> This makes me crazy. Packagers have a habit of borking Perl. I tend to see weird issues like this when using system-provided Perl and mod_perl, but never when I’ve built from source (which is my preferred method of running mod_perl apps, anyway).
>
>> root@newcms:~# dpkg -l | grep -i mod.perl
>> ii libapache2-mod-perl2 2.0.5-5ubuntu1 Integration of perl with the
>> Apache2 web server
>
> All looks okay to me, at a glance. Anyone else got experience getting Bricolage working with the stock Ubuntu Apache, mod_perl, and Perl installs?
>
> But you might want to try compiling Apache and mod_perl from source, and maybe Perl, too. I suspect that will solve your problems.
>
> Wish I knew what, exactly, caused the error you’re seeing, because it has come up over the years, but I have never seen a satisfactory explanation for it.

I've determined that the cause of my problem was Ubuntu's use of
apache2-mpm-worker by default. Replacing with apache2-mpm-prefork
seems to work just fine though.

Oddly enough I now vaguely remember having come across that once
already for something else. I do not know why I didn't come across
something saying "use the prefork" this time around so this is
probably a big dumb error on my part... heh.

On Jan 11, 2013, at 9:06 PM, Darren Embry <dse@webonastick.com> wrote:

> I've determined that the cause of my problem was Ubuntu's use of
> apache2-mpm-worker by default. Replacing with apache2-mpm-prefork
> seems to work just fine though.
>
> Oddly enough I now vaguely remember having come across that once
> already for something else. I do not know why I didn't come across
> something saying "use the prefork" this time around so this is
> probably a big dumb error on my part... heh.

Maybe, but I appreciate you replying with this information, as it increases the chances that:

1. The next person to have this problem will find your reply in the archives

2. The rest of us will remember you said it and be better able to help others.

Thanks!

David