Processing commands for [EMAIL PROTECTED]:
> tag 269499 moreinfo
Bug#269499: apache-ssl: SSL log directives don't work?
There were no tags set.
Tags added: moreinfo
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
tag 269499 moreinfo
stop
On Wed, 1 Sep 2004, Rafael D'Halleweyn wrote:
> Package: apache-ssl
> Version: 1.3.31-5
> Severity: important
>
> The SSL log directives don't work for me, I only get a '+' in the logs.
>
> Looking at the source in src/modules/standard/mod_log_config.c, I see
> that the '
Function not implemented: mod_rewrite: could not create rewrite_log_lock
Configuration Failed
Package: apache-ssl
Version: 1.3.31-5
Severity: important
The SSL log directives don't work for me, I only get a '+' in the logs.
Looking at the source in src/modules/standard/mod_log_config.c, I see
that the '%{clientcert}c' log directive is actually handled by
log_connection_status since it app
(Mailing List Information, including unsubscription instructions are
located at the end of this message)
Greetings,
MindIQ is celebrating your success! Since 1986, we have assisted over
13,000 IT professionals by providing them the highest quality technical
training available. To thank you, we
Hi.
I have same problem, after a daily upgrade of my system, apache stopped
serve php-pages. I tested to remove httpd.conf and run dpkg-reconfigure
apache. And followed the README instructions in /usr/share/doc/.. for
"apache" and "php4", but without any luck. I have done alot of mixuring
by my
Processing commands for [EMAIL PROTECTED]:
> severity 269019 wishlist
Bug#269019: Please package mod_bandwidth 2.0.5
Severity set to `wishlist'.
> retitle 269019 Please package mod_bandwidth 2.0.5
Bug#269019: Please package mod_bandwidth 2.0.5
Changed Bug title.
> thanks
Stopping processing here
severity 269019 wishlist
retitle 269019 Please package mod_bandwidth 2.0.5
thanks
There are two modules called mod_bandwidth. You're reading the
documentation for the one we don't ship. Were it not now only picoseconds
before sarge releases, I'd add the new mod_bandwidth, but we're planning
on
On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote:
> Ok. I'll try to attach the index.php. Which config files would help?
All of them. I need to reproduce your environment here.
>
> Also, the same problem occurs no matter which .php file I try to view on
> the site. regular .html files work no problem
Processing commands for [EMAIL PROTECTED]:
> severity 269019 wishlist
Bug#269019: apache: mod_bandwidth does not work
Severity set to `wishlist'.
> retitle 269019 Please package mod_bandwidth 2.0.5
Bug#269019: apache: mod_bandwidth does not work
Changed Bug title.
> thanks
Stopping processing he
Additionally, 'apache2ctl status' still doesn't work:
host:/# apache2ctl status
Not Found
The requested URL /server-status was not found on this server.
_
Apache/2.0.50 (Debian GNU/Lin
On Wed, Sep 01, 2004 at 04:26:46PM +0200, Fabio Massimo Di Nitto wrote:
> On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote:
>
> > Yes. /etc/apache/httpd.conf has the line: Include /etc/apache/modules.conf
> >
> > and /etc/apache/modules.conf has the line:
> > LoadModule php4_module /usr/lib/apache/1.3/l
Processing commands for [EMAIL PROTECTED]:
> reassign 239364 apache-common
Bug#239364: apache: Suexec incompatible with php4-cgi
Bug reassigned from package `apache' to `apache-common'.
> merge 239364 69818
Bug#69818: apache: suexec not suitable for virtual host setup.
Bug#239364: apache: Suexec
Processing commands for [EMAIL PROTECTED]:
> severity 239364 wishlist
Bug#239364: apache: Suexec incompatible with php4-cgi
Severity set to `wishlist'.
> merge 239364 69818
Bug#69818: apache: suexec not suitable for virtual host setup.
Bug#239364: apache: Suexec incompatible with php4-cgi
Mismatc
On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote:
> Yes. /etc/apache/httpd.conf has the line: Include /etc/apache/modules.conf
>
> and /etc/apache/modules.conf has the line:
> LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
>
> Let me know what other info might be helpful. Could it have anything t
On Wed, Sep 01, 2004 at 10:20:13AM +0200, Fabio Massimo Di Nitto wrote:
>
> Please keep the bug number in CC.
>
> On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote:
> > > You need to enable the php4 module manually with something like:
> > >
> > > LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
>
Brian C wrote:
>
> looked around and saw that apache-mod-php4 was not installed. It seems
> to me that it used to be. So, I installed it and still no fix.
As a data point for PHP bugs, which frontend did you use to upgrade?
apt-get, dselect, aptitude?... I'm trying to hunt down under what
circums
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.4
> # Sorry, typo in bugnr
> tags 269290 - pending
Bug#269290: apache2-common: new default Include is too inclusive
Tags were: pending
Tags removed: pending
>
End of message, stopping pr
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.4
> tags 269290 + pending
Bug#269290: apache2-common: new default Include is too inclusive
There were no tags set.
Tags added: pending
>
End of message, stopping processing here.
Please
Dear Sir,
Our company owns pixadultcontent.com, a website selling adults contents for the web and electronic media.
Since we have decided to terminate this part of our activities by the end of 2004, we are currently offering our whole catalog at an exceptionel price:
- 852 Hardcore v
Package: apache2-mpm-worker
Version: 2.0.50-11
Severity: normal
Hello,
I activated apache2 using the NO_START=0 setting in
/etc/default/apache2. Then I set this back to 1.
Now stopping apache2 does not work:
Not starting apache2 - edit /etc/default/apache2 and change NO_START to
be 0.
At least
Please keep the bug number in CC.
On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote:
> > You need to enable the php4 module manually with something like:
> >
> > LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
> >
> > otherwise php4 isn't used at all.
>
> Such a line is in my modules.conf after us
Processing commands for [EMAIL PROTECTED]:
> tag 269377 moreinfo
Bug#269377: apache: Upgrade broke Apache and PHP
There were no tags set.
Tags added: moreinfo
> severity 269377 normal
Bug#269377: apache: Upgrade broke Apache and PHP
Severity set to `normal'.
> stop
Stopping processing here.
Ple
tag 269377 moreinfo
severity 269377 normal
stop
On Wed, 1 Sep 2004, Brian C wrote:
> Package: apache
> Version: 1.3.31-4
> Severity: important
>
>
> I just upgraded Apache (among other things.) Now my site, which runs
> b2evolution (serving up a .php index file), does not display and
> constantly
Package: apache
Version: 1.3.31-4
Severity: important
I just upgraded Apache (among other things.) Now my site, which runs
b2evolution (serving up a .php index file), does not display and
constantly generates new windows with nothing in them. (It's like an
infinite loop.)
Or, if Mozilla/your br
On Tue, 31 Aug 2004, Ivan Dimitrov wrote:
> Hello
> I've translated apache-1.3.31-1 debian/po/ file to Bulgarian, it is called
> bg.po, please reply to me where should I send the file, as I'm not subscribed
> to this list.
>
Please send it to me or to the list.
Thanks for your translation effor
26 matches
Mail list logo