localhost => FQDN - Apache dies?

Help
2011-12-08
2013-05-30
  • philip_rhoades

    philip_rhoades - 2011-12-08

    People,

    Using:

    - Fedora 14 x86_64
    - PostgreSQL
    - PGV (latest SVN)
    - http://localhost/phpgedview

    I am happily entering data now but when I try to use:

    - http://FQDN/phpgedview

    (without changing anything in config.php)

    it takes ages to display stuff - mostly the hourglass stuff:

    - On This Day …
    - Users Logged In
    etc

    but the main problem is that while this is happening, whatever is going on kills all other web sites that my server is providing - they all sit forever with their hourglasses churning . . but I can't see where the problem is - I have to exit out of the browser trying FQDN/phpgedview and wait for a little while for the other sites to recover. Checking with "top" and looking at httpd logs doesn't indicate any issues. I have never had this sort of problem before - has anyone got suggestions about what is wrong?

    Thanks,

    Phil.

     
  • Gerry Kroll

    Gerry Kroll - 2011-12-08

    Check the contents of the text file "config.php" in your PhpGedView install directory.

    The $SERVER_URL definition should be empty.

     
  • philip_rhoades

    philip_rhoades - 2011-12-08

    canajun2eh,

    Yes, it is empty.  After more experimentation I find that if I wait for about 10 minutes for the remote connection to finish downloading all the icons and info, then everything starts working again for all the other web sites as well as the local and remote PGV browsers. It is still a mystery what is going on - it couldn't possibly take so long to download the little icons and there is virtually no data so I am at a loss to know what else to check. It is not a big issue at the moment but if I get lots of family members logging in I don't want each of their first logins killing my other sites for ten minutes each . .

    Thanks,

    Phil.

     
  • Gerry Kroll

    Gerry Kroll - 2011-12-09

    It sounds as if your "FQDN" server is not properly configured. 

    Perhaps there's a very low limit to the number of concurrent sessions, or PHP scripts aren't allowed enough memory, resulting in hard drive thrashing.

    I can't really advise you here - I know nothing about server configurations.

     
  • philip_rhoades

    philip_rhoades - 2011-12-09

    canajun2eh,

    I think you might be right - all the other web sites are static pages or Rails based - so I don't know much about PHP debugging or tuning . .

    Thanks,

    Phil.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks