[EMAIL PROTECTED] wrote:

> On 17-Dec-98, Peter \(Troff\) Petroff took time to write :
> > to check error logs and suprise, it said that ServerName wasn't set. But the
> > thing was, Apache WORKED for a few days before it failed to start up and I
> > made NO repeat NO changes to ANY Apache configs. When I set ServerName, it
> > DID start working again. But what the heck caused it to fail in the first
> > place?
> do you mean for example it works, you reboot your computer, and then it
> doesn't work anymore ?
I mean:
* Installed Linux, installed Apache as a package and let dselect do the
automatic configuration for me (oh okay, instead of selecting /var/www as
DocumentRoot, I changed it to /home/www).
* On login, I browsed to my own Apache and it worked fine.
* Shutdown, restart, worked fine. Repeat shutdown, restart, worked fine for
days. (I don't keep my Linux up long term yet, I'm still learning and trying to
configure it as a Winborg replacement one-person machine.
* No repeat no config changes WHATSOEVER.
* One day I wake up, boot Linux. As I'm watching the boot messages, I see the
message:
        'Starting Apache... failed.'
* This repeats for many shutdown/restarts.
* Checked the error log as suggested, found the message re: ServerName. Fixed it
by giving the machine name ('superego').
* Apache starts working again with no problems.

But the problem should never have occurred in the first place 'cause I
definitely didn't screw with it!


> it can be a problem with your dns settings.
> are you using a dns on your network (btw are you on a network, or only
> occasionnaly with ppp, or ...), or do you have a dns on the same box than
> Apache ?
A local eth0 network consisting of:
        'superego', the dualboot Winborg98/Linux AMD K6-233
        'id', a PentiumII Winborg98.
A part-time ppp.
No DNS on the superego/id network (selected during initial Linux installation),
just a substantial /etc/hosts.
PPP is configured to use my ISP's DNS. As far as global browsing goes, it works
fine; I can ping global sites, as well as id.


> If Apache upon booting doesn't find the information in the DNS it needs, then
> it will dye.
> But if you relaunch it after that, it may work.
Never complained about DNS, just about its own local name. And repeated
restart/launches made no difference.


> what does apache -S tell ? is it like :
> vagabond:~# apache -S
> httpd: cannot determine local host name.
> Use ServerName to set it manually.
I'll have to get back to you on that.

But since I put 'ServerName: superego' into apache.conf, it's been working just
fine. Except I don't understand how it could have failed in the first place
after a successful installation followed by days of proper operation and NO
changes.

[shrug]

-- 
Peter Petroff, IT Support
Lifestyle Support Services (LSS), Uniting Church of Australia in Queensland
Note: Opinions expressed are the author's and not those of the LSS.
-------------------------------------------------------------------------------
"I told her... DON'T - F*** - WITH - WENDY - TESTEBURGER!"
        - Wendy Testeburger, "South Park".
<----------- Your mail window may want to consider being this wide ----------->

Reply via email to