in reply to Re^2: Prototype mismatch using mod_perl
in thread Prototype mismatch using mod_perl

If you ask me, it sounds like your OS released a new version of mod_perl that doesn't play well with your existing scripts. So, if that's the case, what does that mean? Maybe there's a problem with your distro's latest release of mod_perl. I'm guessing we're talking about Linux so I'd start by checking out my distro's bug tracker to see if anyone else is having mod_perl issues. Maybe you got bumped from mod_perl 1.xx to mod_perl 2.xx which is very different.

If the above is wrong, take a close look at what changed in your environment. Whatever it was that changed is most likely the culprit.

In a pinch, if none of the above helps, you might try a manual build of mod_perl to see where the problem lies. If your build works, then the distro has a problem, if not, you should at least get some build errors to point you in the right direction.

Of course, if you're running windows, very little of the above may apply. But I'd still look for a recent mod_perl update to be the problem.

  • Comment on Re^3: Prototype mismatch using mod_perl

Replies are listed 'Best First'.
Re^4: Prototype mismatch using mod_perl
by AlfaProject (Beadle) on Aug 09, 2011 at 11:14 UTC
    I found that the developers of mod_perl don't support anymore ModPerl::PerlRun
    That was the answer to the guy that had same problem as me.
    https://bugzilla.mozilla.org/show_bug.cgi?format=multiple&id=124591
    Not fun at all, that thing working on our production server.