on 12-28-2009 2:09 PM
Hi,
In one of the SDN thread , it was mentioned (Markus Doehr) that we can install apache 2.2.x.
We are getting below error when we start apache, after content server installation.
httpd: Syntax error on line 54 of /apache/<sid>cs/conf/httpd.conf: API module structure 'sapcs_module' in file /apache/<csd>cs/modules/mod_sapcs2.so is garbled - expected signature 41503232 but saw 41503230 - perhaps this is not an Apache module DSO, or was compiled for a different Apache version?
We had used apache 2.2.14. Issue is that compilation is done with apache 2.2, and mod_sapcs2.so is having singnature equivalent to 2.0.
It looks like mod_sapcs file is available for apache 1.3 and apache 2.0 only and we can't use apache 2.2 at the moment.
LoadModule sapcs_module modules/mod_sapcs2.so entry is already available in httpd.conf file.
We have applied the note 514500, but no luck.
Please advise if you have any fix.
Thank you,
Thaslim
Apache 2.2.x is now supported by CS 6.40, as of a very recent CS patch. "The versions which are tested are Apache 2.2.8 and Apache 2.2.22." If you download the patch, the file mod_sapcs22.so has apache 2.2 support. I was able to download and compile httpd-2.2.22, get content server 6.40 running with it, this way on RedHat RHEL 5.7.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
For content server you need to have 64-bit compiled version of Apache. The Apache version available with OS installations are 32-bit. You need to build a 64-bit compiled version for respective OS.
Refer SAP note
664384 Generation info for Apache Web server for SAP Content Server
Hope this is useful.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> For content server you need to have 64-bit compiled version of Apache. The Apache version available with OS installations are 32-bit. You need to build a 64-bit compiled version for respective OS.
I doubt that this is the problem in this case, the module can be loaded in the first place so the bitness of the module and apache seems to be compatible.
I would rather say the original poster is right, the modules work only with Apache 2.0.
I'll try to reproduce.
Markus
Hello colleges
@deepakkori
No, i think our apache is 64-bit...
httpd -V
Server version: Apache/2.2.3
Server built: Oct 6 2011 12:11:58
Server's Module Magic Number: 20051115:3
Server loaded: APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture: 64-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
file /usr/sbin/httpd
/usr/sbin/httpd: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, stripped
@Markus Doehr
Unfortunately you are right, seems to SAP Content Server not support Apache 2.2.x
At the same time, I think it's wrong to leave the customer without the OS updates in part of Apache.
> Unfortunately you are right, seems to SAP Content Server not support Apache 2.2.x
> At the same time, I think it's wrong to leave the customer without the OS updates in part of Apache.
Apache 2.0 is still maintained so from a security perspective it's not an issue. However, you're basically right. Content server supportes IIS 7.x on Windows 2008 R2 as new operating system so it should consequently also support newer Apache versions. I'd open an OSS call.
Markus
Face the same problem on Apache/2.2.3 (from RedHat package)...
API module structure `sapcs_module' in file /<path>/mod_sapcs2.so is garbled - perhaps this is not an Apache module DSO
SAP Content Server version is 6.4 SP8
@Thaslim J: did you solve this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.