in reply to Re^3: Invalid Command 'PerlModule' perhaps misspelled or defined by a module not included in the server configuration
in thread Invalid Command 'PerlModule' perhaps misspelled or defined by a module not included in the server configuration

What would be a command to run mod_perl in apache. I used LoadModule but that seems to be already running. I'm trying to install RT.
  • Comment on Re^4: Invalid Command 'PerlModule' perhaps misspelled or defined by a module not included in the server configuration

Replies are listed 'Best First'.
Re^5: Invalid Command 'PerlModule' perhaps misspelled or defined by a module not included in the server configuration
by jethro (Monsignor) on Aug 19, 2010 at 23:19 UTC
    You might enable the server info module, see http://httpd.apache.org/docs/2.2/mod/mod_info.html. After enabling it, looking at http://localhost/server-info will list all installed modules and any commands enabled by the module.
      I tried adding a server info module on my apache2.conf file. But the problem still persists. I cannot laod the localhost server info page, neither can i find how many modules are enabled in the server. Is there any other place other than this and mod_perl.so -> which i cannot find, can i see for the perl modules installed in the server. The error says that My webserver need to be configured to "run" mod_perl handler. My config file contains a PerlHandler and a PerlResponse Handler required to initate and run the perl_module process. Do you think its a mistake in directing the root folder of the virtual host i created. I am running on port 443, as port 80 returned a error. Thanks for your prompt replies. I appreciate it.

        Some of what you are saying is somewhat cryptic, for example "Do you think its a mistake in directing the root folder of the virtual host i created". No idea what you mean by that. Also you say port 80 returned an error. What does the error message say?

        To find out which modules get loaded by apache, start it with

        strace -f -o /tmp/traceoutput /etc/init.d/apache2 start

        Note you will have to do "/etc/init.d/apache2 stop" from a second terminal as the strace will not stop and will not react to CTRL-C

        Search /tmp/traceoutput for the module you load, you should see something like this for mod_perl:

        31503 open("/usr/lib/apache2/modules/mod_perl.so", O_RDONLY) = 5 31503 read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\314\0" +..., 512) = 512 ... 31503 open("/usr/lib/libperl.so.5.8", O_RDONLY) = 5

        The same goes for the other modules like the server-info module. You can look through the file with grep, less (less has a nice search function) or any editor

        Some general hints: 1) Try to make one thing work before going to the next. I.e. first check that your apache serves a simple html page to your browser. If that works, get a simple module like server-info running. Only when you can see the output of that module with your broswer try to get mod_perl working (with the help of apaches mod_perl docs). Only then look at rt and try to make that work

        2) To check if a configuration file was loaded at all, insert a syntax error. apache2 should complain.

        3)Always look at the logfiles. Set apaches LogLevel to debug to get more information

        4) If all fails, redo. If nothing helps, remove everything you have done and reinstall apache and mod_perl. If possible, install from your distributions repository instead of compiling yourself, mod_perl should be in there as well as apache. Advantage is that the repository also installs sensible config-files. Document every step you do and if you hit a block, ask at a apache forum or mailing list which step you forgot.

        No, neither of those are related to mod_perl not being installed or configured to run ... check the logs, check the docs