| Author | Post |
|---|
Martin
Member
| Joined: | Tue Jun 14th, 2005 |
| Location: | |
| Posts: | 66 |
|
Posted: Wed May 30th, 2007 04:53 pm |
|
A few days ago all was fine and all my Child installation worked excellent. Now I find when I go to the log in page of these installations I get a page which states the following:
Your server does not have a usable environment variable for determining your site's root path
What does that mean? Especially seeing as a few days ago everything worked fine.
Regards,
Martin
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Wed May 30th, 2007 05:06 pm |
|
| Check the permissions on the directory opening into your parent installation. It sounds like the server may have reset that permission on a reboot or something. That permission must allow users from outside that domain to read the contents of the domain. It's permission must be 0755.
|
Martin
Member
| Joined: | Tue Jun 14th, 2005 |
| Location: | |
| Posts: | 66 |
|
Posted: Wed May 30th, 2007 08:10 pm |
|
Thanks Keith that was exactly what was going on.
Rather annoying that this happened but it is solved now.
Martin
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Wed May 30th, 2007 10:45 pm |
|
| Solved for now. But your server probably did that on a reboot and will probably do it on subsequent reboots. Rather annoying when the server admin messes with a setting that is none of his business. If it does it again, contact your server admin to see if he can comment out that parent domain for permission setting on bootup, or write a bash script to reset it to 0755 after a bootup.
|
Martin
Member
| Joined: | Tue Jun 14th, 2005 |
| Location: | |
| Posts: | 66 |
|
Posted: Thu May 31st, 2007 02:54 pm |
|
I will keep an eye on it Keith and if it happens again will contact them.
Thanks mate!
|
lcanter
Member
| Joined: | Sat Mar 25th, 2006 |
| Location: | |
| Posts: | 20 |
|
Posted: Mon Sep 10th, 2007 02:50 am |
|
| I'm having the same problem, but permissions ARE set to 0755 so it must be something else. Any suggestions?
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Mon Sep 10th, 2007 12:10 pm |
|
lcanter
On the parent domain access wrx.cgi?environment
That will display all of the server's environment variables for the parent. Look for the DOCUMENT_ROOT variable. Copy that variable's path. Then open wrx.cgi in the child and paste that path into the $path_to_library value in the sub parent subroutine and complete the path to end in the /library. That ensures that the $path_to_library in the sub parent subroutine variable is correct.
Then, if you try to access wrx.cgi in the child domain and you get a message that it can't find a usable variable it has to be a permission problem somewhere in the path from the child to the parent's library folder.
Create a cgi script with the following code
#!/usr/bin/perl --
use CGI::Carp qw(fatalsToBrowser);
$file='/path_to_parent/index.html';
print "Content-type: text/html\n\n";
open(FILE,"$file");
while(<FILE>){print}
Change the path_to_parent to the DOCUMENT_ROOT value that you copied from wrx.cgi?environment in the parent domain. Install that script in the parent domain and run it in the browser. It should display the parent's index.html (or whatever your index page's name is). Now, install the same script in the child and run it. It should again display the index page of the parent domain. If it fails, it's a permissions problem somewhere in that document root path. If that works, then change the $file path to the /editwrx/library/routines.txt path and try it. If permissions on /editwrx & /library are also 755 then that should also work.
|
lcanter
Member
| Joined: | Sat Mar 25th, 2006 |
| Location: | |
| Posts: | 20 |
|
Posted: Mon Sep 10th, 2007 01:52 pm |
|
Thanks, but that hasn't solved the problem - I've sent details to you via email.
L Canter
|
Current time is 05:01 pm | |
|
