Re: Configuring mod_perl on Debian
My guess is that some error message is terminating your headers before the
content-type is sent. stdout and stderr get buffered independently so the
stderr can come out of your script first, even if it's generated later in
your code.
* Set $|=1; as the first thing you do in your test script, immediately
followed by your content-type header. This turns of buffering of your IO
streams.
* look at what's in your error logs, though this might not be much until
you set $|.
* Don't use your browser to test what's going on. go lower level. If
you're not comfortable doing this with telnet, use `lynx -mime_header` or
`Get -Se`, although be aware that both of these can mung the output a
little, as does apache.
I've gotten debian's mod_perl running on multiple machines under both
potato and woody.
You miss most of the advantage of debian's package management if you start
building core components independently. Debian looks after you pretty
well, but it's a bit of an all or nothing affair. ie it's worth a little
effort to stick with the debian packages if you can.
Andrew
On Mon, 27 May 2002, Ian D. Stewart wrote:
> Date: Mon, 27 May 2002 14:22:02 -0400
> From: Ian D. Stewart <idstewart@compuvative.com>
> To: Ian D. Stewart <idstewart@compuvative.com>
> Cc: Eric <eric@taedium.net>, modperl@perl.apache.org,
> debian-user@lists.debian.org
> Subject: Re: Configuring mod_perl on Debian
>
> Well, I haven't had any better luck with the debian package but I have
> gotten Apache and mod_perl running by building from source.
>
>
> Thanx for all the help,
> Ian
>
>
> On 2002.05.27 13:06 Ian D. Stewart wrote:
> > On 2002.05.27 12:59 Eric wrote:
> >> On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart wrote:
> >> > On 2002.05.27 11:43 Lucas M. Saud wrote:
> >> > >maybe you can try a "chmod 755" in the script...and check the perl
> >> > >path in first line of the script...and set the directory
> >> permission
> >> to
> >> > >777....
> >> >
> >> > Tried all of those. Still no good.
> >> >
> >> > I've downloaded the source for both Apache and mod_perl, and will
> >> be
> >>
> >> > building from scratch. If that works, that I well chock it up to a
> >> > debian packaging/configuration issue.
> >> >
> >> >
> >> > Thanx for the feedback,
> >> > Ian
> >>
> >> You said you were using woody (testing)?
> >>
> >> I haven't been following your problems, but I was able to get
> >> apache/mod_perl running on debian with little fuss. What packages
> >> have
> >> you tried? As a point of reference, these are the apache packages I
> >> have installed:
> >>
> >> % dpkg -l '*apache*' | grep "^i"
> >> ii apache-common 1.3.24-3 Support files for all Apache
> >> webservers
> >> ii apache-ssl 1.3.24.2+1.47- Versatile, high-performance HTTP
> >> server with
> >> ii libapache-mod- 1.26-3 Integration of perl with the
> >> Apache
> >> web serv
> >> ii libapache-requ 0.33-1 Generic Apache Request Library
> >>
> >> Eric
> >
> > Eric,
> >
> > Here is what I have:
> >
> > dpkg -l '*apache*' | grep '^i'
> > ii apache-common 1.3.24-3 Support files for all Apache
> > webservers
> > ii apache-perl 1.3.24-2-1.26- Versatile, high-performance HTTP
> > server with
> > ii libapache-mod- 1.26-3 Integration of perl with the Apache
> > web serv
> >
> > Not sure where our configurations are different (I note you do not
> > have apache-perl installed), but after I installed apache-perl, I had
> > to copy /etc/apache/httpd.conf to /etc/apache-perl/httpd.conf, and
> > make quite a few changes by hand.
> >
> >>
> >>
> >> p.s. you shouldn't ever set a cgi directory to be world-writable
> >> (777).
> >
> > Yeah. That struct me as being a bit off...
> >
> >
> > Thanx,
> > Ian
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: