Apache error logs

[tash S]

Hi All,


I have three *sl share library on HP-UX 11i like:

aaa.sl
bbb.sl
ccc.sl

The result of 'what' command for *sl are like

----------------------------
aaa.sl
xxx for Web [222] (04/10/01_01:11:01)
bbb.sl
xxx for Web [222] (04/10/01_01:11:01)
ccc.sl
xxx for Web [222] (04/10/01_01:11:01)
------------------


The error_log (Apache) is like:

-------------------------------
[Tue Apr 17 19:46:27 2007] [notice] Apache/2.0.52 (Unix) test/[001] configured -- resuming normal operations
-------------------------------


The err_log of Apache shows '001' not '222'
The 001 is actually for old library.

If someone knows the reason, let us know.

The Apache try to get the 'what' command internally and get the result.
Is this correct?

Thanks,

[Matti_Kurkela]

No, Apache is definitely *not* running the "what" command or doing anything similar internally. It has a completely different mechanism for building up the message shown in the error_log.

"what" simply searches inside the binaries for strings beginning with "@(#)". This is what the revision control system uses as a sign for auto-embedded revision information in the source files (and the resulting binaries).

"Apache/2.0.52 (Unix) test/[001]" comes from the ServerTokens system in the Apache server. The first parts are created by the core server, but a module can add some information to ServerTokens using the Apache module API.
This happens when the module uses the ap_add_version_component() function.

I think you should check the source code of your module: you'll probably find that instead of using some form of the version number auto-embedding, the string "test/[001]" is hardcoded to the module and nobody has remembered to update it since the first test version.

Search the source code for "ap_add_version_component" to find the location that needs updating.

MK

[Ashok Arun Prakash K]

Hi,

Did you try restarting Apache after you have got the new version of the Libraries in place?

Please try doing that.. this may help!

[Tony Abo]

Double check that the LoadModule directives in httpd.conf are loading the libraries from the path that you think they're in. Maybe httpd.conf is pointing to older versions from some other directory.

You might also try (on eaqch library):
strings aaa.sl | grep '001'

That will tell you of the 001 string is actually still embedded in the new libraries.