Redhat secure server - Jan 2000 - Re: Virtual Host Problem

Hello,
Dennis Edmonds.

Have you created  log files for every virtual host?
If you do not create a file for log file which you
spell in httpd.conf, apache cannot startup.
crete a text file before you start up Apache.
http -t can not check this error.
but it can be loged in the server''s log file.


Sincerely yours,
David Ge
2000-01-05

You 2000-01-04 10:53:00 you wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>Hello,
>
>I hate to address a list with a problem like this without browsing the
>archives, but that''s not very easy to do right now (even listserv
>archives are not letting me retrieve more that 12 files at a time.)
>
>Anyway, I have just finished setting up a RedHat secureweb-3.1 server
>(brand new machine...fresh install) at work and migrated our Virtual
>Hosts over from the old installation of Apache 1.3.x (can''t
remember
>the exact version.)  The problem is that the Virtual Hosts are not
>working on the new server.  I have verified that the httpsd.conf file
>is correct and that the nameservers are still working properly (the
>main nameserver didn''t even change.)  The output from httpsd -S
looks
>similar enough to another Apache 1.3.9 system that I believe apache is
>reading the config file correctly and understanding the vhost config.
>
>Has anyone experienced similar problems, or have any other suggestions
>on potential problem areas I could take a closer look at?
>
>Thanks in advance,
>
>Dennis Edmonds
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP Personal Privacy 6.0.2
>
>iQA/AwUBOHIXgtNaXrbtbShkEQKaSwCg0o/vk2xufUCyEiNboTmgDl2iB7gAnjMk
>WbRyVT2tPNblgd6nZ+tJOqlI
>=Hv0E
>-----END PGP SIGNATURE-----
>
>
>
>--
>  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
>		http://www.redhat.com http://archive.redhat.com
>         To unsubscribe: mail redhat-secure-server-request@redhat.com with
>                       "unsubscribe" as the Subject.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Thanks to everyone for the suggestions.  After much stress and hair
pulling yesterday, I finally stumbled onto the problem.  I was using
the public IP address of the machine in the NameVirtualHost directive,
instead of the machines actual IP address (this machine is being NATed
to/from a private IP address.)  I had misunderstood exactly what kind
of information the server would receive from the client.  I had
thought that it would be looking at www.notareal.name and the real IP
address...not just the name.

Lessons learned: NAT can be a real headache ;)

Thanks again,

Dennis Edmonds

-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.0.2

iQA/AwUBOHNaDNNaXrbtbShkEQJuZwCgqM0OSoHgbGTzM25vGfGUMlRgym8AoKoI
qvdH1NIQfA0oRGgmAVhbugnu
=2rks
-----END PGP SIGNATURE-----