Mike,

It looks like you need to remove the NameVirtualHost line unless you're wanting 
to do virtual hosting. If that's the case, you need to put lines 33-40 inside 
of a VirtualHost container.

Also, if you post your config again, can you copy it from the "edit" page 
instead of the "display" page? The way you copied it made it very hard to read.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]On
Behalf Of Mike Cunningham
Sent: Tuesday, March 29, 2005 10:53 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] HTP8406 error


Digging inside an HTTP job I found this in the joblog. The server starts
and runs applications OK. Is this anything to worry about ? We created
this web server to support a Webfacing app and followed IBM
documentation on creating the Apache config
 
Message ID . . . . . . :   HTP8406       Severity . . . . . . . :   20 
     
Message type . . . . . :   Diagnostic                                  
     
Date sent  . . . . . . :   03/29/05      Time sent  . . . . . . :  
09:44:53 
                                                                       
     
Message . . . . :   NameVirtualHost as400adm.pct.edu:1414 has no
VirtualHost.
Cause . . . . . :   NameVirtualHost as400adm.pct.edu:1414 has no
VirtualHost 
  container.                                                           
     
Recovery  . . . :   Correct the problem and try the request again.     
     
Technical description . . . . . . . . :   A NameVirtualHost directive  
     
  as400adm.pct.edu:1414 has been specified but there is no VirtualHost 
     
  container that corresponds to it.                    
 
Apache config
 <snip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.