Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-06 Thread Thomas Goirand
On 01/06/2011 08:17 AM, christ...@hilbert.alphasky.net wrote:
 Thomas Goirand z...@debian.org wrote:
 
 Hi Ian,

 I think that if nobody found the issue, it's because nowadays, almost
 everyone is using IP based virtualhosts, because starting apache with
 named virtualhost makes apache resolve as many hostname as you have
 vhosts, and in many situations, this can take a long long time.

 Anyway, did you try to add a:

 Sound-Start: bind9

 in the init script dependencies of Apache? Does it fixes the issue?

 Thomas



 
 Hi Thomas,
 most people who have a restricted number of ip addresses use name based 
 virtualhosts though.

This has absolutely nothing to do with the number of IP address you may
have. You can for example do:

VirtualHost 1.2.3.4:80
ServerName www.example.com
DocumentRoot [...]
[...]
/VirtualHost
VirtualHost 1.2.3.5:80
ServerName www.example.org
DocumentRoot [...]
[...]
/VirtualHost

This way, you'd have both www.example.com and www.example.org sharing
the same IP.

 I rather think that not everyone is running bind in order to ensure name 
 resolving. External
 nameservers are another option and I don't know wheter it can be considered 
 as a default to
 have an own one.

Whether you use external or embedded name server has nothing to do with
it: resolving is slow, and you should avoid it.

Anyway, that's just my 2 cents of advice, and it has nothing to do with
this bug entry anymore... :)

Thomas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-05 Thread christoph
Thomas Goirand z...@debian.org wrote:

 Hi Ian,

 I think that if nobody found the issue, it's because nowadays, almost
 everyone is using IP based virtualhosts, because starting apache with
 named virtualhost makes apache resolve as many hostname as you have
 vhosts, and in many situations, this can take a long long time.

 Anyway, did you try to add a:

 Sound-Start: bind9

 in the init script dependencies of Apache? Does it fixes the issue?

 Thomas




Hi Thomas,
most people who have a restricted number of ip addresses use name based 
virtualhosts though. I rather think that not everyone is running bind in order 
to ensure name resolving. External nameservers are another option and I don't 
know wheter it can be considered as a default to have an own one.

Regards,
Christoph



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-02 Thread Thomas Goirand
Hi Ian,

I think that if nobody found the issue, it's because nowadays, almost
everyone is using IP based virtualhosts, because starting apache with
named virtualhost makes apache resolve as many hostname as you have
vhosts, and in many situations, this can take a long long time.

Anyway, did you try to add a:

Sound-Start: bind9

in the init script dependencies of Apache? Does it fixes the issue?

Thomas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2010-12-08 Thread Ian Jeffray
Package: apache2.2-common
Version: 2.2.16-4
Severity: normal


Can't believe nobody else has hit this before, but can't see it in the bug 
tracker.
The new dependency-based init scheme added in debian testing has caused apache2 
to be started
before bind9.  This means that it can't resolve hostnames and just fails with
errors like: No address associated with hostname: Could not resolve host name 
www -- ignoring!

This apache configuration has been perfectly fine until the upgrade to 
dependency based
initialisation.

-- Package-specific info:
List of enabled modules from 'apache2 -M':
  alias auth_basic authn_file authz_default authz_groupfile
  authz_host authz_user autoindex cache cgi dir env mem_cache mime
  negotiation php5 proxy_connect proxy_ftp proxy_http proxy python
  reqtimeout rewrite setenvif status userdir
List of enabled php5 extensions:
  curl idn mysql mysqli pdo pdo_mysql suhosin

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.36 (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/dash

Versions of packages apache2 depends on:
ii  apache2-mpm-prefork   2.2.16-4   Apache HTTP Server - traditional n
ii  apache2.2-common  2.2.16-4   Apache HTTP Server common files

apache2 recommends no packages.

apache2 suggests no packages.

Versions of packages apache2.2-common depends on:
ii  apache2-utils 2.2.16-4   utility programs for webservers
ii  apache2.2-bin 2.2.16-4   Apache HTTP Server common binary f
ii  libmagic1 5.04-5 File type determination library us
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  mime-support  3.48-1 MIME files 'mime.types'  'mailcap
ii  perl  5.10.1-16  Larry Wall's Practical Extraction 
ii  procps1:3.2.8-9  /proc file system utilities

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org