Results 1 to 2 of 2

Thread: Apache files inaccessible on net, all of a sudden

  1. #1

    Question Apache files inaccessible on net, all of a sudden

    Any ideas what could be causing this?
    Apache was working just fine, and then I got a couple file permission weirdnesses, and a login error messages (since fixed). Whether as a result or part of the initial problem, YaST froze up and had to be closed in mid-save.
    Since then, Apache starts, stops, and gives a local host default page of "It works" but all pages in browsers come up "Access forbidden."
    Further, YaST seems to be unble to keep virtual hosts properly configured, as the "determine by HTTP Headers" keeps getting replaced by "determine by Server IP"... I have deleted the entire host tab and re-entered the info, but it still messes up.

    What can be done?

  2. #2
    Join Date
    Jun 2008
    Location
    Oklahoma, US
    Posts
    822

    Default Re: Apache files inaccessible on net, all of a sudden

    oldog wrote:

    >
    > Any ideas what could be causing this?
    > Apache was working just fine, and then I got a couple file permission
    > weirdnesses, and a login error messages (since fixed). Whether as a
    > result or part of the initial problem, YaST froze up and had to be
    > closed in mid-save.
    > Since then, Apache starts, stops, and gives a local host default page
    > of "It works" but all pages in browsers come up "Access forbidden."
    > Further, YaST seems to be unble to keep virtual hosts properly
    > configured, as the "determine by HTTP Headers" keeps getting replaced
    > by "determine by Server IP"... I have deleted the entire host tab and
    > re-entered the info, but it still messes up.
    >
    > What can be done?
    >
    >


    Having just realized I didn't install Apache on my 11.0 server, I can't
    verify this, but were there any updates to Apache recently?

    It's entirely possible that an update bumped your config files to a
    httpd.conf.rpmsave and replaced them with stock config files.

    Can't think of any other method in which Apache config files change
    unexpectly.

    Especially curious is the bit where you said it gives the default "it works"
    page... if that reappeared, then it's very likely that an update has
    overwritten or moved your config files. If that has happened, you should
    find one or more files named "xxx.rpmsave" or "xxx.YaSTsave" (or something
    close at least)

    copy those files back to their respective proper names, and restart apache
    to see if that helps.


    --
    L R Nix
    lornix@lornix.com

Tags for this Thread

Posting Permissions

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