Hello,
Yesterday I upgraded my Tamino 4.1.4.1 to 4.1.4.5. And after applying that, Apache server fails. I have been using the apache server without problems with 4.1.4.1. According to what I understand, the update kit 4.1.4.5 contained some Apache modules. But the installation process didn’t ask the ApaacheRoot directory. Incidentally my Apache is not on the default location. I suspect this has caused the mishap.
Some error messages from the Apache error log below:
[Thu Jul 22 12:23:17 2004] [warn] child process 1367 still did not exit, sending a SIGTERM
[Thu Jul 22 12:23:17 2004] [warn] child process 1368 still did not exit, sending a SIGTERM
[Thu Jul 22 12:23:22 2004] [error] child process 1367 still did not exit, sending a SIGKILL
[Thu Jul 22 12:23:22 2004] [error] child process 1368 still did not exit, sending a SIGKILL
[Thu Jul 22 12:23:39 2004] [notice] caught SIGTERM, shutting down
[Thu Jul 22 12:46:09 2004] [notice] Apache/2.0.48 (Unix) configured – resuming normal operations
[Thu Jul 22 19:08:21 2004] [notice] child pid 1362 exit signal Segmentation fault (11)
[Thu Jul 22 19:08:29 2004] [notice] child pid 1363 exit signal Segmentation fault (11)
I did “strace” and the output below:
select(0, NULL, NULL, NULL, {0, 160000}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = ? ERESTARTNOHAND (To be restarted)
— SIGCHLD (Child exited) —
select(0, NULL, NULL, NULL, {0, 790000}) = 0 (Timeout)
fork() = 1459
wait4(-1, [WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV], WNOHANG|WUNTRACED, NULL) = 1355
gettimeofday({1090565314, 144687}, NULL) = 0
write(7, “[Fri Jul 23 09:48:34 2004] [noti”…, 87) = 87
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = ? ERESTARTNOHAND (To be restarted)
— SIGCHLD (Child exited) —
select(0, NULL, NULL, NULL, {0, 630000}) = 0 (Timeout)
fork() = 1460
wait4(-1, [WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV], WNOHANG|WUNTRACED, NULL) = 1356
gettimeofday({1090565317, 144691}, NULL) = 0
write(7, “[Fri Jul 23 09:48:37 2004] [noti”…, 87) = 87
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
wait4(-1, 0xbffed180, WNOHANG|WUNTRACED, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0} ?unfinished …?
Is there anybody else out there who is also suffering from a similar problem as me?
Can anybody please help me?
Best regards,
Gopal.
Hello Gopal,
I assume you are running Tamino on UNIX (really doesn’t matter). The only Apache modules I noted in Update 5 are Tamino’s 32-bit (ApacheModuleIno.so) & 64-bit (Apache2ModuleIno.so) Apache modules. These modules are installed in the Tamino directory structure and do not get loaded or copied to the Apache directory structure. So having your Apache installed in your own site specific directory structure would have no effect with Update 5.
If you feel that Tamino is the cause of the problem, comment out the call to the Tamino Apache module (Include “/usr/SAG/ino/v4211/X_Port/Apache2/TaminoApache.conf”) in your Apache httpd.conf. If the problem continues then it can not be a problem with Tamino. The “Include” is the only link between Apache and Tamino at Apache startup time.
But, if the problem does disappear, uncomment the include for Tamino (noted above) and confirm that the problem is reproducable and still exists.
If this does confirm a problem (with Tamino, Update kit 5 and Apache) I would open a support request with Software AG?s Customer Support to get this fixed as the problem with the Apache2Module.Ino.so (and repairing it) is beyond the scope of this forum. Normally if the problem was with the Apache2ModuleIno.so module I would expect an error in the Apache error_log to point to that and not what you see. Strange.
Rob