On Thu, Jul 04, 2002 at 01:46:18PM +0200, Oliver Bleutgen wrote:
Hi,
On Wed, Jul 03, 2002 at 12:02:47PM +0200, Oliver Bleutgen wrote:
Strictly speaking those module updates should not have been necessary.
I doubt that, from my own experiences.
Well I can not state that it works for all ~60 modules -- but for mod_php4 and mod_perl it does.
Peter,
I have a small logical problem with that. You claim that the apache-1.3.19-115.rpm would run with modules of the original suse distribution, which is apache-1.3.12-120.
Oliver, perl and php modules from stock 7.0 do indeed not work with the latest update (segfaults upon requests just as you described)
Then, if this is so, why did SuSe release updated versions of all apache modules, when it first made the jump to apache-1.3.19-30? (that was the new version at that time, I did some searching).
If the modules should work with apache 1.3.19-115 as you say, why shouldn't they have worked with apache 1.3.19-30? Either the update of the modules at that time was unnecessary, or it's still necessary today. (Or, there's some deep voodoo involved which makes the newer apache 1.3.19 "more compatible" with 1.3.12 modules than the old one - plausible?)
It might be that we knew that updated modules were necessary, but the knowledge got lost.
Well, at least we have rpm --changelog: [...] As I wasn't affected from the above bug, I didn't upgrade.
Understandable.
If I am right, I'd think SuSE should take a look at their testing procedures, because they issued an update package which won't work on a stock install. And this is the first configuration on which I'd expect tests to be run.
We are currently taking a look, in reaction to these problems. (However, the situation in question is, as we see it, *not* the first configuration, that needs to be tested -- we expect systems being up to date with security updates to be more important/frequent.)
Perhaps it wasn't notified because apache will startup, but not work.
Good guess, but our tests do fetch pages from apache, too ;^} But all modules were up to date in our tests.
Anyway, it's plausible that this incidend is caused mainly by growing problems and pains with aging versions of a distribution.
I would love to know the exact reason.
In summary, two thing come to mind which would have helped me:
- proper rpm dependencies well, I can install rpms, that's it, so I've no idea if this is doable in all cases.
- A hint in the advisory to also install the newer apache modules.
Agreed.
Ok, thanks for taking the time to answer my ramblings ;-).
No, thanks for your patience ;) Peter -- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...