Apache Troubleshooting


Results 1 to 9 of 9

Thread: Apache Troubleshooting

  1. #1
    Join Date
    Aug 2003
    Posts
    35

    Question Apache Troubleshooting

    How to I troubleshoot my apache setup?

    I started httpd from my linux box and tried to access it from my windows box via http://192.168.1.101 and I don't get anything. It just times out. My windows can ping the linux box.

    I don't have a working mouse port on my linux box so I can't use any gui tool. All configuration must be done at the prompt.

    Thanks,

    -Rex

  2. #2
    Join Date
    Mar 2003
    Location
    Florida, USA
    Posts
    221
    Ok, just a few questions to be going on with...

    Is there a firewall on the Linux box?
    If you do ps aux | grep httpd is the task listed?
    Are you starting Apache with httpd -k start? Do you get any error messages?
    Does the error_log show any details?
    Which version of httpd are you using? (httpd -v will tell you)
    Just for the hell of it, which distro / kernel is it?

    Answer as many of these as possible and it will help us to help you.

    Phil.
    Get yer trousers on. You're nicked.

  3. #3
    Join Date
    Aug 2003
    Posts
    35
    Is there a firewall on the Linux box?

    There is no firewall on the linux box but I'm using a dsl router a a hub (is this ok??). I've used this router before to connect 2 computers with no problem. I'm still waiting for my DSL setup in a few weeks.

    If you do ps aux | grep httpd is the task listed?

    yes the task is listed. There are about 8 task for httpd

    Are you starting Apache with httpd -k start? Do you get any error messages?

    Yes i start apache using httpd -k start and no error messages.

    Which version of httpd are you using?

    Version :Apache 2.0.40

    How would I know what distro or kernel I'm using?

    Thanks for the reply,

    -Rex

  4. #4
    Join Date
    Mar 2003
    Location
    Florida, USA
    Posts
    221
    You should know your distro - Red Hat, Suse, Mandrake etc?
    You can find the kernel by typing uname -a at a prompt.

    If you've got multiple httpd tasks listed then it's running. If you're in Windows, in IE you should be able to type http://<linux ip address> and see a web page... you say you can ping it so it doesn't sound like a routing issue... the only thing I can think of right now is that Apache isn't set to point to any default page.

    I would suggest tracking down httpd.conf - sometimes in /var/www/conf or /etc/http.d - location varies, do a "find / -name httpd.conf" if you don't know where it is... open that up and in there (somwhere!) will be a DocumentRoot parameter, which should be pointing to a directory. Check that directory exists and there's an index.html of some description in there.

    Anyone else any other ideas?

    Phil.
    Get yer trousers on. You're nicked.

  5. #5
    Join Date
    Aug 2003
    Posts
    35
    My distribution is RedHat 9 and the kernel is 2.4.20-8.

    I checked the directory where DocumentRoot points to in httpd.conf file and it does exist. I created an index.html file there but still no luck.

    How else can I troubleshoot my Apache setup?

    Thanks for the reply.

    -Rex

  6. #6
    Join Date
    Aug 2002
    Location
    FDR India
    Posts
    340
    Hi

    ping 192.168.1.101:80. Whats the response to that?

    Apache by default listens to port 80. You could also check Listen directive in httpd.conf.

    regards
    theN
    O Nobly Born, be thou grave and courteous in thy speech; quick to succour and slow to flame.
    --- Registered Linux User #293167 ---

  7. #7
    Join Date
    Aug 2003
    Posts
    35
    Hi,

    I pinged http://192.168.1.101:80 and I get a timeout. I tried it on a website that I can ping successfully and I also get a timeout when I include port 80.

    I'm using DHCP on my router and when I view the DHCP IP Table my linux box IP address shows up but with a blank Hostname. Could that be related to my Apache woes? Where do I set the hostname in linux?

    I will open a new thread regarding that.

    Thanks for the reply.

    -Rex

  8. #8
    Join Date
    Mar 2003
    Location
    Florida, USA
    Posts
    221
    Fixing the hostname shouldn't affect whether or not http://<ip address> works.

    However, put the name in /etc/hosts :-

    a.b.c.d myaddress.mydomain.com myaddress



    That should fix that problem.
    Get yer trousers on. You're nicked.

  9. #9
    Join Date
    Aug 2003
    Posts
    35
    Hi,

    I ran 'service iptables stop' and it worked. I got the idea from a post by cowanrl on another thread.

    Thanks for all the replies,

    -Rex

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •