FW: silent failure still a problem in mod_perl 2.0?
Kyle Dawkins writes: > I'd betcha your problem is almost certainly caused by your use of DSOs. If > you *really* want to prune your system down to see where your bug is, then > build apache and mod_perl statically. There was a very well-known bug that > caused DBI to segfault if it was run under a DSO. Please rebuild your > binary and then let us know if that was the problem. I just ran into the silent-failure problem again today, when a sysadmin unknowingly upgraded glibc underneath mod_perl built as a DSO. Unfortunately, it was on a production system; fortunately, it was not on a very important production system, and rebuilding the tools fixed the problem. In anticipation of the postmortem meeting, I'm trying to find out if this problem still exists in mod_perl 2.0. Websearches have been fruitless; any pe[a]rls of wisdom from the list? Charlton
silent failure still a problem in mod_perl 2.0?
Kyle Dawkins writes: > I'd betcha your problem is almost certainly caused by your use of DSOs. If > you *really* want to prune your system down to see where your bug is, then > build apache and mod_perl statically. There was a very well-known bug that > caused DBI to segfault if it was run under a DSO. Please rebuild your > binary and then let us know if that was the problem. I just ran into the silent-failure problem again today, when a sysadmin unknowingly upgraded glibc underneath mod_perl built as a DSO. Unfortunately, it was on a production system; fortunately, it was not on a very important production system, and rebuilding the tools fixed the problem. In anticipation of the postmortem meeting, I'm trying to find out if this problem still exists in mod_perl 2.0. Websearches have been fruitless; any pe[a]rls of wisdom from the list? Charlton
RE: Any known good configuration for mod_perl DSO?
In response to my question, Ged Haywood pointed me at a message from Chip Turner, reproduced here in part: > When it comes to perl and mod_perl, we've been working to try to make > sure it works reliably from RPMs. RH 7.3 should work well out of the > box, as should 7.2, once all errata applied. The rest of this thread > points out a few issues, though, but I think that tends to be issues > with other perl modules that have shared library components. If you > (or anyone else!) have specific failures or test cases you've seen, > though, I'll look into it and see if it is something we can fix. That "should" is a big big word, as I came across Mr Turner's message in a search of the list archives -- I'm currently working with a RedHat 7.2 box with all errata applied. All Perl-related RPMs were supplied by RedHat. And I get silent failure in the form of segmentation faults. So that's why I asked my original question. Can I expect that if we upgrade our web servers to RedHat 7.3, we'll be rid of the segfault problem? Or am I looking at rolling my own RPMs or installing from source RPMs? My suspicion, confirmed by Mr Turner, is that this is tied directly to shared libraries and toolchains, and so I suspect further that the problem will go away if I build everything from scratch using source RPMs. In the meanwhile, thanks to the people who have offered tips on building from source RPMs. Right now, it looks like this is the way we're going to go. And finally, thank you to the people who recommended (many in private messages) ditching RPMs altogether and installing from source, but unfortunately that's not an option, as I thought I had made clear in my initial post. One of the reasons we're using RPMs to handle configuration management is that we have several redundant servers in production and several servers for development use, and it's important that the configuration on each server be identical. It's also important that, if we add a new server to either group, we can produce an identical configuration to the development and production clusters. Charlton
Any known good configuration for mod_perl DSO?
Hello collective wisdom, I have the task of making Apache, mod_perl, and HTML::Mason work together under RedHat. I know this is a problem; the most frequently recommended solution that I've found is to build everything from scratch and link it all together, without using DSOs. However, my constraints are that all configuration management must be handled using RPMs, because we have a multitude of web servers that must all be maintained in parallel. My order of preference is for using downloadable binary RPMs, followed by using SRPMs and building from scratch, and finally followed by rolling my own RPMs. So I have a couple of questions that I'm currently researching, and if anybody here knows the answers, I'd be grateful to hear them: First, is there a known good binary RPM configuration, a combination of mod_perl and apache RPMs, from RedHat or another vendor that doesn't suffer from the silent-segfault problem? Second, is it possible that building from source RPMs would prevent the problem? Occasionally I've seen problems like this arise due to differing versions of the toolchain, and building from source RPMs would ensure that the same toolchain was used to build all of the components. If I find answers to these questions elsewhere before I receive answers from this list, I'll follow up to myself and share the wisdom. Thanks, Charlton -- Charlton Wilbur [EMAIL PROTECTED]
