 Relationships |
|
| Anonymous | Login | 2024-04-27 17:33 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0003922 | [apache2] upgrade | crash | always | 2009-09-28 17:59 | 2010-11-07 13:48 | ||
| Reporter | ois_unix | View Status | public | ||||
| Assigned To | ihsan | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | closed | ||||||
| Summary | 0003922: After upgrade, cannot load libexec/mod_include.so | ||||||
| Description |
After upgrading to Apache 2.2.13, the Apache service refused to start. The workaround was to comment out the mod_include module in httpd.conf, but the real problem seems to involve the module file itself. The full error message reported was: "Executing start method ("/var/opt/csw/svc/method/svc-cswapache2 start") httpd: Syntax error on line 77 of /opt/csw/apache2/etc/httpd.conf: Cannot load /opt/csw/apache2/libexec/mod_include.so into server: ld.so.1: httpd: fatal: relocation error: file /opt/csw/apache2/libexec/mod_include.so: symbol ap_escape_html_2: referenced symbol not found |
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0006765) skayser (administrator) 2009-09-28 21:33 |
Thanks for reporting. Do you still see the problem after a "svcadm clear cswapache2"? I have seen a similar problem during upgrade, but a subsequent "svcadm clear cswapache2" solved it for me. See https://bugzilla.redhat.com/show_bug.cgi?id=491567#c3 [^] for a similar problem description on Fedora. On their platform, the old apache version was still running and - on reload - tried to load the updated mod_include, which relied on a function that was only provided by the new apache version. Seems to me as if we ran into the same issue. From a packaging perspective, it might be best to display a big warning message on an upgrade between the two affected versions. A forced restart could sound tempting also, but i wouldn't want to force a restart on a user (after all apache is still functional while running, the issue only seems to get triggered on reload). |
|
(0008438) bwalton (administrator) 2010-11-07 13:48 |
Closing due to lack of response from reporter and age. New version is out now. |
| Copyright © 2000 - 2008 Mantis Group |  |
