Announcement

Collapse
No announcement yet.

Apache2 not working

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Apache2 not working

    So after installing apache2 from Adept, I tried firing it up, and get the message "apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName" ... and apache doesn't start.

    I've looked through the apache2.conf file, all looks fine. I've checked with guarddog that I have http set as an allowed protocol too. Everything checks out. I've never had any trouble getting apache working on ANY distro before, even with a lot of customization. But all I can get whether I try accessing through http://127.0.1.1, http://127.0.0.0 (the old standard), http://localhost, or my dyndns domain, all I get from Firefox is "Problem loading page." Unable to establish a connection. Checked my system services, see that apache isn't running, and it simply won't start. Just keeps giving me the qualified domain message and does nothing. Tried reinstalling too ... same deal. Any ideas?? I've never had trouble getting apache to run before.

    #2
    Re: Apache2 not working

    Hi,

    It should prevent apache2 to start... It's just a warning, I remember I had this error in the past, you should modify the name of your server or domain in config files...

    To see what would block you, you should check in log file :
    /var/log/apache2/error.log

    Cheers

    Comment


      #3
      Re: Apache2 not working

      Well, it took a while, but it turned out to be a bad install of clamav that was screwing up apache!! Thanks for directing me to the error log ... it put me on the path to getting it working. Now to configure apache. w00t!!

      Comment


        #4
        Re: Apache2 not working

        Okay, I'm having a similar problem, I think.

        I've only been using Linux for about a week now, so...be gentle! As far as I can tell, Apache is working fine. When I browse to http://localhost, I get a directory list w/ an apache folder & a test.php file that i created. Clicking on either of these works as expected (the apache folder links to the Apache2-default page, & my test page says "hello world", as all good test pages should.)

        However, when I start/restart apache from the command line, I'm getting the same error as you: Could not determine the server's fully-qualified domain name, using 127.0.1.1 for ServerName. What does this mean?

        I want to make sure everything is as it should be, before I start setting up my website & throw a whole bunch of other possible problems into the mix! Would anybody mind helping shed some light on this for a noobie in need??!

        The following are the most recent entries from my /var/log/apache2/error.log file:

        [Sat Aug 05 21:05:40 2006] [notice] Apache/2.0.55 (Ubuntu) PHP/5.1.2 configured -- resuming normal operations
        [Sat Aug 05 22:42:32 2006] [error] [client 127.0.0.1] File does not exist: /var/www/favicon.ico
        [Sat Aug 05 22:43:12 2006] [error] [client 127.0.0.1] File does not exist: /var/www/favicon.ico
        [Sat Aug 05 23:31:28 2006] [notice] SIGHUP received. Attempting to restart
        apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
        [Sat Aug 05 23:31:28 2006] [notice] Apache/2.0.55 (Ubuntu) PHP/5.1.2 configured -- resuming normal operations
        [Sat Aug 05 23:31:41 2006] [notice] SIGHUP received. Attempting to restart
        apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
        [Sat Aug 05 23:31:41 2006] [notice] Apache/2.0.55 (Ubuntu) PHP/5.1.2 configured -- resuming normal operations
        Much Thanks!

        Shane

        **Possibly relevant addition: I'm trying to set up a development server -- no access from the outside world; just from my laptop.

        Comment


          #5
          Re: Apache2 not working

          Hi,

          In fact, it's not really bad if you're only trying to make it for developement... It's just a warning message which tells you that you didn't set the servername like kubuntu.org for example... So if you're using it to develop, you don't need this, it's only useful if you're using a hostname and domain name

          BTW, it's an option in config files, but I don't remember which one, you're just putting : ServerName "yourhost"

          Cheers

          Comment

          Working...
          X