[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#491868: marked as done (apache2: upgrade caused virtualhosts to disappear)



Your message dated Tue, 22 Jul 2008 22:37:53 +0200
with message-id <200807222237.53761.sf@debian.org>
and subject line Re: Bug#491868: apache2: upgrade caused virtualhosts to disappear
has caused the Debian Bug report #491868,
regarding apache2: upgrade caused virtualhosts to disappear
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
491868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491868
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.2.9-5
Severity: important

After upgrading Apache2 via aptitude full-upgrade all my virtual hosts
stopped working and pointed to the default site (the "It works!" message).

Restarting the server displayed this warning twice:
[warn] NameVirtualHost *:80 has no VirtualHosts

All my VirtualHost entries had been defined with:
<VirtualHost *>

To fix the problem I added the port to the all the directives:
<VirtualHost *:80>

I don't understand why I had to do this when it was working fine before
the upgrade. The Apache manual is clear that specifying the port is
optional.

Best regards,
Andrew


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
On Tuesday 22 July 2008, Andrew France wrote:
> I don't understand why I had to do this when it was working fine
> before the upgrade. The Apache manual is clear that specifying the
> port is optional.

The change was necessary to allow a reasonable ssl default 
configuration. It was described 
in /usr/share/doc/apache2/NEWS.Debian.gz . You can/should install 
apt-listchanges which can display relevant sections from all 
NEWS.Debian files before upgrades.

Cheers,
Stefan


--- End Message ---

Reply to: