in reply to Re^2: Trying to use Apache2::Module throws an Apache exception
in thread Trying to use Apache2::Module throws an Apache exception

Thanks for this extra info. I'd still be interested to see those parts of the Apache configuration where you have

  1. Loaded the module
  2. Used the new directive

If the problem is with either of those then it should be easy both to spot and to remedy.

  • Comment on Re^3: Trying to use Apache2::Module throws an Apache exception

Replies are listed 'Best First'.
Re^4: Trying to use Apache2::Module throws an Apache exception
by davehodg (Acolyte) on Sep 08, 2017 at 09:01 UTC
    I've created a stripped down httpd.conf and it's definitely the call to ::add that's triggering it: 
    
my @directives = (
                  {
                   name         => 'JournalsTrans',                
                  },
                 );

Apache2::Module::add(__PACKAGE__, \@directives);

    [download]
    All httpd.conf needs is: 
    PerlRequire Journals::Trans
JournalsTrans parm1 parm2

    [download]
    I should probably file a bug on the Apache2::Module page.
[reply]
[d/l]
[select]
[reply]
[d/l]
[select]
        Sorry, it's there. Omission while trying to craft something legible. I've filed a bug on the mod_perl2 CPAN. Is epel the one true source for the mod_perl RPM? I'm torn as to whether to build my own RPM. I got 25% of the way there last night. It's been 20 years since I did that! I suppose I could try on my Ubuntu VM.
[reply]

In Section Seekers of Perl Wisdom