Expired
Please read bug report and suggested fix supplied in previous message.
On 9/22/07, Launchpad Janitor <[EMAIL PROTECTED]> wrote:
> [Expired for apache2 (Ubuntu) because there has been no activity for 60
> days.]
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95
[Expired for apache2 (Ubuntu) because there has been no activity for 60
days.]
--
Apache2 Fails to install/start
https://bugs.launchpad.net/bugs/95162
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
I have ignored your request for dpkg -l .. the problem is the upgrade
scripts. If this is too difficult to script, then it needs to be in the change
list and package readme files/kept in doc.
The problem was that as part of the upgrade from apache2 to apache2.2 the
required modules where
On Mon, Jul 30, 2007 at 01:41:14PM -, Tim Webster wrote:
> The problem still exist. Cannot upgrade apache2 in Edgy to apache2 in
> Feisty or Gutsy.
I need a bit more info about the current state of apache2 on your system
to figure this one out. There is code in place that should handle this.
This is a rather easy fix - I don't know if it could be done as a post-
install script or something? Anyway, I fixed it with the following:
$ cd /etc/apache2/mods-enabled
$ for f in `ls ../mods-available` do
>sudo ln -s ../mods-available/$f $f
>done
$ sudo apache2 -k start
This is because eve
The problem still exist. Cannot upgrade apache2 in Edgy to apache2 in
Feisty or Gutsy.
The hardware this server is running on is due to be upgraded in Sept.
I have decided to run debian on our servers and ubuntu on our
desktops. The apache2 upgrade problem is not to sole reason for this
decision.
hmm, I have apache-common (1.3) installed as well. I should have
removed that a long time ago. dpkg, apt wasn't complaining so I never
though to check. Since apache-common (1.3) contains mod_access,
perhaps that was the problem. I will check when I get back.
On 7/13/07, Soren Hansen <[EMAIL PROTE
I am currently away on a business trip. I will verify this when I
return. And I will also take a look at the package install scripts.
The first apache upgrade from (2.0) to (2.2) failed just like the
rest. Chuckle if the first updated didn't fail I wouldn't have a
problem now, smile. I look into th
The trouble is that the Order directive moved during the Apache 2.2 development
cycle. It used to live in mod_access, but now lives in mod_authz_host. This is
handled in Debian and hence Ubuntu by automatically adding these modules when
doing a fresh install or when upgrading from anything below
I appreciated your help with this. I know I could solve this myself,
but that is not the point. Long term support means moving from release
to release, or continuously upgrading without reinstalling.
On 7/1/07, Caspar Clemens Mierau <[EMAIL PROTECTED]> wrote:
> Thanks for your comment. Can you
Thanks for your comment. Can you please attach your apache2.conf and a
"ls -al" of "mods-enabled" and mods-available? Thank you.
--
Apache2 Fails to install/start
https://bugs.launchpad.net/bugs/95162
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
BUG has NOT been fixed by apache Version: 2.2.3-5
The problem is perhaps the apache upgrade from 2.0 to 2.2
Starting from apache2 2.0.55-4ubuntu4
upgrade apache2, libapache2-svn, libapache2-mod-python to gutsy by
aptitude install apache2 libapache2-mod-python libapache2-svn
There are no install
** Changed in: apache2 (upstream)
Status: Unknown => Fix Released
--
Apache2 Fails to install/start
https://bugs.launchpad.net/bugs/95162
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
If you could test it with the latest version from gutsy (2.2.3-5) from
ubuntu, it would be great. But don't do it on your production server. If
you can test it on a test server, that would help us to check if the
latest version in gutsy fixes your problem.
Tanks for your help.
--
Apache2 Fails t
Thanks for getting back to me.
Currently I am using 2.0.55-4ubuntu4 which is fine. The apache version
that comes with festy 2.2.3-3.2build1 is broken for me. Are you
interested in a bug report for this version.
This is on a production server, so I am reluctant to upgrade this
computer to gutsy at
Thanks for your bug report. I cannot prove this bug report with the same
package. Can you please check if this bug still persists and provide us
with your steps to you your apache installation and the important apache
configuration files like apache2.conf?
Thank you in advance
** Bug watch added:
Bug Fixers,
Still waiting for this fix in feisty!
I am looking the following.
1) An estimate how long it will be until someone has the time to look at this
and move the fix from debian into ubuntu.
If I don't get a response by the end of May, This will be the last time I
install ubuntu on a ser
I have the same problem:
Error:
apache2ctl -t
Syntax error on line 141 of /etc/apache2/apache2.conf:
Invalid command 'Order', perhaps misspelled or defined by a module not
included in the server configuration
from 141 of apach2.conf
Order allow,deny
Deny from all
Bug Reference:
http:/
18 matches
Mail list logo
