Apache on red Hat

Discussion in 'Apache' started by tanweernoor, Dec 1, 2008.

  1. #1
    out of curiosity, just wanted to know as a user ( I am accessing the URL on different machine) how can I troubleshoot errors shown by apache web server,
    let me put 1 scenario...
    I am running an Apache web server and server is up from server's browser and few other machines its showing the index page.
    but one of the user complains that he is getting some error after pointing his/her browser say 404 or something.

    now my question is how the user can troubleshoot what could be the problem as server is up and accessible from other machine.

    thanks
    Tanweer
     
    tanweernoor, Dec 1, 2008 IP
  2. tanweernoor

    tanweernoor Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    any update on this??
     
    tanweernoor, Dec 2, 2008 IP
  3. kailash

    kailash Well-Known Member

    Messages:
    1,248
    Likes Received:
    42
    Best Answers:
    0
    Trophy Points:
    190
    #3
    There are many reasons for that DNS propagation, domain is not pointing correctly, multiple DNS or A records etc.
     
    kailash, Dec 5, 2008 IP
  4. tanweernoor

    tanweernoor Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    well, thanks for your reply, do you mean in that case i should try to ping my DNS??
     
    tanweernoor, Dec 10, 2008 IP
  5. kailash

    kailash Well-Known Member

    Messages:
    1,248
    Likes Received:
    42
    Best Answers:
    0
    Trophy Points:
    190
    #5
    You can tell your user to ping to your site as well as you can tell to do a tracert from his/her end.

    Kailash
     
    kailash, Dec 10, 2008 IP
  6. tanweernoor

    tanweernoor Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #6
    Hey Kailash
    what is tracert and how a user can do from his/her side, thanks for your quick reply buddy!!!


    ~Tanweer
     
    tanweernoor, Dec 10, 2008 IP
  7. Lexiseek

    Lexiseek Banned

    Messages:
    2,499
    Likes Received:
    115
    Best Answers:
    0
    Trophy Points:
    0
    #7
    I would look through /site/error_log and /site/access_log

    That will contain the details of what the user attempted to do. These logs serve as your main debugging tools.
     
    Lexiseek, Dec 11, 2008 IP
  8. tanweernoor

    tanweernoor Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #8
    Lexiseek... you are absolutely correct but thing is you can check this on server..... I want to troubleshoot as a user.
     
    tanweernoor, Dec 11, 2008 IP
  9. Lexiseek

    Lexiseek Banned

    Messages:
    2,499
    Likes Received:
    115
    Best Answers:
    0
    Trophy Points:
    0
    #9
    On a brand new server, the first thing I would check is firewall rules.

    If you did have access to the server logs, you could use grep to look for his IP and see what error is being generated.
     
    Lexiseek, Dec 11, 2008 IP
  10. kailash

    kailash Well-Known Member

    Messages:
    1,248
    Likes Received:
    42
    Best Answers:
    0
    Trophy Points:
    190
    #10
    You can follow this link for ping and tracert reports. The steps provided in the link is for Windows Operating system except Vista.

    Kailash
     
    kailash, Dec 11, 2008 IP
  11. tanweernoor

    tanweernoor Peon

    Messages:
    9
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #11
    Great!!! thanks Kailash..... is there something for Linux also..
     
    tanweernoor, Dec 12, 2008 IP
  12. kailash

    kailash Well-Known Member

    Messages:
    1,248
    Likes Received:
    42
    Best Answers:
    0
    Trophy Points:
    190
    #12
    for Linux the command is traceroute.

    traceroute domain.com

    Kailash
     
    kailash, Dec 12, 2008 IP