Re: Problems with latest Apache2 update

[John Foster <jfoster@augustmail.com>]

On Monday 29 March 2004 04:17 am, Antonio Rodriguez wrote:
> On Sun, Mar 28, 2004 at 11:11:41PM -0600, John Foster wrote:
> > I recently updated my apache2 from SID. Now when it tries to start I get
> > a message that it can not find the fully qualified domain name of my
> > network server. I have recently used the newest Debian network installer
> > from SID to
>
> To change the hostname you probably would need to do as follows:
> 1. hostname new_name
file /etc/hostname  shows the correct name  brutus which is the name of my 
network server on my home network
> 2. Edit files /etc/hostname and /etc/hosts
file /etc/hosts  lists as follows:

127.0.0.1	localhost
216.87.145.170	brutus.advance-computing.com

# The following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

I don't see any problems here & it exactly matches my other server setups on 
other systems.

> 3. Edit /etc/apache/httpd.conf
In apache2 that is an empty file and all of the configs are in apache.conf 
along with a couple of other files. Also nowhere does it have the ip address 
of the host server that I can locate anywhere in /etc/apache2/

Now the real interesting thing is that when you issue the command 'hostname' 
brutus is delivered
If you issue the command 'dnsdomainname  --fqdn'  then unknown host is 
delevered.

So I currently am exonorating apache2 and figure something is slightly buggy 
with the new network install iso image that I used..& this is the one 
curently touted for sarge.
At any rate thanks Antonio and Simmel  for taking a shot at this as they did 
prompt me to look deeper than previous.

-- 
John Foster