Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Thu, Mar 15, 2001 at 02:03:37PM -0600, Nathan E Norman wrote: On Thu, Mar 15, 2001 at 09:32:23AM +0100, Paul Slootman wrote: On Wed 14 Mar 2001, Dimitri Maziuk wrote: Hmm, interesting... Why tf did I install apache-perl in the first place? Because the combination apache + mod-perl had/has(?) a pretty bad memory leak? Which was why apache-perl was created in the first place. Is this an issue with certain versions of apache mod_perl? Do you know if it's been resolved? It has been 'somewhat' resolved, in both potato and unstable (I -think-). The problem is that a lot of libraries are not good about freeing memory when they expect the program to exit, and thus when they restart they leak a bit. -- Daniel Jacobowitz Debian GNU/Linux Developer Monta Vista Software Debian Security Team I am croutons!
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Wed 14 Mar 2001, Dimitri Maziuk wrote: Hmm, interesting... Why tf did I install apache-perl in the first place? Because the combination apache + mod-perl had/has(?) a pretty bad memory leak? Which was why apache-perl was created in the first place. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Thu, Mar 15, 2001 at 09:32:23AM +0100, Paul Slootman wrote: On Wed 14 Mar 2001, Dimitri Maziuk wrote: Hmm, interesting... Why tf did I install apache-perl in the first place? Because the combination apache + mod-perl had/has(?) a pretty bad memory leak? Which was why apache-perl was created in the first place. Is this an issue with certain versions of apache mod_perl? Do you know if it's been resolved? -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Inc. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgppWMJzSey7e.pgp Description: PGP signature
So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
Ok, I'm not in the mood for flamefests today so here's a serious question: apache here fails to start with (this is from error.log) [Wed Mar 14 12:36:15 2001] [warn] pid file /var/run/apache.pid overwritten -- Unclean shutdown of previous Apache run? Apache.pm failed to load!. Ok, here's the list of Apache.pm's I have: odyssey:/# odyssey:/var/log/apache# grep Apache.pm /var/lib/dpkg/info/*.list /var/lib/dpkg/info/apache-perl.list:/usr/lib/perl5/5.005/i386-linux/Bundle/Apache.pm /var/lib/dpkg/info/apache-perl.list:/usr/lib/perl5/5.005/i386-linux/Apache.pm /var/lib/dpkg/info/perl-modules.list:/usr/share/perl/5.6.0/CGI/Apache.pm Questions: 1. which of these fails to load? 2. where is that configured? 3. where is that documented? (I've already seen /usr/doc/apache-perl thank you) TIA Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) I'm going to exit now since you don't want me to replace the printcap. If you change your mind later, run -- magicfilter config script
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Wed, Mar 14, 2001 at 01:23:02PM -0600, Dimitri Maziuk wrote: Ok, I'm not in the mood for flamefests today so here's a serious question: apache here fails to start with (this is from error.log) [Wed Mar 14 12:36:15 2001] [warn] pid file /var/run/apache.pid overwritten -- Unclean shutdown of previous Apache run? Apache.pm failed to load!. Ok, here's the list of Apache.pm's I have: odyssey:/# odyssey:/var/log/apache# grep Apache.pm /var/lib/dpkg/info/*.list /var/lib/dpkg/info/apache-perl.list:/usr/lib/perl5/5.005/i386-linux/Bundle/Apache.pm /var/lib/dpkg/info/apache-perl.list:/usr/lib/perl5/5.005/i386-linux/Apache.pm /var/lib/dpkg/info/perl-modules.list:/usr/share/perl/5.6.0/CGI/Apache.pm Questions: 1. which of these fails to load? 2. where is that configured? 3. where is that documented? (I've already seen /usr/doc/apache-perl thank you) /usr/share/doc/apache-perl is the documentation for the apache-perl package (apache with perl linked in, not as a module). Have you tried running apache (not apache-perl) and loading mod_perl? It looks to me like you've got some problem caused by the prel 5.6 upgrade. I'll see if apache + mod_perl works here and report back. Luck, -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Inc. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpvvQFMmq1Bt.pgp Description: PGP signature
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Wed, Mar 14, 2001 at 02:17:08PM -0600, Nathan E Norman wrote: ... Have you tried running apache (not apache-perl) and loading mod_perl? It looks to me like you've got some problem caused by the prel 5.6 upgrade. Hmm, interesting... Why tf did I install apache-perl in the first place? I purged old apache-perl with --force-depends to get a clean slate and installed apache. Apacheconfig is still b0rken (there's a full output in one of my previous posts if anyone's interested) so I edited config files and finally got apache to run. The next update that runs apacheconfig will presumably break it again, but that's way better than rebooting your box and finding out that apache won't start anymore. Thanks Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) I'm going to exit now since you don't want me to replace the printcap. If you change your mind later, run -- magicfilter config script
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Wed, Mar 14, 2001 at 03:39:53PM -0600, Dimitri Maziuk wrote: On Wed, Mar 14, 2001 at 02:17:08PM -0600, Nathan E Norman wrote: ... Have you tried running apache (not apache-perl) and loading mod_perl? It looks to me like you've got some problem caused by the prel 5.6 upgrade. Hmm, interesting... Why tf did I install apache-perl in the first place? I purged old apache-perl with --force-depends to get a clean slate and installed apache. Apacheconfig is still b0rken (there's a full output in one of my previous posts if anyone's interested) so I edited config files and finally got apache to run. Well, that's good :) Perhaps you want to use RCS or CVS to track config changes ... The next update that runs apacheconfig will presumably break it again, but that's way better than rebooting your box and finding out that apache won't start anymore. So don't let apacheconfig make changes! Always answer n to thje prompt. FWIW I can't get stock apache from testing/unstable to play nice with mod_perl. Investigating further ... -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Inc. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpKJ06YsiPqU.pgp Description: PGP signature
