> > Alternatively, if you can run your server in single-process mode and > > come up with a repeatable series of steps that cause the error, you > > can work back from the point where you saw the error until you find > > the offending code. > > > Yes, httpd -X is a good idea. I should have thought of that > before. I'll give that a go and report back to the list.
Our site only has three mod_perl pages, and I've cycled through all of them with the webserver, trying to model behaviour that goes through the different execution paths, in single process mode but still been unable to repeat the error. I'll keep on trying but I'm not sure if the issue is a badly behaved CPAN module. I've been through my $HOME/.cpan/build directory for modules I've installed in the last few months, again I couldn't see any setgid references even though I was now searching through .xs files also. I should point out that sometimes in the past I've seen the error in our Website::Proxy module. This module is simply a url mapping module which would take a url like /research/user/search and map that to the module Website::User::Search and it would do a eval "use $module;" (where $module is untained) before calling the constructor and delegating construction of the page. I saw the same error at that eval statement also. Again this was sporadic, but here I would have been simply compiling the code of modules rather than running them (save for code in BEGIN blocks etc.). What I found was if I changed my Website::Proxy module to load all modules on webserver startup (i.e. in it's own BEGIN block) rather than on demand then the eval errors there stopped. This seems to imply that the interpreter is getting into a confused state after some continued use. Does anyone have any other suggestions? =ANYTHING+BELOW+THIS+LINE+WAS+ADDED+AFTER+I+HIT+SEND= ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------
