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

[download]

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.

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.