HP3000-L Archives

March 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Tue, 27 Mar 2001 06:29:25 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Claudio Jösch wrote:
>
> Hi all,
>
> has somebody gotten or seen the following error messages in error_log after
> trying to start the Apache webserver after an update from 6.0 to 6.5?
>
> HTTPD.PUB.APACHE: [Thu Mar 22 22:11:36 2001] [error] Failed to resolve
> server na
> me for 192.6.2.1 (check DNS) -- or specify an explicit ServerName
> HTTPD.PUB.APACHE: [Thu Mar 22 22:11:36 2001] [error] Failed to resolve
> server na
> me for 195.53.4.4 (check DNS) -- or specify an explicit ServerName
> HTTPD.PUB.APACHE: [Thu Mar 22 22:11:36 2001] [crit] You cannot use multiple
> List
> ens safely on your system, proceeding anyway.  See src/PORTING, search for
> SERIA
> LIZED_ACCEPT.

It would be helpful to see your httpd.conf to understand what you're trying to
do here.

The SERIALIZED_ACCEPT issue should be fixed in Apache 1.3.9 which is now
available as a GR patch for 6.5.

...snip...

> In RESLVCNF.NET.SYS the domain is specified but no nameserver?!

That's probably the problem.  Apache is unable to do inverse lookups on the IP
addresses 192.6.2.1 and 195.53.4.4.  Specify one or more nameserver lines in
RESLVCNF.NET.SYS that point to DNS servers that can look up those addresses.
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...

ATOM RSS1 RSS2