On 08/05/07, Brett Parker iDunno@sommitrealweird.co.uk wrote:
The only Listen 80 is in the mod_ssl section, after Listen 443. No changes have been made to the hosts file since the upgrade, though, and it worked before, so it's probably not a config error.
Errrrrr, what's it doing in the mod_ssl section?! That seems a little odd... but, anyways...
I'm sure there'll be a good reason as my predecessor knows much about most of debian. Not so good at leaving documentation though.
What does it show if xinetd is stopped and apache is restarted?
apache still won't start when xinetd is stopped. Same error [crit] (98)Address already in use: make_sock: could not bind to port 80 but now sudo netstat -t -l -n -p | grep 80 has no resulting output.
That seems rather strange. Does xinetd listen on 0.0.0.0:80 or a particular IP address? If they both want 0.0.0.0:80, it won't work.
No, xinetd is on a different address. I'll ask the previous administrator about it when I next manage to catch up with him (he's very elusive).
I'm still thinking (as I said on IRC), drop the 2 entries for xinetd (you'll probably find that in both cases apache is configured to handle them), then restart xinetd, then restart apache. Then wait for someone to yell something is broken (if you don't know why it's there, then it probably shouldn't be there ;).
Slightly worried that your svn server and your main webserver are one and the same box, but hey :)
Sorry - I'm not ignoring your suggestion,it's just that I'm very reluctant to start removing stuff that used to work fine, when I haven't sussed out what it all does and is for yet. The svn entry will be for balloonboard.org so I really don't want to stop that working.
Thanks,
Jenny