in reply to Re: Apache Server restart fails
in thread Apache Server restart fails

I checked if ModPerl::Registry was installed, and that is not the case. I am not sure if it was installed before. Anyway, when I try to install ModPerl::Registry in CPAN, it fails with the error message:
[ error] Unable to open /etc/apache2/ap_release.h: No such file or di +rectory [ error] Unable to determine server version, aborting. [ error] Please specify MP_APXS or MP_AP_PREFIX. Warning: No success on command[/usr/local/bin/perl Makefile.PL INSTALL +DIRS=site] 'YAML' not installed, will not store persistent state PHRED/mod_perl-2.0.5.tar.gz /usr/local/bin/perl Makefile.PL INSTALLDIRS=site -- NOT OK Running make test Make had some problems, won't test Running make install Make had some problems, won't install Could not read metadata file. Falling back to other methods to determi +ne prerequisites Failed during this command: PHRED/mod_perl-2.0.5.tar.gz : writemakefile NO '/usr +/local/bin/perl Makefile.PL INSTALLDIRS=site' returned status 256
It can't find some apache2 file ap_release.h. I remember seeing this error message before all these problems occurred though.

Replies are listed 'Best First'.
Re^3: Apache Server restart fails
by Anonymous Monk on Mar 02, 2012 at 14:50 UTC

    To install that module manually, you need to have the apache development headers installed. (I am not sure this is the cause of your problem, though)

    Anyway, it is frowned upon that you replaced your node's content in whole, especially after someone already replied to it.

      Sorry about that, I didn't see the reply until after I modified my reply. I am still trying to figure out what's wrong. Think I might try re installing everything.
Re^3: Apache Server restart fails
by Anonymous Monk on Mar 02, 2012 at 14:30 UTC

    "Perl-handling module" as in the Apache module that provides the PerlResponseHandler etc directives. That is, mod_perl. Anyway, I'm with zwon here that you either removed or disabled mod_perl by accident somewhere along the way.

      Yes, I apologize for not making that very clear.   I was speaking of Apache modules, which are loaded with the LoadModule directive in httpd.conf.   For some reason, Apache no longer thinks that it’s supposed to be loading this module, or it’s no longer successfully doing so.

      AFAIK, Apache’s architecture is to first load the various modules, effectively as extensions to its core, then to present each incoming configuration directive to each one of them.   If Apache “suddenly doesn’t know what you’re talking about,” it’s because a module, not the core, is what knew about it all along.