Page 1 of 1
INCLUDE_ERROR frustration!
Posted: Thu Mar 23, 2006 2:09 am
by neotim
Ok, I did a search about this error and read a number of solutions, none of which work for me.
I have two blogs on the same server. And both of them are all of a sudden giving me this error now. The serendipity_config_local.inc.php file is showing permissions of 700, and I'm unable to download a copy of it, delete it, or change permissions on it.
I tried creating a php file with the code below:
Code: Select all
<?php
chmod('serendipity_config_local.inc.php', 0777);
?>
I tried accessing the file, and I just got the same include_error.
What can I do to get my blogs back up and running!!!
Posted: Thu Mar 23, 2006 2:25 am
by neotim
I finally got the fixperm thing to at least run... but this is what I get:
Code: Select all
Warning: chmod(): No such file or directory in /home3/neotim/neotim-www/blog/scr8694.php on line 2
Any suggestions?
Posted: Thu Mar 23, 2006 2:30 am
by neotim
dude... I'm on a roll tonight!
Ok, my path was wrong - fixed it and I get this now:
Code: Select all
Warning: chmod(): Operation not permitted in /home3/neotim/neotim-www/blog/fixperm.php on line 2
Here's the fixperm file:
Code: Select all
<?php
chmod('/home3/neotim/neotim-www/blog/serendipity_config_local.inc.php', 0777);
?>
Now I'm really stumped
Posted: Thu Mar 23, 2006 3:49 am
by judebert
Essentially, it's telling you that you're not allowed to chmod. That's not especially surprising: usually only root is allowed to chmod (or override the file system in any way). Sometimes FTP will be allowed to do it.
I think you're traveling the right path, though: that file has got to be changed! Contact your sysop/sysadmin/whatever. Sounds like they made a change to the way they run their scripts.
How did the permissions get changed in the first place?
Posted: Thu Mar 23, 2006 4:11 am
by neotim
judebert wrote:How did the permissions get changed in the first place?
I'm not sure if I did it or not. I was changing permissions earlier today in a totally different folder (a different project), but I know I didn't change anything in either of my blog folders.
I'll contact tech support and have them try to chmod.
Posted: Thu Mar 23, 2006 6:11 am
by neotim
Ok, my host tech changes perms to 777, and everything works now. They said this:
Code: Select all
the situation on those files is strange. It might be do to an automated security script on our end. In some versions of serendipity there was a vulerability in in that config file.
What should the permissions be? I tried 770 and it wouldn't work, so I have it sitting at 777 now, which is a security risk, isn't it.
Posted: Thu Mar 23, 2006 9:32 am
by garvinhicking
Usually the file should be owned by the HTTP process user, and only be read+writable for that user, and not for any other users.
HTH,
Garvin