1 |
Mystery solved. As expected: my bad. Details at the bottom |
2 |
|
3 |
On 9/7/07, Kevin O'Gorman <kogorman@×××××.com> wrote: |
4 |
> |
5 |
> On 9/7/07, Steen Eugen Poulsen <sep@×××××××××.net> wrote: |
6 |
> |
7 |
> > Kevin O'Gorman skrev: |
8 |
> > > My 00_default_vhost.conf: |
9 |
> > > =============== start 00_default_vhost.conf ========================== |
10 |
> > > # If your host doesn't have a registered DNS name, enter its IP |
11 |
> > address |
12 |
> > > here. |
13 |
> > > # |
14 |
> > > #ServerName www.example.com:80 <http://www.example.com:80> |
15 |
> > > ServerName www.kosmanor.com:80 <http://www.kosmanor.com:80> |
16 |
> > > |
17 |
> > > #KOSMANOR changes |
18 |
> > > #Listen 80 |
19 |
> > > Listen 64.166.164.49:80 <http://64.166.164.49:80> |
20 |
> > > Listen localhost:80 |
21 |
> > |
22 |
> > Thats not a vhost configuration, so it's a bit confusing why your trying |
23 |
> > to use Gentoo's default vhost config file and making non vhost configs |
24 |
> > and I bet it isn't liking the missing: |
25 |
> > |
26 |
> > NameVirtualHost *:80 (You will have to check the apache2 doc for the |
27 |
> > VirtualIP version of NameVirtualHost) |
28 |
> > |
29 |
> > <VirtualHost *:80> |
30 |
> > |
31 |
> > If you want to make a non vhost configuration, then do so from the |
32 |
> > ground up, don't mix vhost and non vhost unless you want a mess. |
33 |
> > |
34 |
> > The reason you get :80 already bound, is because your configuration bind |
35 |
> > twice to the same IP. It's Apache itself that bind twice and bails on |
36 |
> > the second attempt. |
37 |
> > |
38 |
> > Not having used this configuration layout in years, I would guess |
39 |
> > ServerName is the one creating the listening socket, maybe because it's |
40 |
> > placed before Listen. |
41 |
> |
42 |
> |
43 |
> A workaround has been found (see below). |
44 |
> |
45 |
> As may be obvious by now, I don't understand much about configuring |
46 |
> apache. I just used what dropped in when I installed Gentoo around 2003, and |
47 |
> tried to adapt as time and updates came along. My needs are fairly simple: |
48 |
> a basic server on a single IP plus localhost, using the default port 80. |
49 |
> Static and CGI pages only, no secure applications. Users (only me, |
50 |
> actually) have a page in public_html. I intend to use mod_python |
51 |
> eventually, or write my own module, but that's for later. |
52 |
> |
53 |
> I have not a clue how to build a configuration "from the ground up", and |
54 |
> I'm hoping to not have to learn. Since it would be a singleton excercise, I |
55 |
> would just forget it anyway in the midst of many other things that claim my |
56 |
> attention. |
57 |
> |
58 |
> Workaround: |
59 |
> In any event, making ServerName come after Listen, or commenting it out |
60 |
> completely, do not change the symptoms at all. However, commenting out all |
61 |
> Listen lines does allow apache to start. It seems you're right and apache |
62 |
> is colliding with itself, but I don't know why, as I don't see any other |
63 |
> Listen directives. This is at best a stopgap because apache's now listening |
64 |
> promiscuously, which I do not like at all. |
65 |
> |
66 |
> I'm hoping for more help, but my fallback is to save my config files, |
67 |
> unmerge apache completely, re-emerge it and see if the default configuration |
68 |
> can be made to work right. That might turn out to be a lot of work, for |
69 |
> which read a lot of time. |
70 |
> |
71 |
|
72 |
I was sure I checked for duplicate Listen directives, but I missed one. |
73 |
Fixing that allowed apache to start. |
74 |
As pennance, I hunted down all my tailorings and put them in a single |
75 |
include file. In the process I wound |
76 |
up eliminating a bunch of other duplications. Hopefully things will be more |
77 |
sane soon. |
78 |
|
79 |
But not right away -- but I'll start another thread for that. |
80 |
|
81 |
++ kevin |
82 |
|
83 |
|
84 |
|
85 |
-- |
86 |
Kevin O'Gorman, PhD |