>
> Synopsis: Logs in 2 places, weird cgi responses
>
> State-Changed-From-To: open-analyzed
> State-Changed-By: marc
> State-Changed-When: Mon Nov 24 16:35:46 PST 1997
> State-Changed-Why:
> I'm afraid you aren't very clear in exactly what you are
> doing, and what you think is wrong and what you do and what
> you expect vs. what you get.
>
Sorry. We've solved the problem, but for the sake of making
sure no one else runs into it I'll go through the questions and
answer them. The person setting the server up :
1) Named the base machine www.XXX.com and gave it an IP
2) Configured Apache 1.2.4 for the base
3) Configured a few virtual hosts, one of which was www.XXX.com
but with different information except the same IP.
to fix
1) Rename machine to YYY.XXX.com and gave new IP
2) Reboot.
>
> I would guess that your virtualhosts are configured
> incorrectly.
>
I had created fresh copies of all the .conf files from
a "form" I've used for dozens of other servers. The virtual host was
correct, but the fact that it was also the BASE systems IP/hostname was
probably very wrong.
>
> Are you trying to use non-IP based vhosts?
>
Tried it both ways, still gave problems.
>
> Do you have an IP address for each virtualhost?
>
Yes, but the 1 virtual host was the same as the BASE
>
> Exactly
> what problems are you having?
>
If you requested a cgi , it appeared to run ok. If you telnetted to the
port (We have monitoring software that does that) and said "GET
/cgi-bin/monitor.pl"
it would tell you it didn't exist, or run it from the BASEs directory.
>
> If you don't have an IP address for each vhost, then it
> is expected that you get the main server if you don't
> send a Host: header.
>
Not doing port based, IP based.
>
> Please state what the main IP is, what each of the virtual
> hosts should be, and include the relevant vhost sections
> from your config.
>
This is where you would have caught it.
Sorry to trouble you.
Tuc/TTSG
