Apache loading error

[santhosh kurian]

Hi all,
When am starting apache in hp_ux 11i i am getting following error
httpd: Syntax error on line 56 of /usr/local/apache/conf/httpd.conf: Cannot load /findna/aml/lib/mod_echo.so into server: Invalid argument

in httpd.conf file i am trying to load our library mod_echo.so.Can somebody help me to solve this problem

[Mridul Shrivastava]

what's the version of Apache ?

Have any changes, like installation of new Apache, being done ?

Could you please post the error_log and swlist -l product output...

[santhosh kurian]

hi,
The apache version is 2.2.4.I had a tar file for apache I untared it and configured using
./configure --prefix =/usr/local/apache \
--enable -rewrite=shared \
--enable --speling =shared
then
make
and Make install
And about the error logs I didnt find any error_logs in logs directory amd in swlist I can find only Hp-UNIX based apache 2.0.54 .That wont support our application as such because our application is 32 bit.

[Mridul Shrivastava]

1. You have a non HP supplied Apache Server version 2.2.4 installed.swlist shows you also have an HP installation of Apache 2.0.54 .


2. While multiple versions of Apache can be installed on the same machine, they cannot both be started to listen to port 80 on the same IP address and they cannot share pid and error_log files.


While I believe that you may have had a working Apache server at one time, it appears that now you have a mix of Apache server software installed on this system. My recommendation is that you remove both Apache servers completely and reinstall an HP distribution of the software. This software and the documentation for it can be found at http://software.hp.com

[santhosh kurian]

HI,
But port no in Hp-based apache confguration file is 80 and other one is 1555.Will it create problem

[Ralph Grothe]

Hi,

normally you can run as many httpd servers as you wish, as long as each of them is servicing a different port.
But to come back to your syntax error.
I suspect that your LoadModule statement for your mod_echo either refers to a wrong path,
or that the wanted module isn't present in that path.
What does your LoadModule statement look like?
e.g. what does this print (please, adapt the path to the httpd.conf file according to your installation)?

# sed -n 56p /usr/local/apache/conf/httpd.conf

Any relative path displayed (one that doesn't start with a slash) refers to a starting point according to your ServerRoot.
In the showed path you must find the binary of mod_echo.so (or a symlink etc.)

[santhosh kurian]

Thanks for ur reply
But u r aasumption is wrong .At 56 th line i am loding library like this
LoadFile /findna/aml/lib/mod_echo.so

and this library is present in that directory also ,there is no problem with the path as well

[Ralph Grothe]

Ok, but you nevertheless still seem to have a syntactical error prevelant.
Otherwise an "apachectl configtest" would not throw an error like the one you cited:

httpd: Syntax error on line 56 of /usr/local/apache/conf/httpd.conf: Cannot load /findna/aml/lib/mod_echo.so into server: Invalid argument

Somehow the apache pre-flight syntax checker is tripping over the strange path /findna/aml/lib/mod_echo.so which it seems to parse as an invalid argument within a mod_echo context.

Have you split up your httpd.conf to other external files that you pull in somewhere else by an Include?

Besides, what is you ServerRoot assigned to?

e.g.

grep ^ServerRoot /usr/local/apache/conf/httpd.conf


Maybe some /findna/aml therein?

[santhosh kurian]

Now I am getting the following error
httpd: Syntax error on line 56 of /usr/local/apache/conf/httpd.conf: Cannot load /findna/aml/lib/mod_echo.so into Server:Unresolved External

what is this unresolved external,I am not able to understand.Plz hepl me asap

[Ralph Grothe]

Hm, do you really require mod_echo?
As I haven't heard of it before I was looking up at the Apache site what its use would be.

http://httpd.apache.org/docs/2.0/mod/mod_echo.html

There its (maturity) status still is designated as "Experimental".
To me it sounds as if this kind of echo server implementation is only required by a few web developers.
Do you need to satisfy such a clientele?
If not, I would simply comment the loading of that module out in your httpd.conf file
so that you for the time being at least you get the webserver started.
Then if someone comes complaining about a missing feature you still could subscribe to the Apache Users' or Developers' mailing lists and post your problem there.
(maybe mod_echo even runs one of its own?)
In the past I have experienced that the developers of open source software very vividly follow their software's mailing lists, and are very keen on receiving bug and problem reports, and are very willing to help overcome any problems of their users.

Btw, here's how they explain "experimental" at the Apache site:

Experimental
"Experimental" status indicates that the directive is available as part of the Apache kit, but you're on your own if you try to use it. The directive is being documented for completeness, and is not necessarily supported. The module which provides the directive may or may not be compiled in by default; check the top of the page which describes the directive and its module to see if it remarks on the availability.