| Summary: | apache segfaults due to apr/apr-util mismatch with apache modules | ||
|---|---|---|---|
| Product: | [OLD] Docs on www.gentoo.org | Reporter: | Nick <nick> |
| Component: | Other documents | Assignee: | Docs Team <docs-team> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | jakub |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://http://www.gentoo.org/doc/en/apache-troubleshooting.xml#doc_chap3 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Nick
2007-07-29 18:06:54 UTC
Can you try it again and find which is a real solution? Either removing the older versions or all versions; we have to know which actually does the job before we could include such a suggestion in the guide. As noted 'remove all versions and reinstall' works, ie. real solution;
1. remove all versions of apr, apr-util & apache
rebuild apr, apr-util, apache & php
It might work to do;
2. emerge -P apr apr-util
rebuild apache & php
If someone finds themself in this position with apache segfaulting, as I did, they might like to try the 2nd suggestion (which is slightly quicker) when rebuilding the tool stack. If apache still segfaults, they will have to resort to the 1st, as I did.
I think part of the problem is that apr & apr-util are at version 1.2.8 and in a new slot, whereas the instructions insist on version (slot?) 0*.
My LAMP stack now works, and I don't intend to break it just to see if pruning is effective in fixing it. I would have to;
remove apr, apr-util, apache & php
install old versions of apr, apr-util, apache & php
upgrade apr, apr-util, apache & php
* hope it breaks *
Then try to fix it with;
emerge -P apr apr-util
rebuild apache & php
At this point my LAMP stack might still be broken: I don't think so.
Summary:
1. real solution -- Tested & Verified.
2. update of existing instructions, that is more likely to work with current
versions of tool stack -- impractical for me to test.
This sounds like duplicate of Bug 182453 (not much useful info posted here) and I don't think it should be documented anywhere. *** This bug has been marked as a duplicate of bug 182453 *** |